wdrobe privacy policy

Last updated: 31 October 2026

This policy explains what the wdrobe app for iPhone and Android collects, what it is used for, who else receives it, how long it is kept and how you can delete it. The app is run by ANEMO BİLİŞİM TEKNOLOJİ VE TİCARET ANONİM ŞİRKETİ (Anemo Technology), Kolektif House, Esentepe Mahallesi, Talatpaşa Caddesi No: 5/1, Levent, Esentepe, İstanbul, Turkey. We decide how this data is used, which makes us the data controller.

Separate pages cover the wdrobe terms of use and how to delete your account.

1. What we collect

• Account: your email address and, depending on how you sign in, a password, which we store only in hashed form, the first and last name on your Google account if you sign in with Google, or the identifier Apple gives us if you sign in with Apple. Your username, and your profile photo if you add one.
• Sign-up answers: your name, which clothes you want to see (men's, women's or prefer not to say), your age range, styles and goals, and how you heard about wdrobe.
• Profile details you can add: date of birth, gender and body type.
• Photos: the selfie for colour analysis, full-body photos for try-on and body analysis, and photos of your clothes. Section 2 explains how they are used.
• What you make in the app: outfits and try-on images, saved and planned outfits, likes, favourites and follows. The AI stylist also keeps short notes about your taste, such as colours you avoid, which you can see and delete in the app.
• Cities: up to 10 cities you choose, for weather-based outfit suggestions. The app does not ask for or read your phone's location.
• Device and app details: device type (iPhone or Android), on Android the phone's brand and model, on iPhone the iOS version (and on iPhones with iOS 15, the name you gave your phone), a random ID the app creates for your device, app version, language, time zone, the country of your app store account, the token used to send you notifications and whether notifications are allowed. Your IP address is recorded with your account activity.
• Purchases: your subscription status and purchase records. Payments are handled by Apple and Google, so we do not see your card details.
• Support: what you write to us in the support form or the support chat.

We do not ask for your phone number. Your conversations with the AI stylist are saved privately for 90 days, and our team reads one only if you give feedback on it or report a reply (section 2).

2. Photos and what we learn from them

Colour analysis selfie: when you run colour analysis, including during sign-up, your selfie is sent to an AI provider (section 4). The provider first checks that the photo shows one face; if it does not, we ask you for a new photo. It then works out your skin tone, undertone, eye colour and hair colour, and how light or deep, how soft or bright and how contrasting your colouring is, and picks your colour season. Your palette and the metals that suit you follow from that season. To suggest a jewellery style and patterns, it also looks at the shape of your face and your bone structure. We store the selfie and these results with your account.

Full-body photos: we store each full-body photo you add: the original, a smaller copy, and a copy in Google Cloud that some try-on models use. An AI provider checks whether the photo can be used for try-on. When body analysis runs on a full-body photo, including during sign-up, AI estimates your body shape and proportions, such as shoulder width, leg length and waist definition, and we store the result.

Try-on: to show clothes on you, we send your full-body photo and the clothing images to an AI image provider and store the image it returns.

Nudity check: Google Cloud Vision checks each photo of you and each clothing photo when you upload it, and each try-on image before you see it, for nudity and sexual content. A photo that fails is not added to your account, and a try-on image that fails is never shown to you. We record on your account that it happened and the check's scores. We keep a copy of the stopped image for 30 days so our team can check whether the check was right, and then delete it. Only a few team members can see it.

Your clothes: AI removes the background from photos of your clothes and tags them with details such as type and colour.

Result cards: when you save or share a colour or body result card, we create an image that contains your photo and results and store it with your account. We also store a web page copy of the card, which contains your photo too. The web copy is deleted with the card: about 30 days after you delete the analysis, or at once when you delete your account. If you deleted an analysis before we started doing this, the web copy of its card can stay until you delete your account.

What we do not do: we do not use your photos for facial recognition or to identify you, and we do not create face templates. We do not use your photos or results for advertising, or to train our own AI models.

AI request record: for most AI requests, such as colour and body analysis, photo checks and outfit suggestions, we record the instructions we sent and the text of the reply. For AI stylist chats we record technical details about each reply, such as which model answered, how long it took, which tools it used and which cards it showed, plus what you tap afterwards, any thumbs up or down and reason you give, and any reply you report and why. What was said is not part of this record: it is kept separately, as described below. We use this record to look into errors and check the quality of AI results. Images are not copied into it. It is deleted when you delete your account.

