Privacy Policy

• Your answers to the style check are stored in your browser. Our server works out your result from them and doesn’t keep them.
• We only have your email address if you join early access, or if you sign in with Apple or Google to save your result to your Cue profile or to keep an outfit, pin a piece or save a look. Each is always your choice. We use an early-access address to tell you about early access and the app’s launch, and for nothing else.
• We only count your visit if you say yes, and you can change your answer at any time in section 5.
• The style check and the Lookbook need no account, and you can look around “Help me dress better”, “Help me wear this piece” and Studio without one. Keeping an outfit, pinning a piece and saving or sharing a look need one: you sign in with Apple or Google to do them.
• If you use Studio, the looks you save are stored in your account, and anyone you give a shared look’s link to can open it.
• While you’re signed in, the directions, outfits, pieces and lessons you keep on the website are saved to your account as well as this browser. Signing in doesn’t move anything this browser already held on its own. If it holds records from before you signed in, You offers to add them to your account, and nothing moves until you press the button.
• We don’t sell personal information, and we don’t show ads.
• The Cue app is in testing and expected in early 2027. Part B explains what it does with photos of your clothes.

Cue Style (“Cue”, “we”, “us”) runs the website at cue.style and the Cue app. We are the controller of the personal data this policy describes. For anything about your data, email admin@cue.style.

This policy has two parts. Part A covers the website, which anyone can use today. Part B covers the app, which only testers use until it launches.

The style check asks you to pick outfits and answer a few questions, then works out a read of your taste from your answers. Your answers are kept in your browser, and our server works out your result:

• Your answers are held in the page while you take the style check. They are also kept in your browser’s session storage, for this tab only, so a refresh doesn’t lose your place: you can pick up where you left off, and a result you have reached is shown again. Closing the tab removes them, and so does starting again. The copy kept in your browser is never sent anywhere.
• Your finished result is kept in your browser until you forget it or clear this site’s data, so you can come back to it. It doesn’t expire.
• The colouring questions (skin depth, undertone, hair and eye colour, and contrast) are optional, and you can skip any of them. They shape which colours your palette holds and how your figure’s skin and hair are drawn. Nothing is inferred from a photo, because the style check never asks for one.
• Working out your style check: to show your result, we send your answers (the pictures you choose and what you tell us) to our server. We use them only to work out your result, and we don’t store them or keep them in our logs. Your colouring answers (skin, hair and eyes) are optional, and help us provide a personal palette for you. They are sent with your answers only while the box under the first colouring question is ticked, as it is to begin with. Untick it, or skip those questions, and nothing about your colouring is sent. To stop the style check being misused, our server counts the requests from each network address in an hour and in a day. It keeps a scrambled form of the address, never the address itself, and deletes the counts after two days.
• Your style card is built in your browser. Printing or downloading it sends nothing to us.
• The Lookbook, for your directions: if you have kept directions in this browser, the Lookbook puts a look and an idea to try for each of them above its looks. Reading what your browser kept sends nothing. To find them, your browser asks our server once for the ideas for every direction, with whether you dress from menswear or womenswear if the style check you took in this browser says, so that it offers only looks you would wear. It sends nothing else about you, not even which directions you keep, it asks for no sign-in, and we don’t keep what you ask for in our logs. The counts of requests from each network address work as described above.
• The Lookbook, from the library: after its own looks, the Lookbook lists more, made from our library of sample pieces. Reading what your browser kept sends nothing. To list them, your browser asks our server for twenty at a time, with whether the Lookbook is filtered to menswear or womenswear, which directions you keep (an id for each, nothing else) so that theirs come first, and, for a look you saved from the library, its id so the page can draw it. It asks for no sign-in, and we don’t keep what you ask for in our logs. The counts of requests from each network address work as described above.
• Dressing for an occasion: the dress page starts from the direction of the style check you took in this browser, if you took one, or from a direction you choose. Reading what your browser kept sends nothing. When you are signed in and the page shows outfits for a direction, it keeps that direction for you, the same as keeping it yourself: it is added to the directions you keep, in your account, and you can forget it on the “Directions you keep” page. Without a sign-in the page keeps nothing. To choose outfits, your browser sends our server the direction, which of the four choices you made and whether you dress from menswear or womenswear. If the result you kept in this browser says how you finish an outfit, it also sends which things you finish with (earrings, a belt, a watch and so on, never the metal or the styles), so an outfit can say where one fits. The request carries no sign-in token, and the page is open to anyone, and we don’t keep what you ask for in our logs. The counts of requests from each network address work as described above.
• The plan’s example: before the brief, the plan page shows how a plan works, with three looks. It reads the pieces you have ticked in your browser to choose which to start from, and sends nothing from them. To show the looks, your browser sends our server the direction you kept last (or a sample direction if you have kept none), each of the four choices the dress page offers and whether you dress from menswear or womenswear. The request carries no sign-in token, though the page is only open once you have signed in, and we don’t keep what you ask for in our logs. The counts of requests from each network address work as described above.
• What defines an aesthetic: the page for an aesthetic starts from its address and, if you took the style check in this browser, from whether you dress from menswear or womenswear. The list of aesthetics you know, on Directions, uses the aesthetic your style check leads with, or the one you chose to explore instead. Reading what your browser kept sends nothing. To show a page or the list, your browser sends our server the aesthetic and whether you dress from menswear or womenswear. It asks for no sign-in, and we don’t keep what you ask for in our logs. The counts of requests from each network address work as described above.

