Privacy Policy

This policy explains what the Wdrobe app for iPhone and Android and the wdrobe.app website collect, what it is used for, who else receives it, how long it is kept and how you can delete it. Wdrobe 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 terms of service, the cookie policy and how to delete your account.

1. What we collect

• Account: you sign in with Google or Apple, so we never ask for a password and do not store one. We keep the email address that comes with your sign-in. With Google, we also keep the first and last name on your Google account. With Apple, we keep the identifier Apple gives us and the email address Apple shares with us; if you chose to hide your email on Apple's sign-in screen, this is a forwarding address made by Apple. On iPhone, if Apple also shares your name the first time you sign in, we save it as the name on your account, and setup does not ask you for it. We also keep your username, which we create for you and you can change, and your profile photo if you add one.
• Before you sign in: when you first open the app, we create a record for your install. It holds whether you use iPhone or Android, the app version, which version of the setup screens you were shown, and which of those screens you finished and when. On iPhone it also holds the Apple Search Ads token described in section 8, and we check that token with Apple at this point. The record does not hold your name, email address, IP address or a device ID. When you sign in, we link it to your account. We do not delete it, even if you never sign in or later delete your account.
• 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 change: your first and last name, username, which clothes you want to see and your styles. Older versions of the app also asked for your date of birth, gender and body type. The current app does not ask for these. If you gave them before, we keep them with your account until you delete it.
• Photos: the selfie for colour analysis, photos of yourself 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, follows and follow requests. The AI stylist also keeps short notes about your taste, such as colours you avoid, which you can see and delete in the app.
• Outfit suggestions: we save each outfit the AI stylist suggests with your account, with the city and day it was for, if one was set, and a short note about the occasion, such as “job interview, smart”. The AI stylist writes this note in its own words. If you used the suggestion screen in older versions of the app, the note is the text you typed there. When you give a suggested outfit a thumbs up or down, and a reason if you pick one, we save that with a short text description of the clothes in the outfit, and we use it to tailor your later suggestions.
• Cities: up to five 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 (iOS or Android, and whether it is a phone or a tablet), 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.
• App use: while you are signed in, the app tells our server when you open it. It then checks in about every 15 seconds while the app stays open. We store when each visit started and ended, with your IP address. We also keep a log of what you do in the app, such as adding or deleting clothes, changing your profile, likes, follows and using the AI stylist, and your IP address is recorded with this log. Our team can see this log. We use it to help you when you contact support, to find problems, and to send fewer reminders and offers when you have not opened the app for a while.
• Purchases: your subscription status and purchase records. We also keep which paywalls and offers you were shown, what you tapped, how long you stayed on a paywall, and the plan and price involved. We keep your credit balance and a record of each time you get or use credits. If Apple or Google refunds you, we keep a record of the refund. Payments are handled by Apple and Google, so we do not see your card details.
• Cancellation answers: when you tap Manage subscription in the app, or open the screen the app shows after you turn off renewal, we ask why you want to leave. We keep the reason you pick and, if you choose “A feature I need is missing” or “Something else”, anything you type in the box. We also record which of these screens you saw and whether you took an offer or went on to the App Store or Google Play. We keep your answer even if you do not cancel. Firebase Analytics receives the reason you picked, but not what you typed.
• Support and feedback: what you write to us in the support chat, and the topic and text of feedback you send us. On iPhone, you can open the feedback form after you sign in by pressing and holding the Wdrobe icon on your Home Screen. Older versions of the app had a support form and a feedback page instead of the chat. We keep what was sent through them.
• Reports and blocks: if you report or block another user, we keep who you reported or blocked, the reason you picked and any note you wrote. Blocking someone also removes any follows between you.

We do not ask for your phone number. We do not store your conversations with the AI stylist: a conversation ends when you close the app. The one exception is a conversation you choose to send us, described in section 2. Apart from the short notes about your taste, the only other thing we keep from the chat is the outfit suggestions described above. We ask the stylist to write the occasion note in its own words and to leave out health and body details. We use the note to pick clothes that suit the occasion and to show the same suggestion again if you ask for the same thing. If you try the outfit on, we also use it to write a short internal description that helps the stylist find your saved outfits later.

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 and do not keep the one that failed. 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.