AI stylist conversations: we save what you write to the AI stylist and its replies in our database, with the kinds of cards it showed and which outfits and clothes were on them. We do not copy photos. If you attach clothes or outfits to a message, we save only which ones you attached, and send their cut-out pictures to the AI provider so it can answer. Our team reads a conversation only if you give feedback in it, such as a thumbs up or down on a reply or on the outfits or clothes it showed, or if you report one of its replies. We use it to find and fix the stylist's mistakes and to look into reports, and we record each time a team member opens a conversation. Each message is deleted 90 days after it was written, and all of them are deleted when you delete your account. Older versions of the app, which tell you that chats are not stored, do not save them.

Reporting a reply: after you give one of the AI stylist's replies a thumbs down, you can report it as rude or hurtful, harmful or unsafe, or for another reason. We save the report with the reason you picked, and our team is alerted (section 4).

Conversations you sent us from older versions: older versions of the app let you send a conversation to our team after you rated a reply, once the app had shown you what was included. We received the text of the messages in that conversation up to the reply you rated, yours and the stylist's, the summary of earlier messages if the conversation was summarised, and which outfits and clothes the stylist showed. We did not receive photos. Only our team can read it, and we use it to find and fix the stylist's mistakes. It is deleted 90 days after you sent it. You can delete it sooner in the app, on the page that lists the AI stylist's notes, and it is deleted when you delete your account.

Some image requests, such as try-on images and background removal, are recorded without a link to your account, so these records stay after you delete it. They hold only technical details and our fixed instructions. Older records of this kind can also hold a link to the photo that was sent, or a short description of the pieces in a clothing photo; we no longer store either. The photos those links lead to are deleted when you delete them, as described in section 9, or when you delete your account.

Copies of our AI instructions: we also keep one copy of each different set of instructions we send to an AI provider, so we can see which version of our instructions gave which result. We copy only fixed instructions, made from our own text and general settings such as the language and the types of clothing involved. Instructions built from your data, such as what you typed, descriptions of your clothes or the AI stylist's notes about you, are not copied. These copies have no link to your account and are not deleted when you delete it.

Before we made this change, we also copied instructions built from your data. For outfit suggestions you asked for outside the AI stylist chat, such a copy can include what you typed, details of your clothes and the AI stylist's notes about your taste. We keep these older copies while your account is open and delete them when you delete your account. For a clothing photo that shows several pieces, an older copy can include a short description of each piece, such as its colour and type. These have no link to your account and stay after you delete it.

3. If you choose “prefer not to say”

During sign-up we ask which clothes you want to see: men's, women's or prefer not to say. If you choose “prefer not to say”, the colour analysis of your selfie also suggests whether to show you the men's or the women's clothing set first. If it cannot suggest one, we ask you instead. You can switch to the other set with one tap.

This suggestion is used only to pick the clothes shown to you. It is not shown to you and is not saved as part of your profile. It is not sent to advertising or analytics tools. We keep only which clothing set was used.

4. Service providers

The companies below handle data on our behalf so we can run wdrobe. For AI tasks, which provider handles a request depends on the feature and the model in use, and when one provider is not available another one from this list may take over.

How long a provider keeps the data it receives is set by that provider's own terms.

5. Human review

Authorised members of our team can see uploaded and generated images to moderate content and check the quality of AI results. They can also read AI stylist conversations, but only the ones described in section 2. Which team members have this access depends on their role.

6. Public features

Your profile, your wardrobe and your outfits are private until you change that. You can make your profile or wardrobe public in Privacy Settings, and an outfit stays private unless you make it public. Public outfits can appear in Discover, where other users can see and like them. When another user attaches one of your public outfits or clothes to a message to the AI stylist, we send the cut-out pictures of those clothes and our own labels for them (category, type, colour, brand, season and style) to the AI provider so it can answer. Your name, the names you gave your clothes and outfits, and your try-on images are never sent.

Before an outfit becomes public, Google Cloud Vision checks its images and OpenAI's moderation tool checks the names of the outfit and its clothes. Our team may also review it.

If you share an outfit, we create a link on wdrobe.app. Anyone with the link can see that outfit, even if it is private. The link does not make the outfit public in Discover.

7. Notifications and email

Push notifications: sent through Firebase Cloud Messaging, and only if you allow notifications. They include reminders to finish setting up, outfit plans, likes and new followers, free credits, replies from support and offers. You can turn types off in Notification Settings, or turn all of them off in your phone's settings.

When your look is ready: if you have allowed notifications, we let you know when the try-on made during sign-up is ready. This notification contains text only, with no image. Notification Settings has no switch for it, and turning off every type there does not stop it. You can turn it off, together with all other notifications, in your phone's settings.