To delete your saved result, choose “Forget my result” on You, or clear this site’s data in your browser’s settings. “Start again” begins a new style check and leaves your saved result as it is until you reach a new one, which replaces it.

cue.style doesn’t set cookies. It keeps a few items in your browser’s local or session storage, and only this site can read them:

• cue.style/assessment/draft@1 held your answers so far, for 24 hours, in an earlier version of the style check. The current one doesn’t write it, and a copy left in your browser is removed when you clear this site’s data.
• cue.style/read/draft@1, in session storage, holds your answers to the style check so far, your colouring answers if you gave any, and your result once you have one. It lasts for this tab only: it goes when you close the tab or start again, “Forget my result” on You removes it too, and it is never sent anywhere.
• cue.style/assessment/snapshot@1 holds your finished result, until you forget it or clear this site’s data. “Forget my result” on You removes it.
• cue.style/read/record@1 holds the written read of your pictures that goes with that result, until you forget it or clear this site’s data. It also holds the colours of your result’s palette, so your palette page can show them. They stay in your browser. It also holds the outfits your result suggested and the lines it offered to explore further, so the For you page can show them. They stay in your browser. If you gave your colouring, this item also holds the palette it gave, and which of its colours sit near your face and which lower down, so your palette page can show the colours that lead for you. It does not hold your colouring answers. It is kept for as long as your result is. Taking the style check again replaces it, “Forget my result” on You removes it, and clearing this site’s data removes it. The style check sends your colouring answers to our server only while the box under the first colouring question is ticked, to work out your palette, and our server never stores them or keeps them in its logs.
• cue_public_saved_looks_v1 holds the looks you save in the Lookbook, until you remove them.
• cue_early_access_joined_v1 records that you’ve joined early access, so the form doesn’t ask again.
• cue.consent@1 records your answer about usage statistics, so we don’t ask on every page.
• cue.consent.views@1, in session storage, holds a count of the pages you have opened in this tab, so the site can wait until the second before it asks about usage statistics. It is a number and nothing else: it holds no page address. It is only written while you haven’t answered, and it is deleted when you close the tab.
• cue_attribution_v1, in session storage, holds the campaign tags of the link you arrived by. It is only written if you allow usage statistics, and it is deleted when you close the tab or turn statistics off.
• cue.handoff.pending and cue.handoff.auth hold a save to the app while you sign in, and are cleared once it’s done. cue.handoff.provider remembers which button you saved with, so this browser can remind you to use the same one. It stays until you clear this site’s data. If you use Google’s button, Google’s sign-in script loads from accounts.google.com and Google may set its own cookies, under Google’s privacy policy.
• cue.studio.auth keeps you signed in to Studio on this browser, until you sign out or clear this site’s data. It holds the sign-in session Supabase gives this browser (a token, never your Apple or Google password). It is separate from the sign-in used to save your result to your Cue profile, and signing out of Studio doesn’t sign you out of the app.
• cue.style/piece/entry@1 holds the sample you chose and the words you typed about your own piece on “Help me wear this piece”, so they are there when you come back. It is kept in this browser only. It is a draft: it expires seven days after you last changed it, and the page then starts clean. It is also cleared when you press “Start again” or sign out of Studio, and clearing this site’s data removes it too. Your saved looks are not touched by any of this. We never see the words: they are not sent to us, put in an address or counted. Searching for a sample asks our server for the sample pieces in the way Studio does (section 9), and sends nothing you type.
• cue.style/studio/return@1 holds where you were going when Studio sent you to sign in or to take the style check: “Help me wear this piece”, or Studio with the samples you had chosen to open and, if you chose one to keep, what you meant to do with it. It is kept in this tab’s session storage only and is never sent anywhere. It is removed as soon as it has taken you there, when you sign out of Studio, after two hours, or when you close the tab. Using it only opens a page: it never saves or shares anything for you.
• cue.style/read/sides@1 holds the sides of your life you chose for each direction on your result, while you sign in to keep them: the names of the aesthetics and the sides, nothing else. It is kept in this tab’s session storage only and is never sent anywhere. It is removed as soon as the result has kept them or found it is not for this result, and it goes when you close the tab.
• cue.style/you/directions@1 holds the directions you keep: for each, the name of the aesthetic, the side of your life you keep it for, one line about it and the day you kept it. It stays in this browser and is never sent anywhere, and signing in doesn’t move it on its own, though you can choose to add it to your account. It stays until you forget a direction on the “Directions you keep” page or clear this site’s data.
• cue.style/you/owned@1 holds the pieces you tick as ones you own in “Closet”: the id of each sample piece and nothing else, never a photo or a word you typed. It stays in this browser, holds at most 100 pieces, and stays until you untick a piece or clear this site’s data. To count how many outfits each piece goes into, the pieces you have ticked are sent to our server with that one request. It uses them to answer and keeps nothing. Studio’s “Use something I own” reads this list in your browser, when you press it, to choose a piece for your board, and sends nothing from it. The dress page reads it in your browser to say how many pieces of an outfit you’ve ticked, or ticked something similar to, and sends nothing from it.
• cue.style/you/outfits@1 holds the outfits you keep, up to 24: for each, its name, the pieces it is made of, the piece its board is built around, the sentence on why it works, the occasion you chose it for, the name of the aesthetic, the side of your life you keep it for and the day you kept it. If you answer “Did you wear it?” under an outfit, it also holds your answer (whether you wore it, and the reason you chose from a short list, such as the colour or the day changing) and the day you gave it. If you press “Ask me later” instead, it holds the day the question will come back, a week on. Nothing on the site uses an answer to choose outfits, and there is nowhere to type anything into it. The exception is your For you page. Once you’re signed in, it reads your newest answer that says how an outfit went: an outfit you said you wore and it felt right leads it with the same style for the next occasion, and one you said was off leads it with a different style. It does that in your browser, for two weeks or until you keep another outfit, and sends nothing. “Not yet” and “Ask me later” change nothing. It stays in this browser and is never sent anywhere, and signing in doesn’t move it on its own, though you can choose to add it to your account. It stays until you forget an outfit on the “Your outfits” page or clear this site’s data.
• cue.style/you/understood@1 holds what you’ve tried: the short lessons we note when you change an outfit in Studio or open one from the dress page. For each lesson it holds the sentence, which kind of lesson it is, the day you met it and where it came from, and it holds at most 24, the oldest making room for the newest. When a Studio change made a lesson, it also holds which change it was (more casual, another colour or something you own) and which of your saved looks or kept outfits you made it on, as an identifier and never its pieces. Notes is for signed-in readers: while you’re not signed in nothing is noted and none is shown, and this key holds only lessons noted in this browser before that. It stays in this browser and is never sent anywhere, and signing in neither reads it nor moves it on its own, though you can choose to add it to your account. While you’re signed in, your lessons are your account’s own, kept as described below, up to 100, and no other account on this browser sees them. It stays until you add it to your account or clear this site’s data, and your account’s lessons stay until you forget them on the “Notes” page or delete your account.
• cue.style/dress/climate@1 holds the place and the season you give on the dress page under “Where do you mostly dress for?”, if you answer it: the place in your own words, up to 60 characters, and one of four seasons. The place never leaves this browser. Only the season is sent with the request for outfits, so a winter asks for layers first and a summer for none first, and we don’t keep it in our logs. Both pre-fill your brief if you write one. It stays until you press “Forget” there or clear this site’s data.
• cue.style/plan/draft@1 holds the brief you write on “Your brief”: the directions you choose, the side of your life, the season you give, the most you’d spend and its currency, the piece you pinned and the colours from your style check if you leave them in, and the words you type for what it must have and what you never wear. It stays in this browser and is never sent anywhere, and while you’re signed in your brief is your account’s own, kept as described below, and no other account on this browser sees it. Nothing reads the words you type to choose an outfit, and nothing counts them. It stays until you press “Forget this brief” or clear this site’s data.
• cue.style/saved/looks-at@1 holds the day you saved each look in the Lookbook, so Saved can show the newest first. It holds look names from our Lookbook and days, nothing you type. It stays in this browser and is never sent anywhere, and a day is removed with its look or when you clear this site’s data. While you’re signed in, a look you save in the Lookbook goes to your account instead, as described below, and this key is left alone.
• cue.style/account/<your account id>@1 holds, while you’re signed in, the directions, outfits, pieces and lessons you keep in your account: the details described above, the day each was last changed and, for one you forgot, an empty marker until your account has been told. It also notes which changes your account hasn’t been told of yet. It is removed when you sign out of Studio. It is a working copy: clearing this site’s data removes it too, and what your account has already saved stays there. It holds as many as your account can: 24 directions, 200 outfits, 300 pieces and 100 lessons, the same limits your account has, and this browser never shows or keeps fewer than your account holds. It also holds the looks you save in the Lookbook, up to 200: each is the name of the look in our Lookbook and the day you saved it.
  cue.style/account/<your account id>/held@1 exists only when changes your account hadn’t been told of were left behind: when you sign out and choose to keep them on this device, or when your session ends underneath the page. It keeps only those changes, and nothing else from your account. If your session ended, the changes are locked: they are scrambled with a key that your account holds and this browser does not write down, so they can’t be read here until you sign in with the same account. If you chose to keep them at a sign-out and this page could not lock them, they are kept as readable text and the page said so when you chose. Either way the copy is at most 256 KB, keeping the newest changes first, and is removed after 14 days, when you sign in with the same account and it has been applied, when you remove it from the notice you’re shown, or when you clear this site’s data. When your session ends and this page does not yet hold your account’s key (it was opened offline, or closed before the key arrived), the changes can’t be locked, and are removed from this browser instead, and the page tells you. A locked copy is not a guarantee: it hides the changes from anyone who only has this browser, but anyone who can sign in as you can read them, this browser still shows that an account has changes waiting (not which account or what they are), and removing a file from a browser doesn’t overwrite the disk it was on. Someone else who signs in on this browser sees their own records and never yours, and can neither inspect, export nor restore your kept changes. Both keys are sent nowhere except to your account, as section 9 describes.