Photos of you for try-on: we store each photo of yourself that you add for try-on or body analysis: 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.

Body analysis: body analysis runs on a photo that shows you from the shoulders to below the hips, such as a full-body photo or one that ends at the knees. During sign-up it runs on the photo you add for your first try-on, if that photo can be used. AI estimates your body shape and proportions, such as your height, shoulder width, leg length and waist, and marks where your shoulders, waist and hips are on the photo so the app can show them as dots. We store the result and these points with your account. A new photo you add for body analysis is also saved as one of your try-on photos. Deleting the body analysis does not delete that photo; you can delete it on its own.

Try-on: to show clothes on you, we send the photo of you that you picked and the clothing images to an AI image provider. We store the image it returns, any in-between images made on the way, such as your clothes put together into one picture, and a copy of the result in Google Cloud.

Your clothes: we store the photo you add, a cut-out copy without the background, and a copy in Google Cloud for try-on. AI removes the background, or redraws the piece on a plain background if you choose the advanced option. It tags each piece with details such as type, colour, season and brand, and gives it a name and a short description. If one photo shows several pieces, AI redraws them laid out flat and splits them into separate items.

Outfit descriptions and search: AI also writes a short description of each saved outfit, which you do not see. We turn your clothing tags and these descriptions into number codes with Google, so the AI stylist can find your clothes and outfits. Both are deleted when you delete the item or your account.

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 and any thumbs up or down and reason you give. We do not record what you and the stylist write, unless you send us the conversation yourself, as described below. The outfit suggestions described in section 1 are kept separately. We use this record to look into errors and check the quality of AI results. Images are not copied into it. Most of it is deleted when you delete your account. If you delete a single colour or body analysis, its record stays until you delete your account.

Conversations you send us: after you give one of the AI stylist's replies, outfits or clothes a thumbs down, you can choose to send that conversation to our team. Before anything is sent, the app shows you what is included. We then receive 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, which kinds of cards the stylist showed and which outfit it suggested. We do not receive photos. Only some members of our team can read it (section 5), and we use it to find and fix the stylist's mistakes. It is deleted 90 days after you send it; if you send the same conversation again, the 90 days start again. 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 fixed 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, the types of clothing involved, the clothing set you chose (men's, women's or prefer not to say) and, for try-on, how much of the body the photo shows. 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. You can change your answer later in your profile. If your answer is “prefer not to say”, each colour analysis of your selfie also guesses whether the men's or the women's clothing set suits you better. Some new users see a sign-up screen that shows an outfit right after the colour result. Only that screen uses the guess, to pick which set to show first. If no guess can be made, we ask you instead, and you can switch to the other set with one tap. Everywhere else the app ignores the guess.

The guess is not shown to you and is not saved as part of your profile. It is not kept in our AI request record and is not sent to advertising or analytics tools. We keep only which outfit was added to your wardrobe on that screen, which shows which 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

Every member of our team who has an account on our admin panel can see the photos you upload and the images the app creates. We use this to moderate content and check the quality of AI results. Only team members with the owner, admin or developer role can read the AI stylist conversations you choose to send us (section 2).

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.

A public outfit shows in Discover and on your profile only if your profile is also public. If your profile is private, only your followers can see your public outfits. While your profile is private, a new follower has to send a request and you have to accept it. People who followed you while your profile was public stay followers until you remove them. Other users can see and like your public outfits, and with each outfit they see your name, username and profile photo. People without a Wdrobe account may also be able to see public outfits in Discover.

When you make an outfit public, people who see it also get a link to the photo of you the outfit was made from, and links to the original photos of its clothes, before we removed the background. This includes people who browse Discover without an account. If someone opens your public outfit from a shared link in the app, the app shows your photo next to the try-on image. When your wardrobe is public, signed-in users can get the original photos of your clothes, not only the cut-outs.

Even if your profile is private, other users can see your name, username and profile photo, how many followers you have and whether you subscribe. They can send you a follow request.