Pictures in notifications: some notifications show a picture, such as an outfit image, which can be a try-on image of you, or the profile photo of the person who liked your outfit or followed you. For these we store a smaller copy of the picture at a web address that is hard to guess. The address does not expire, and anyone who has it can open the picture. These copies are currently not deleted when an account is deleted.

Email: we send email through Amazon Web Services from noreply@wdrobe.app: verification codes, account notices, replies to support requests and offers. Offer emails contain an unsubscribe link and a small image that tells us whether the email was opened.

8. Ad measurement and analytics

There are no ads in wdrobe. We advertise wdrobe on other platforms, and we use the tools below to see which of those ads lead to installs and purchases, and to run subscriptions.

• AppsFlyer receives your wdrobe user ID and events such as install, sign-up, paywall views, trial starts, and purchases with price and currency. On iPhone it receives the advertising identifier (IDFA) only if you allow tracking when the app asks. On Android it reads the advertising ID unless you have turned it off in your phone's settings. It also receives your IP address, device details and, on iPhone, an identifier Apple gives each app (IDFV).
• TikTok receives install events and in-app events such as sign-up, sign-in, paywall views, trial starts and purchases from AppsFlyer, server to server. The app does not contain TikTok's software (no TikTok SDK).
• RevenueCat runs subscriptions. It receives your wdrobe user ID, device identifiers, IP address, your purchases and how we think you found wdrobe: for example the kind of source, such as a search engine, an AI assistant, TikTok or a friend, the ad campaign or the page on wdrobe.app you came from, how sure we are about that, and your answer to the question about how you heard of wdrobe. It passes renewals and trial conversions on to AppsFlyer.
• Apple Search Ads: on iPhone, the app gets a token from Apple that shows whether the install came from an Apple Search Ads ad. We check this token with Apple.
• Firebase Analytics receives app events, such as which screens you open and which paywall you saw, with device details and your wdrobe user ID. It also receives how we think you found wdrobe and how sure we are. We do not give it your name or email address.
• Links on wdrobe.app: when someone taps an App Store or Google Play button on wdrobe.app, we record a hashed (scrambled) form of their IP address, their country, the screen size, language, time zone, device model, operating system version, the page or campaign they came from, the page and the part of the page where they tapped, the kind of site that first brought them to wdrobe.app (for example a search engine, an AI assistant, TikTok or Instagram) with any campaign tags in that link, and whether the page was open inside another app, such as TikTok or Instagram, and which one. On Android, the link to Google Play also carries a random code for that tap and the kind of site they came from, and Google Play passes both on to the app. Outside the EU, the UK and Switzerland, we may also record the first page of wdrobe.app someone opens in a browser tab on an iPhone, even if they do not go to a store, with the same kinds of details and a random ID for that tab. We use these page visits only to work out how a later install found wdrobe, and delete the ones that match no install after 2 days. The other records are deleted after 180 days.
• The first time the app opens: the app sends us a random install ID it makes, the same kinds of device details, the app version and whether it is a new install or an update from an older version, and we record a hashed form of the IP address it connects from. We compare this with the store taps and page visits recorded on wdrobe.app to guess whether the install came from the website. On Android, the app also reads the Google Play install referrer once. It holds the tags of the store link you used, or says there were none, and when you tapped the link and installed. For a link on wdrobe.app, the tags include the tap code. It sends this to us, and we use it to label your install and to check how often our website guess is right. AppsFlyer's software in the app also reads it. We link these records to the record the app keeps for your install and, once you sign in, to your account. That install record can also hold a hashed form of the IP address the app connected from, which we use only for this link and delete after at most 180 days, or sooner if you delete your account. From these records, your Apple Search Ads answer, the Google Play install referrer, any invite code or shared link you used and your answer to how you heard about wdrobe, we work out how you most likely found wdrobe and how sure we are. We keep that with your install record and your account, send it to RevenueCat and Firebase Analytics, and may use it to choose which version of sign-up or which offer you see. We do not send it to AppsFlyer, TikTok or other ad networks. When you delete your account, we remove the link between these records and your account. These records are deleted after 180 days.
• Google Analytics on wdrobe.app: every page of wdrobe.app uses Google Analytics, a Google service. It records which pages you open, the page address (which can include the code of a shared outfit link), where you came from, for example Instagram, TikTok, Pinterest, a search engine, an article or a shared link, which download buttons you see and tap, which store you go to and whether you tapped a button or the download page opened the store by itself. On articles it also records how long and how far you read. On every page it also records which links, menus, questions and pictures you tap, how far you scroll and which parts of the page you see, that you copied some text (never the text itself), whether the contact form was sent, and how fast the page loads. Google receives your IP address and browser and device details. Google Analytics stores its own cookies in your browser, as described in the cookie policy at wdrobe.app/cookie-policy.
• Cloudflare Web Analytics: wdrobe.app also counts visits with Cloudflare Web Analytics. It records which pages are opened, where visitors came from, the country, the type of device and how fast pages load. It does not set cookies or save anything in your browser, and it does not identify you or follow you to other sites.