Everything except the campaign tags is needed for a feature you chose to use, so it needs no separate permission. The campaign tags need your permission, which is why they wait for it.

If you join early access, we collect:

• your email address;
• your first name and phone type, only if you add them;
• that you ticked the box to agree, when you did, and which version of the wording you agreed to;
• if you leave your email on the plan page to be told when payment opens, that it was left there, so we can tell interest in the plan from interest in the app. Your brief is not sent with it;
• if you leave your email on the Pro page to be told when Pro opens, that it was left there, so we can tell interest in Pro from interest in the plan and in the app. Nothing else is sent with it;
• if you leave your email on the Ultra page to be told when Ultra opens, that it was left there, so we can tell interest in Ultra from interest in Pro, the plan and the app. Nothing else is sent with it;
• if you allowed usage statistics, the campaign tags of the link you arrived by, the website that sent you (its domain only, never the full address) and the page you landed on.

We use these to email you about early access and the app’s launch, including an invitation if a testing place opens up, and to learn which links bring people to Cue. We don’t add you to any other list, and we don’t share your details with advertisers.

If you left your email on the plan page, we use it to tell you when payment for the plan opens, and for nothing else. The plan is an early test, so it may change or not go ahead, and then we will tell you that instead.

If you left your email on the Pro page, we use it to tell you when Pro opens, and for nothing else. Pro is not built yet, so it may change or not go ahead, and then we will tell you that instead.