When you make an outfit public, Google Cloud Vision checks the outfit's try-on picture for adult or violent content, and OpenAI's moderation tool checks the names of the outfit and the clothes from your wardrobe in it. If a check fails, the outfit stays private. Our team may also review the outfit. These checks run only when you make an outfit public. If you rename a public outfit or one of its clothes later, the new name is not checked. Your name, username and profile photo, the separate photos of each piece of clothing, the clothes in a public wardrobe, and outfits or clothes you share by link are not checked before other people can see them.

You can report or block another user from their profile. To report someone, you pick a reason and can add a note of up to 500 characters. We store the report with your account and theirs, and our team reads it. Our team can then remove outfits or close accounts. When you block someone, their outfits stop showing in your Discover and yours stop showing in theirs, and any follow between you is removed. We do not tell the other person about a report or a block.

Sharing by link: if you share an outfit or a piece of clothing, we create a link on wdrobe.app. Anyone with the link can see that outfit or piece of clothing, even if it is private. A clothing link shows the piece's cut-out picture and its name, never your original photo. People who open a clothing link in the app while signed in can also see the piece's details, such as category, brand, colour, season and tags, and can save it to their favourites. A link does not make the outfit or your wardrobe public in Discover. We count how many times a link is opened, and we note which app you shared it with. A link stops working when you delete the outfit or piece of clothing, or your account. The picture can still load for up to an hour after that, and apps that already showed a preview of the link may keep it.

Favourites: other users can save your clothes. If someone saves one of your clothes to their favourites, we copy that item into their account. They can do this from a public outfit in Discover, from your public wardrobe or from a link you shared. We also make this copy if they try on a Discover outfit that includes the item. The copy includes the cut-out picture, your original photo of the item and details such as its name, brand and colour. The copy stays in their account if you later delete the item or your account.

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, new followers, follow requests and when someone accepts yours, free credits, replies from support, problems with a payment, notes that your subscription is about to end or has ended, messages our team sends to everyone, to groups of users or to you, and offers. You can turn most types off in Notification Settings. Replies from support have no switch there, and neither does the message that your look is ready (see below). These switches also cover some of our email: if you turn off Discounts, we also stop sending you offer emails, and if you turn off General, we stop most of our general emails too. You can turn off all push notifications 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. You can turn it off, together with all other notifications, in your phone's settings.

Notification list: notifications are also kept in a list inside the app, even if push notifications are off. A notification about a new follower shows that person's name, and it stays in your list if they later delete their account.

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. We never delete these copies. A copy stays after the outfit is deleted, after a profile photo is changed or removed, and after the account it came from is deleted, whether that is your account or the account of the person who liked your outfit or followed you.