What these tools do not receive: your photos, your colour and body results, the clothing-set suggestion described in section 3, and your answers about which clothes you want to see, your age range, styles and goals.

9. Keeping and deleting data

We keep your data for as long as your account is open, unless you delete it sooner.

Deleting one item: when you delete a photo, a piece of clothing, an outfit or an analysis, it is removed from the app at once. The files are deleted from storage about 30 days later. We keep them for that time so our team can still moderate content after it has been removed.

AI stylist conversations: each message is deleted 90 days after it was written. Conversations you sent us from older versions of the app are deleted 90 days after you sent them, or sooner if you delete them in the app.

Deleting your account: takes effect at once and cannot be undone. It deletes your photos, try-on images, analysis results, clothing photos, result card images and their web page copies. It also removes your name, username, date of birth, gender, body type, clothing and style preferences, saved cities, notification token, device names and device IDs, the AI stylist's notes, your AI stylist conversations and the ones you sent us, the IP addresses on your account activity and your AI request record. Your outfits are removed from Discover and from the app. The steps are on the wdrobe data deletion page.

What we keep after account deletion:

• Your email address and, if you signed in with Apple, the identifier Apple gave us. We keep them only to stop the same account being created again.
• The closed account record, without your name or photos. It still holds your age range, goals, how you heard about wdrobe, how we think you found wdrobe, your app store country, your subscription status, the app version and platform you signed up on, how far you got in setup and the Apple Search Ads token described in section 8. We use these for statistics.
• Records of likes, follows and purchases, so that counts and our purchase records stay correct.
• Support requests and support chat messages. Write to us if you want them deleted.
• Copies of pictures used in notifications, as described in section 7.
• The copies of our AI instructions and the records of image requests described in section 2, which have no link to your account. Older ones can describe the pieces in a clothing photo or hold a link to a photo that has already been deleted.

Apple and Google also keep purchase records under their own policies. Deleting your account does not cancel a subscription: cancel it in the App Store or Google Play.

10. Where your data is processed

Our servers and database run on Amazon Web Services in Stockholm, Sweden. Your photo files and generated images are stored there too. Some copies used by Google's AI services are kept in Google Cloud. Email is sent through Amazon Web Services in the United States. Most providers in section 4 are based in the United States and process data there or in other countries where they operate. Using wdrobe therefore means your data is transferred outside Turkey.

11. Security

The app talks to our servers over encrypted connections. Photos in the app are loaded through links that expire, except the notification pictures described in section 7. Passwords are stored only in hashed form, and our team's access to user data depends on each person's role. No system is fully secure, so we cannot guarantee that data is always protected from unauthorised access.

12. Children and teenagers

wdrobe is not for children under 13. If we learn that a child under 13 has an account, we delete it.

People aged 13 to 17 can use wdrobe, including the selfie and full-body photo steps, and this policy applies to them in the same way. In some countries the law requires a parent's or guardian's consent below a certain age, which in the EU can be up to 16. If that applies where you live, you need that consent before you use wdrobe.

13. Your rights

You can see and change most of your details in the app, and delete single items or your whole account there. Under article 11 of Turkey's Personal Data Protection Law No. 6698 (KVKK) and, where it applies, the EU General Data Protection Regulation (GDPR), you can also ask us to:

• tell you whether we hold data about you and give you a copy
• correct data that is wrong or incomplete
• delete your data
• stop or limit a particular use of your data
• tell you which companies we have shared it with
• consider your objection to a result about you that was reached only by automated analysis and works against you
• give you the data you provided in a format you can take to another service

Write to info@anemotech.com from the email address on your account. You can also complain to the data protection authority where you live. In Turkey this is the Personal Data Protection Authority (KVKK).

14. Changes to this policy

When we change this policy, we update the date at the top of this page. If a change affects how we use your photos or who receives your data, we also tell you in the app or by email.

15. Contact

For questions about this policy or your data:

• Company name: ANEMO BİLİŞİM TEKNOLOJİ VE TİCARET ANONİM ŞİRKETİ
• Address: Kolektif House, Esentepe Mahallesi, Talatpaşa Caddesi No: 5/1, Levent, Esentepe, İstanbul, Turkey
• Email: info@anemotech.com

To delete your account, follow the steps on the wdrobe data deletion page.