If you left your email on the Ultra page, we use it to tell you when Ultra opens, and for nothing else. Ultra is not built yet, so it may change or not go ahead, and then we will tell you that instead.

Ultra is a stylist, a real person, looking at your style check, your closet and your colouring. If you choose to share your shape and features with the stylist for a plan, they see what you share for that review, and we keep no photograph of your shape or features. We don’t ask for any of it in the style check, and we don’t work anything about your body out from a photograph.

We rely on your consent, which you can withdraw at any time with the unsubscribe link in any of our emails, or by emailing admin@cue.style. You must be 13 or over to join.

Your details are stored with Supabase, our database provider. We keep them until you unsubscribe or ask us to delete them, and we delete the early-access list within 12 months of the app’s public launch. After you unsubscribe we keep only your email address on a do-not-email list, so that we respect your choice. Before we send the first early-access email, we will name the email service that sends it in this policy.

We count visits only if you allow it. The site asks from the second page you open in a tab, and not on the sign-in page, and nothing is counted until you say yes. If you ignore the question, the answer is no. If your browser sends a Global Privacy Control signal, we treat that as a no and don’t ask.

If you say yes, we record events like these:

• which pages you open;
• which Journal piece you open, by its address name and strand.
• which steps of the style check you complete or skip, and whether you finish it;
• which parts of your result you open, and whether you keep your style card;
• which of the ways in on the home page you choose: finding your style, dressing better, wearing a piece, making something in Studio, or opening the Lookbook. Only that choice is recorded, never anything you type;
• if you see the offer for a plan, that you saw it, and if you ask to be told when payment opens, that you did. Nothing else is recorded with either, not your brief or anything you type;
• if you open the Pro page, that you did and where on it you opened it: the top, or one of its four sections. Nothing else is recorded with it, not anything you type;
• if you open the Ultra page, that you did and where on it you opened it: the top, or one of its two sections. Nothing else is recorded with it, not anything you type;
• if one of the quiet prompts for Pro or Ultra, on For you, Dress and Closet, is shown to you or you open it, that it was, and which one. Nothing else is recorded with it, not the words on it, your style check or anything you type;
• whether an early-access signup started, worked or failed, but never the address you entered.
• if you keep a direction, which side of your life it is for (work, everyday, going out and so on) and where on the site you kept it. Never the direction’s name or anything you type.
• if you keep an outfit, which side of your life it is kept for (work, everyday, going out and so on) and where on the site you kept it. Never the outfit, its pieces, the aesthetic’s name or anything you type.
• if you answer “Did you wear it?” under an outfit, your answer (yes and it felt right, yes but something was off, or not yet) and the reason you chose from a short list, such as the colour or the day changing. It is recorded as an event when your answer tells us more than your last one: the first time you say you wore it or give a reason for a “not yet”, and again if a “not yet” later becomes a yes. A reason you add to a yes afterwards stays in your browser and is not recorded again. A plain “not yet” and “Ask me later” are not recorded. We use these events only to see whether people answer. Never the outfit, its pieces, or anything you type.
• if you press “Try it in Studio” on a card in the Lookbook, which side of your life the direction is for (work, everyday, going out and so on). It never sends the aesthetic, the look or the idea.
• if we note a lesson from an outfit you change, which kind of lesson it was (the pieces that carry a direction, visual weight, how dressed up it is, colour, or why an outfit works). Never the lesson’s words.
• if you press “Try it on another outfit” on a note on “What you’ve tried”, which change the note was made with (more casual, another colour or something you own). Never the outfit, the note or its words.
• if you open the dress page, which of its four choices we showed outfits for (a first week at a new job, a date, a cold wet day or nothing feeling right), whether you chose it or the page showed it first (a yes or no, nothing else) and how many outfits we showed you. It never sends the direction you dress in, an outfit or a piece.
• if you tick a piece in “Closet”, how many pieces you have ticked in all. Never which pieces, which direction or anything you type.
• if you are shown the suggested next step on a page, which step it was, and if you press its button, which step you pressed. A step is one of a fixed list of ids (to take the style check, to sign in, to keep a direction and so on). Never what you have kept, a direction, an outfit or anything you type.
• if you tick a piece as one you own, how many pieces you have ticked in all, as a range (1, 2 to 4, 5 to 9 or 10 or more). Never which pieces.
• if you open the page where you set out your brief for a plan, that you opened it; and, if you leave it with changes you did not save, the name of the last part of the brief you were filling in (the direction, the budget and so on). Never what you wrote in it.
• if you use Studio, which kind of place you choose a piece for (a top or shoes, say), whether you chose it from the suggested row or the whole list, how far along the row it was, and whether the place was empty before. Studio also counts when you try another piece, undo a change and what kind of change it was, save a look, turn sharing on or off, download an image of a look and in which shape, and tap a suggestion under the board. If you use “Try a change”, Studio also counts which of its four changes you ask for. If you add a piece from the row of kinds under the board, Studio also counts which kind you press (a hat or a skirt, say). It never sends which piece, which look or anything you type.
• if you pin a piece in Studio from “Help me wear this piece”, which of four ways you chose: wear it quietly, bring out one of its colours, make the outfit more expressive, or adapt it. It never sends which sample you chose or anything you type.