Email: we send email through Amazon Web Services from noreply@wdrobe.app. We send a welcome email when you sign up, a code when you ask to delete your account, and our answer when you write to support. If you cancel a subscription or free trial, we may email you 2 days later with how many clothes, try-ons and outfits you have saved, and again 3 days before your access ends with an offer to stay. After a subscription or free trial ends, we may send up to three emails with offers to come back. Our team may also email news, offers and tips to groups of users. The automatic emails sent after you cancel, or after your subscription or trial ends, contain an unsubscribe link and a small image that tells us whether and when you opened the email. The unsubscribe link stops these automatic emails. Other offer emails, which our team sends to groups of users, do not have an unsubscribe link or this image. To stop all offer emails, turn off Discounts in Notification Settings. This also turns off Discounts notifications on your phone.

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, your install, and a short report each time you open the app. It also receives these events: sign-up and sign-in (with how you signed in, for example with Apple or Google), finishing setup, paywall views (with the screen that showed the paywall), taps on a subscription buy button, trial starts, subscriptions and credit pack purchases. Purchase events include the plan or pack, the price, the currency and the store's order number. While we test different paywalls, each event also says which paywall version you saw. 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 ID Apple gives to all apps from the same developer on your phone (IDFV), which is not the advertising ID. If you installed Wdrobe after seeing an ad, Apple may also send AppsFlyer a copy of its install report (SKAdNetwork). That report has no ID for you or your device. It only shows which ad campaign led to the install and a rough value for what you did in the app, such as starting a trial.
• TikTok gets install events and in-app events from AppsFlyer, server to server. These include sign-up, sign-in, paywall views, trial starts and purchases with their price. With them, TikTok gets your phone's advertising ID if AppsFlyer has it; on iPhone, that is only if you allow tracking. TikTok uses this to tell whether you installed Wdrobe after seeing or tapping a TikTok ad. On iPhone, Apple can also send TikTok its own install reports (SKAdNetwork) for installs that came from TikTok ads. These reports do not identify you. The app does not contain TikTok's software (no TikTok SDK).
• RevenueCat runs subscriptions. It receives your Wdrobe user ID, your AppsFlyer ID, device identifiers (on iPhone the IDFV, and the IDFA only if you allow tracking; on Android the advertising ID), your IP address and your purchases. On iPhone it also receives the Apple Search Ads token, so it can tell whether you came from an Apple Search Ads ad. It also receives how you found Wdrobe: for example the ad campaign or the wdrobe.app article or page 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, when you first open the app, it gets a token from Apple that shows whether the install came from an Apple Search Ads ad. This happens whether or not you allow tracking. We send the token to Apple to check it, and RevenueCat also checks it with Apple. We keep Apple's answer with your account. If the install came from one of our ads, the answer shows which campaign, ad group, keyword and ad it came from, the country or region, and whether you tapped the ad or only saw it.
• 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 your subscription status (free, trial or paid), which setup flow you went through, and for each purchase the product, price, currency and store order number. On Android it can read your phone's advertising ID, unless you have turned it off in your phone's settings. On iPhone it gets the advertising identifier (IDFA) only if you allow tracking when the app asks. We do not give it your name or email address.
• Store buttons and the download page: the App Store and Google Play buttons on wdrobe.app go through our download page at wdrobe.app/get, and shared outfit and clothing links send people there too. When someone on a phone or tablet goes from it to the App Store or Google Play, by tapping a button or because the page opens the store for them, we record a scrambled (hashed) form of their IP address, their country, the screen size, language and time zone, which store they went to, the page or campaign they came from, the first page of their visit and, if they came from a shared outfit or item, that link. On Android we also record the phone model and Android version, and on iPhone and iPad the iOS version. We do not record this for taps made on a computer or for visitors who use an anonymising service such as Tor; for these visitors the page does not send these details at all. 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 or item 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 and which links you tap. 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.
• 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.
• The first time the app opens: on every new install, whether or not you came from the website, the app sends us a random install ID it makes, whether you use an iPhone or an Android phone, the screen size and pixel density, the language, the time zone, the phone model and the system version. We record a hashed form of the IP address it connects from and, when we can, its country. We compare this with the visits recorded on the download page to guess whether the install came from the website. If we think it did, the app saves that guess, with the page or campaign, to your subscription record at RevenueCat. If you came from a shared outfit or item, the app opens it for you after you sign up. On Android, the app later sends where the install came from, as reported through AppsFlyer and Google Play: the source (for example our website, an ad, or no source), and the campaign and page if there was one. We store this with the same record only to check how often our website guess was right. The app sends these first-launch details from every country, but where the download page records nothing, there is nothing to match them to. The install ID is not linked to your phone, and a new one is made if you reinstall the app. These records are deleted after 180 days.
• Shared links and installs: if you open an outfit or item that someone shared on wdrobe.app and then install Wdrobe, we try to open that outfit or item for you after you sign up or sign in. On Android, the link is passed to Google Play when you go to the store. The app reads it from Google Play the first time it opens, and only if Wdrobe was installed less than a day ago. AppsFlyer's software in the app also reads this Google Play information. On iPhone, the link is saved with the download page record described above, and our server sends it back to the app if it can match your first launch to that record. This is a best guess, and it does not work where the download page records nothing. The link is kept with these records and deleted after 180 days. When someone opens a shared link, we only add one to that link's open count; nothing about the person who opened it is sent to us.

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 or this section gives a shorter time.

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, and a link you shared to it stops working. 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. Two kinds of copies are not deleted this way: the smaller copies made for notification pictures (section 7), and the copy someone else made if they saved one of your clothes to their favourites. Removing an item from your own favourites hides it, but its picture copies are not deleted.