Each event also carries: the page’s address, without anything after a “?” (and, for a look shared in Studio, without the look’s own id); the website that linked you here (its domain only); your browser, operating system, device type, screen size and language; and a random reference for your style check, made when you start it and kept only in the page, so a reload starts a new one. Page views and signups also carry the campaign tags of the link you arrived by.

We never record your picks (the pictures you pick in the style check), your colouring, what your result says, your name, your email address or anything else you type. There are two exceptions, both on your result and both only if you allow usage statistics: your answer to “Does this sound like you?” (yes or not quite), and, if you press Send under “Report a problem” on your result, which of four fixed reasons you chose. Nothing you type is ever recorded.

If you name an aesthetic that your picks do not support, and you allow usage statistics, we also count it when your result is shown: how many of your names your picks did not support, how many they did, and whether your picks led your result on their own. Only those two numbers and a yes or no are recorded, never the names or a pick.

If your picks give us nothing to read, and you allow usage statistics, we also count it when we tell you so: whether you picked nothing or your picks did not point to a style, and how many outfits and pieces you picked. Only that reason and that number are recorded, never a pick.

PostHog processes these events for us in its EU region. PostHog uses your IP address to estimate your approximate location (country, region and city) and then discards it, so we never see the IP address. Nothing is stored on your device for statistics, and no cookies are set. We rely on your consent, and we keep the events for up to 12 months.

Your choice

The “Privacy choices” links in the footer and at the foot of your You page ask the same question in a small window, with the same two choices.

• Vercel hosts cue.style. Like any web host, it receives your IP address and the details of each request (the page, your browser) to deliver pages and protect the site, and keeps them briefly in its logs.
• The pictures of clothes on the home page, in the Lookbook and in some parts of your result are delivered by Bunny.net, which receives your IP address and browser details when your browser fetches them.
• Our fonts, and the pictures in the style check itself, are served from cue.style. No font provider receives your details.

If you email us, we receive your email address and what you write, and use them to reply.

The result page’s “Report a problem” builds a report in your browser. Nothing is sent unless you copy it into an email to us yourself. The report contains your picks, your exclusions, version details and your result, and your colouring answers only if you tick the box to include them. We use a report only to find and fix the problem, and delete it within 12 months.

Only if you choose to, by signing in with Apple or Google on the page that offers it. We then store your style check answers and your result on your Cue profile, which is part of your Cue account, so your result is kept for you and the app can open on it when it arrives. Your colouring answers (skin, hair and eyes) are stored only if you tick the separate box for them, which is your explicit consent; otherwise they aren’t saved to your account. We keep the saved answers until you delete your Cue account, which deletes them with it. Signing in does not add you to any email list, and the website signs you out once the answers are saved.

If you tick to send your colouring, we also keep the palette it gave, and use it only to tell you whether a board’s colours sit in it.

Studio is where you build outfits from our sample library and save them. You can open Studio and build a look without an account. Saving a look and sharing it need one, so you sign in with Apple or Google when you press Save or Share, which is the same account the app uses (section 10 says what we receive when you do). The same sign-in is needed to keep an outfit on the dress page and pin a piece on the piece page. The style check and the Lookbook need no account. Studio doesn’t ask you to take the style check first: it starts from your style check’s aesthetic if this browser or your account holds one, and says where to take the check if neither does. We never see your Apple or Google password. If you use Google’s button, Google’s sign-in script loads from accounts.google.com when you are asked to sign in, and Google may set its own cookies, under Google’s privacy policy. Studio keeps you signed in on this browser, in cue.studio.auth, until you sign out. Signing out of Studio signs out this browser only, never the app on your phone. The sign-in page uses the same sign-in and keeps nothing of its own: the page it sends you on to is in its address, and isn’t stored.

When you save a look, we store it with Supabase, in a table called studio_looks, tied to your account. A look is the sample pieces you chose (their names in our library and the version of each picture), which piece you built it around, the aesthetic those pieces are closest to, when you made and last changed it, and whether it is shared. It holds nothing you type, apart from one thing you may choose: a name to show on a look you share, of up to 40 characters, which is empty until you turn it on and goes when you turn it off. Only your account can read your saved looks, apart from a look you share (below). The pieces are our own pictures and not your clothes: a look is never added to your wardrobe in the app, and it changes nothing the app works out about you. We keep a look until you delete it, or delete your account, which deletes it with everything else.

What your account keeps. While you’re signed in, the directions, outfits, pieces and lessons you keep are saved to your account with Supabase, in a table called saved_context, as well as in this browser. Each is a short record of what section 3 describes, with the day you last changed it, and nothing you type is added. Only your account can read them. We don’t share them, put them behind a link or use them for advertising. When you forget one, its details are removed and an empty marker stays for 30 days, so your other devices learn of it, and then it is deleted. We keep what you save until you forget it or delete your account, which deletes it with everything else, and no timer removes it if you don’t sign in. A device that has been away for longer than the marker lasts can’t bring back something you forgot on another. Your account decides how many it holds (24 directions, 200 outfits, 300 pieces and 100 lessons), and if you reach a limit the page says so and nothing already saved is removed. If you write a brief, it is saved too, with the words you typed in it. Nothing reads them to choose an outfit or to count anything. If you save a look from the Lookbook while you’re signed in, it is saved to your account too, up to 200: the name of the look in our Lookbook and the day you saved it. Until your account can keep them, they stay on this device only, and the page says so. Your account also keeps one random key, in a table called saved_context_recovery_keys, that only you can read. This browser holds it in memory while you’re signed in, to lock any changes that your account hasn’t been told of if your session ends underneath the page. The locked changes are never sent to us; the key is the only part we hold, and it is deleted with your account.

Adding what this browser kept. If this browser holds directions, outfits, pieces or lessons you kept before you signed in, You shows what they are and has a button, “Add them to my account”. Nothing moves until you press it. Pressing it saves each of them to your account as described above, and a record is taken out of the browser’s own list only after your account has confirmed that record saved. From then on it belongs to your account and isn’t a guest record in this browser after you sign out. A record your account didn’t take (it holds as many as it can, it couldn’t be reached, or it already has a newer version) stays in this browser as it was, the page tells you how many, and pressing the button again tries only those. Pressing it twice does no harm. Your saved result is a separate step and isn’t part of this. It adds no storage key and sends nothing except the records to your account. Looks you saved in the Lookbook are among them.

Downloading and deleting what you’ve saved. On You, “Download what I’ve saved” asks your account for every record it holds, right then, and your browser makes one JSON file from the answer. The file also lists any guest records this browser still holds, marked as guest records. It is made in your browser, nothing is sent anywhere to make it, we don’t keep a copy, and it doesn’t change if your account does. Anyone who opens the file can read it. “Delete what I’ve saved” asks twice, then forgets every direction, outfit, piece and lesson your account holds, so it works however many you have. Each leaves an empty marker for 30 days, as described above, so your other devices learn of it. Deleting leaves your account itself, your Studio looks, which you delete one at a time, any guest records in this browser, and files you downloaded earlier. Deleting your account deletes everything it holds, and section 17 says how.

If you share a look, anyone who has its link can open it without signing in, and see the board, the aesthetic it’s closest to and the pieces in it. They can’t see who made it, unless you chose to show a name on it: then the name you typed is on the look’s page and in the preview of its link, and nothing else about you is. You can turn the name off at any time, and it comes off the look at once, and we don’t list shared looks anywhere. Shared looks ask search engines not to list them. If you turn sharing off, or delete the look, the link stops working at once, though anyone who has already seen it may have kept a copy of what they saw.

Where the pieces come from. The sample pieces you choose from are kept on our server, not in your browser. When you open a part of an outfit, such as the tops or the shoes, your browser asks our server for its pieces and sends it the sign-in token Studio holds, so the server knows you are signed in. When you build a look, or your saved looks are listed, your browser sends it the names of the pieces in them, and gets back their pictures and the aesthetic they are closest to. When you open a shared look’s link, your browser sends the link’s id, and our server reads that one look. We don’t keep the token, and we don’t keep what you ask for or the link’s id in our logs. To stop the library being copied in bulk, our server counts the requests from each network address in an hour and in a day. It keeps a scrambled form of the address, never the address itself, and deletes the counts after two days.