AI stylist conversations you send us: deleted 90 days after you send them, or sooner if you delete them in the app.

Deleting your account: in the app, go to Profile, then Settings, then Profile Information. You can also open Profile Information by tapping your profile photo. Tap the bin icon at the top right, then Send Code. Enter the code we send to the email address on your account and tap Verify. Deletion 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, date of birth, gender, body type, clothing and style preferences, saved cities, notification token, device names and device IDs, the AI stylist's notes, the AI stylist conversations you sent us, the IP addresses on most of your account activity and your AI request record. Your outfits are removed from Discover and from the app, and links you shared stop working. If you cannot open the app, write to info@anemotech.com from the email address on your account. The full 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 username, age range, goals, how you heard about Wdrobe, your app store country, your subscription status and whether you used a free trial, the app version and platform you signed up on, which version of sign-up you saw and how far you got in it, when you last opened the app, your follower and following counts, how you signed in, and the Apple Search Ads token and Apple's answer described in section 8. We use these for statistics. Your username can also still appear in the follower and following lists of people you followed or who followed you.
• The dates and times of your visits and the type of each action in the app use log, such as adding clothes, making outfits and using credits. The IP address and other details are removed from most of it, but the IP address stays on the records of credits you used.
• The install record created before you signed in (section 1).
• Records of likes, follows and purchases, so that counts and our purchase records stay correct. Notifications other people got about your likes and follows, such as “Ada liked your outfit”, stay in their notification list with your name as it was then.
• Outfit suggestions we made for you, and your thumbs up or down on them. A suggestion can hold a short note about what it was for: what you typed in older versions of the app, or a short summary the AI stylist wrote.
• Support requests and support chat messages, feedback you sent, reports you made and what you wrote when cancelling a subscription in the app. Write to us if you want them deleted.
• Records of the reminders and offers we sent you, and whether you opened them.
• Clothes you saved from other people to your favourites, with their picture copies. If someone else saved one of your clothes to their favourites, their copy, with its photos, also stays.
• 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.

The records made when someone uses the download page at wdrobe.app/get, or when the app first opens (section 8), are not linked to your account. They are deleted after 180 days, whether or not you delete your account.

Deleting your account does not delete what our service providers in section 4 have already received, such as RevenueCat, AppsFlyer, Firebase and Telegram. They keep it under their own terms.

Apple and Google keep their own purchase records under their own policies, and RevenueCat, which runs our subscriptions, keeps its own records too. 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 Railway in Amsterdam, the Netherlands. Your photo files and generated images are stored with Amazon Web Services in Stockholm, Sweden. 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. Only team members with an admin panel account can see user data, and some data, such as AI stylist conversations you send us, is limited to the owner, admin and developer roles. 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. During sign-up we ask for your age range, and there is no option for people 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. If you choose the 13 to 17 age range during sign-up, the app asks you to confirm that you are at least 13 and that a parent or guardian has agreed to you using Wdrobe. You cannot continue with that age range without confirming. Some countries set a higher age for agreeing on your own, which in the EU can be up to 16.

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. The wdrobe.app website

You can read wdrobe.app without an account. The site uses Google Analytics and Cloudflare Web Analytics on every page and records store button taps, as described in section 8. It does not use advertising tools. It saves the first page of your visit in your browser, as described in the cookie policy.

Fonts and pictures: to show its typefaces and some of its pictures, the site loads files from Google Fonts (Google), Fontshare (Indian Type Foundry) and Unsplash. When a page opens, your browser connects to their servers, which receive your IP address and browser details.

Server logs: like any website, the servers that deliver wdrobe.app receive your IP address, browser details and the page you asked for. They use this to deliver the page and to keep the site secure.

Messages you send us: if you write to us, we use your message and your email address to answer you. If you use the contact form on wdrobe.app, we also keep your name, the company and topic you enter, the page and language of the site you wrote from, your country and your IP address. We use the IP address only to limit how many messages can be sent from one connection. Our team is told about each new message through Telegram (section 4). Write to us if you want your message deleted.

15. Changes to this policy

When we change this policy, we update the date on 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.

16. 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