We don’t add you to an email list because you use Studio, and we don’t show ads in it today. Studio counts the few choices listed in section 5, and nothing else you do there. If you have allowed usage statistics, the pages you open still count as they do anywhere on the site, but a shared look’s link is cut down to “/studio/look” before anything is sent, so the link itself never reaches our statistics provider.

The app is in private testing ahead of its launch, expected in early 2027. You sign in with Apple or Google. We receive your email address (with Apple, a private relay address if you choose to hide yours) and an account identifier from them, and your name if they share it. We never see your Apple or Google password. Your account is stored with Supabase.

When you add a piece to your Closet:

• the photo is uploaded to Bunny.net, which stores it and delivers it back to the app. Photos are delivered over long, unguessable links that aren’t listed anywhere, but they aren’t access-controlled: anyone holding the exact link can open the image;
• it’s sent, through our server, to Anthropic’s Claude, which describes the piece (category, colour, fabric, formality and so on). Anthropic doesn’t use data sent through its API to train its models;
• it’s sent to Bria to cut the garment out of its background, and the cut-out is stored with Bunny.net;
• a private copy of the original photo is kept in our own storage with Supabase, which only we can read, so we can check and improve how accurately Cue describes clothes. You can object to this at any time by emailing admin@cue.style, and we will delete your copies.

We don’t send your photos to anyone to train their AI models. Please photograph clothes, not people: a photo that shows a person is processed in the same way.

The pieces you add and their descriptions, your style answers and style profile, and the outfits you save, wear, like or dislike are stored on your phone and synced to our database with Supabase, where only your account can read them. If you answer the app’s colouring questions, your answers are stored with your style profile to order your palette, and are never used to infer anything else about you.

To suggest outfits for the day’s weather, the app asks ipapi.co to estimate your approximate location from your IP address, then asks Open-Meteo for the forecast there. ipapi.co receives your IP address and Open-Meteo receives approximate coordinates; neither receives anything else from Cue. We don’t store your IP address or your location, and the app keeps the forecast on your phone for an hour. The app doesn’t use your phone’s GPS. Reminders are scheduled on your phone, and nothing about them is sent to us.

When the app suggests something to fill a gap in your wardrobe, it sends a description of the kind of garment (for example, “navy wool overcoat”) through our server to SerpAPI, a shopping search service. It never sends your photos or your style profile. Tapping a suggestion takes you to the retailer’s own site, where the retailer’s privacy policy applies. We have no affiliate arrangement with them today.

The app records how its features are used and when something goes wrong, so we can fix problems and improve its suggestions. These records go to PostHog, in its EU region, and to our database with Supabase. They never include your photos, image links, AI prompts or AI responses. We also count how often each account uses the AI features, to keep costs within daily limits. You can turn usage analytics off in the app’s Settings.

If you subscribe to Cue Pro, we keep which plan you chose, the store you bought it from, when it started, renews or ends, whether it will renew, and whether a payment is being retried or was refunded. We use these to provide Cue Pro and to check a subscription with the store. Apple or Google takes the payment, so we never see your card or bank details.

RevenueCat manages subscriptions for us. It receives your Cue account identifier and your purchase records from the App Store or Google Play, and tells us whether you have Cue Pro.

You can delete your account by emailing admin@cue.style, and we will permanently delete your data within 30 days. You can also download your data from the app’s Settings.

You can also delete your account in the app, in Settings. That deletes your account and everything our database holds with it at once, including our record of your Cue Pro subscription. The image files of your wardrobe photos stay with our image host until you email us, and then we delete them within 30 days.

Apple, Google and RevenueCat keep their own records of purchases, which they may need for tax and accounting. Deleting your Cue account doesn’t remove them, and it doesn’t cancel a subscription: cancel that in the store first. Email us and we’ll ask RevenueCat to delete its record of you.

On the website, You has a “Delete what I’ve saved” button that removes the directions, outfits, pieces and lessons your account holds and leaves the account. Deleting the account itself is by email, as above, and deletes those records with everything else.

The private copies of your photos described in section 11 aren’t yet deleted automatically: email admin@cue.style and we will delete them within 30 days.

These companies process personal data on our behalf, only to provide their service to us:

• Vercel (United States, global network): hosts the website.
• Supabase (European Union, Ireland): database, sign-in and storage, including the early-access list, and the server that works out your style check result, and the looks you save in Studio, and the server that gives Studio its sample pieces.
• PostHog (European Union): usage statistics, when you allow them, and app analytics.
• Bunny.net (BunnyWay d.o.o., European Union, Slovenia; storage in Frankfurt, Germany, delivered worldwide): stores and delivers images, both the wardrobe photos you add in the app and Cue’s own pictures of sample pieces.
• Anthropic (United States): AI descriptions of clothes, and outfit suggestions, in the app.
• Bria (Israel): cuts garments out of their backgrounds in the app.
• RevenueCat (United States): manages Cue Pro subscriptions in the app.
• SerpAPI (United States): shopping search in the app.
• ipapi.co (Kloudend, Inc., United States) and Open-Meteo (OpenMeteo GmbH, Switzerland, which deletes its request logs after 90 days): approximate location and the forecast for the app’s weather.

Apple and Google sell Cue Pro through the App Store and Google Play, take the payment and let you sign in. They handle that data as controllers under their own privacy policies.

We don’t sell personal information, share it for cross-context behavioural advertising, or use it for advertising profiles.

• Early-access emails and usage statistics: your consent (GDPR Art. 6(1)(a)), which you can withdraw at any time without affecting what happened before.
• Running the app for you, including your account, photos and wardrobe, Cue Pro if you subscribe, and the day’s weather for your look: performance of a contract with you (Art. 6(1)(b)).
• Keeping outfits and pinning pieces, which you sign in to do, and the looks you save in Studio: performance of a contract with you (Art. 6(1)(b)).
• Serving and securing the website, replying to you, app error reports and analytics, and the private photo copies used to improve accuracy: our legitimate interests in running a reliable, accurate service (Art. 6(1)(f)). You can object to any of these, and we will stop unless we have a compelling reason.
• Colouring answers saved to your account: your explicit consent where that’s required.
• Sending your colouring answers to work out your palette and your figure, while the box under the first colouring question is ticked: to give you the result you asked for (Art. 6(1)(b)). Untick the box, or skip those questions, and they aren’t sent.

Some of the companies above are outside the UK and the European Economic Area. Where a recipient is certified under the EU–US Data Privacy Framework (with its UK Extension and the Swiss–US framework), we rely on that. Otherwise we rely on the European Commission’s standard contractual clauses, with the UK Addendum for data from the UK. Israel and Switzerland have adequacy decisions from both the European Commission and the UK. You can ask us for a copy of the safeguards that apply.

• In your browser: a result until you forget it or clear this site’s data, and the rest until you clear it (section 3).
• Early access: until you unsubscribe or ask, and no later than 12 months after the app’s public launch.
• Usage statistics: up to 12 months.
• Directions you keep: in your browser, until you forget them or clear this site’s data.
• Pieces you tick as ones you own: in your browser, until you untick them or clear this site’s data.
• Outfits you keep: in your browser, until you forget them or clear this site’s data.
• Looks you save in the Lookbook: in your browser, or in your account while you’re signed in, until you forget them or clear this site’s data or delete your account.
• Notes: in your account while you’re signed in, until you forget them or delete your account. Any left in your browser from before you needed to sign in: until you add them to your account or clear this site’s data.
• Studio looks: until you delete them, or delete your account.
• Directions, outfits and pieces saved to your account: until you forget them or delete your account. A forgotten one leaves an empty marker for 30 days, so your other devices learn of it. Changes kept in this browser because they hadn’t been saved when you signed out or your session ended: up to 14 days, or until you sign in again with the same account and they have been applied, you remove them or you clear this site’s data.
• The sample and words you keep on “Help me wear this piece”: in your browser, until seven days after you last change them, or until you press “Start again” or sign out of Studio.
• Problem reports and emails: up to 12 months after the matter is closed.
• App account and wardrobe: while your account is open. Photos with Bunny.net and our private copies: until you delete them, delete your account and ask us, or object.

Wherever you live, you can ask us what we hold about you, ask us to correct or delete it, stop our emails, or withdraw a consent you gave. Email admin@cue.style. We reply within one month, and may need to check that a request comes from you, for example by replying to the address we hold. We won’t treat you differently for using any of these rights.

For what your account saves on the website, you don’t need to ask: “Download what I’ve saved” on You gives you a file of it, and “Delete what I’ve saved” removes it. To delete the account itself, see section 17.

In the EEA, the UK and Switzerland

You have the right to access, rectify and erase your data, to restrict or object to its processing, to data portability, and to withdraw consent. You can also complain to your data protection authority: in the UK the Information Commissioner’s Office (ico.org.uk), in the EU the authority in the country where you live or work, and in Switzerland the FDPIC. We’d appreciate the chance to put things right first.

In the United States

If you live in California or another state with a consumer privacy law, you have the right to know what personal information we collect, use and disclose, and to access, correct and delete it. The categories we collect are identifiers (an email address, an account identifier), internet activity (usage statistics, only with your permission), approximate location (from your IP address), and, in the app, the photos, descriptions and style profile described in Part B. We don’t sell or share personal information, or use it for targeted advertising, so there is nothing to opt out of, and we honour Global Privacy Control as a refusal of usage statistics. You can use an authorised agent to make a request.

In Canada, Australia, Brazil and elsewhere

You can access and correct your data and withdraw consent under your local law, and complain to your regulator: the Office of the Privacy Commissioner of Canada (or the Commission d’accès à l’information in Québec), the Office of the Australian Information Commissioner, or Brazil’s ANPD. If your country gives you other rights, email us and we will honour them.

The style check and early access are for people aged 13 and over. We don’t knowingly collect personal data from anyone younger. If you think a child has given us their details, email admin@cue.style and we will delete them.

We use encrypted connections, access controls, and database rules that keep each account’s data readable only by that account. No system is completely secure. If you think your account or data has been exposed, email admin@cue.style straight away.

When this policy changes, we update the date at the top. If a change matters to how we use data we already hold, we will tell you by email (if we have your address) or in the app at least 14 days before it takes effect, and ask again where we need your consent.

Email admin@cue.style about anything in this policy.