Legal

Privacy policy

Your wardrobe is yours. Here's what we collect, why, where it goes, and how to delete it.

Last updated 7 November 2026

In short — full detail below

  • You can use Kleidly without an account. Your wardrobe is then stored under a guest profile, not on your phone alone.
  • Your photos are used to build your wardrobe. They are analysed by an AI service on our behalf, never shown to other users, never sold, never used for advertising.
  • We name every provider that touches your data. Some of them are outside the EU.
  • Delete your wardrobe, account or guest profile from inside the app, any time.

Who we are

Kleidly is the product; it's currently operated by an individual developer, John Okoroafor — not a registered company. John Okoroafor is the data controller (under the GDPR) for the processing described here, contactable at Margarete-Steiff-Str. 9, 80997 München, Germany (see our legal notice) and at privacy@trykleidly.com.

Using Kleidly without an account

You don't need an account to start. When you first open the app it creates a random ID and stores it on your phone. Everything you add is saved on our servers under that ID, and processed exactly as it would be for an account holder — including the photo analysis described below. The ID isn't linked to your name, email or phone number.

  • If you later create an account, that same wardrobe becomes your account.
  • To delete a guest wardrobe, use You › Delete my data in the app, or email us.
  • A guest profile that never had anything added to it is removed after 30 days.

What we collect

Your clothesThe photos you add, in full — they may show you, your surroundings, or other people — plus what our systems and you record about each piece: type, colour, pattern, fabric, brand, season, layer, cut, how it's worn, where the garment sits in the photo, a short technical description used to generate a studio image, and how often you wear it.
Style inspirationImages you save to your style board, and the mood tags and captions generated from them.
Style profileA short summary and a set of style tags you can edit, plus a longer internal description of your style that our systems write and use to shape suggestions. It's not shown in the app, but you can ask for it. Also a short list of what we've learned from your feedback, which you can see and clear in the app.
Outfits and feedbackThe outfits suggested to you, which ones you saved or wore and when, the ones you turned down, and any reason you picked or note you typed. We also keep any fit previews made of them, and the reasons or note you give if you report one as wrong. What you type into “Describe my day” is sent for the suggestion but not stored word for word: we keep a one-line summary of what you asked for with each look suggested, and the stylist's reply. Outfits you log yourself are kept the same way; a photo you log one from is only used to find its pieces, then deleted.
Account detailsOnly if you create one: your name, your email and a password we store only as a one-way hash. If you sign in with Apple or Google instead, we receive from them your email (with Apple, possibly a private relay address that forwards to you), your name if you chose to share it, and an ID that identifies you to Kleidly. We store that ID to recognise you next time. We never see your Apple or Google password. An account made this way has no Kleidly password until you set one.
LocationIf you allow location access, the app sends your current position when you open it, so today's pick can match the weather. We keep only the most recent position, not a history. You can switch to a typed city in You › Weather & location instead.
Settings and deviceLanguage, temperature unit, timezone, notification preferences, how you dress, your work days, and a push-notification token for your device.
Usage stats, only if you turn them onWhich screens are opened and which features are used, and app performance timings. They're off until you switch on Usage stats on the app's last welcome screen or under You › Settings › Privacy, and switching them off again also clears what your phone hadn't sent yet (what was already sent is kept as described under “Where it lives”). Tied to a random app-instance ID, not to your name or email, and we don't use your device's advertising ID. See “Who we share with”.
Crash reportsWhen the app crashes or hits an error: device model, OS version, app version, what went wrong and where in the app it happened. Never your photos or what you type. Tied to a random app-instance ID, not to your name or email.
App useOur servers note the days you use the app and which features you use, so we can count how Kleidly is used. We only look at totals.
Technical logsOur servers record each request: IP address, time, the endpoint called, and error details. Used for security, rate limiting and fixing problems.

Not your contacts, not your calendar, not your camera roll — only the photos you pick on purpose.

Your photos and AI

  • Each photo is analysed by an AI service — Google's Gemini API, processing on our behalf — to identify the garments in it, label them, and write the technical description mentioned above.
  • From that photo Kleidly generates a new, AI-drawn “studio” image of each garment on a plain background. It's an approximation; the app keeps your original photo and lets you choose which to display.
  • If you ask for a fit preview, Kleidly draws one AI image of the whole outfit on a plain, faceless form, from your pieces' studio images (or their photos, where there's no studio image yet). It shows the outfit, never you.
  • Outfit suggestions, your style summary, inspiration captions and the “Stylist” replies in “Describe my day” are all produced by the same AI service from your wardrobe data and what you type. The Stylist is an AI, not a person.
  • We don't train AI models on your photos or data, and our provider's terms don't allow it to use them to train its models either.
  • We use feedback on suggested outfits (what you save, wear or turn down, and why) to improve Kleidly's suggestions, for you and for everyone. Our team may review suggested looks to check their quality. They see the pieces (as studio shots or cut-outs), any fit preview of the look, the occasion and weather, a short summary of what you asked for and any reason or note you gave, never your full photos, your name or your email. You can object to this (see Your choices and rights).
  • Otherwise, our staff only look at your photos when you ask for support, when we investigate misuse, or when it's needed to keep the service running.

Our legal bases

Under EU data protection law, here's why we're allowed to process each thing:

  • To run the app you asked for (our contract with you): your account details, the clothing photos and wardrobe you build, the AI analysis and studio images made from them, your style profile, and the outfit suggestions. These are the service itself — we can't provide it without them.
  • Your consent: sharing your device location for the weather-based pick, usage stats in the app, and joining the waitlist. You can withdraw any of these at any time (turn off location in your settings, switch off Usage stats under You › Settings › Privacy, or ask us to remove your address), and that doesn't affect anything we did lawfully beforehand.
  • Our legitimate interests: keeping the service secure and working (technical logs, rate limiting), fixing crashes, answering your support messages, counting how the app is used, and improving Kleidly's suggestions from the feedback you give on outfits, including our team reviewing suggested looks — weighed so they don't override your rights.

Crash reports are sent on our legitimate interest in keeping the app working. You can object by writing to privacy@trykleidly.com. The same goes for how we count app use.

Who we share with

These providers process data on our instructions, under contracts that limit them to serving us:

SupabaseDatabase hosting, Frankfurt, Germany. Holds everything except image files.
CloudinaryStores and delivers your photos, studio images, fit previews, inspiration images and support screenshots. United States.
RenderRuns our servers. Uploaded photos pass through it briefly before storage. EU region.
Google Gemini APIThe AI analysis described above. Receives your photos and what you type in the app.
Apple and Google sign-inOnly if you use “Sign in with Apple” (iPhone) or “Continue with Google”. Apple or Google confirms who you are and passes us the details above; they learn that you use Kleidly. When you delete an account that uses Sign in with Apple, we tell Apple to end Kleidly's access to your Apple ID.
Google FirebaseDelivers push notifications, and collects the usage, performance and crash data described above.
ResendSends our emails: welcome, password reset, account-deletion confirmation, support replies and waitlist confirmations. It also keeps the waitlist's addresses so we can send news about Kleidly. We don't track opens or clicks.
Microsoft (Outlook)Our support and waitlist notification emails land in a Microsoft-hosted inbox that we read and reply from.
Open-MeteoWeather. Receives coordinates or a city name, never your identity.
CloudflareHosts this website and sees the IP address of visitors. Its Web Analytics counts visits to this website without cookies and without identifying you. Also runs Turnstile, the bot check on our contact and waitlist forms, which looks at your browser and IP address when you use one of those forms — see Cloudflare’s Turnstile Privacy Addendum.
UmamiCounts visits to this website and clicks on its buttons, such as the app store badges, without cookies and without identifying you.

Our database and our servers are hosted in the EU. Your image files are stored by Cloudinary in the United States. Google (Gemini and Firebase), Cloudinary, Resend, Microsoft, Cloudflare and Umami are US-based and may process the data they receive outside the EU; for those transfers we rely on safeguards recognised under EU law — the EU–US Data Privacy Framework and/or the EU standard contractual clauses.

Beyond these providers we only disclose data if the law requires it, to protect our rights or users, or as part of a sale or merger of the business (we'd tell you first). We don't sell personal data and don't share it for anyone's advertising.

Where it lives, and for how long

  • Data is encrypted in transit. Our database and file storage encrypt data at rest.
  • Your wardrobe is kept while your account or guest profile exists. Removing a piece hides it from your wardrobe and outfits at once; its photo and details are deleted together with your account or profile.
  • Unsaved outfit suggestions are deleted after 30 days, or after about two months if you made a fit preview of one. Saved or worn outfits stay with your wardrobe. Suggestions you turned down are kept for 180 days, with any reason or note you gave, to improve the suggestions.
  • Fit previews are deleted with their outfit. If you report one as wrong, its image is deleted straight away; the reasons and note you gave stay with the outfit.
  • Deleting your account or profile removes your wardrobe, photos, outfits, history, style profile, inspiration board, settings, push tokens and any Apple or Google sign-in link. It's permanent: your data is deleted from our systems straight away.
  • Usage data is retained for 2 months, and crash reports for about 90 days, by Google Firebase.
  • App use is kept for about a year.
  • Technical logs are kept for a short period for security and debugging.

Your choices and rights

  • Permissions are yours. Camera, photos, location and notifications can each be declined, and the app still works — you can type a city instead of sharing location, and add photos from your library instead of the camera.
  • Delete anything — one piece from its detail screen, your saved outfits, your inspiration images, or everything at once: You › Delete my data (step by step).
  • Correct your name and email in You › Account; correct any tag on any piece in the app.

Under EU law you have the right to: access — request a copy of the personal data we hold about you; rectification — fix anything inaccurate; erasure — have your data deleted; restriction — ask us to pause processing while something is being sorted out; portability — receive your data in a portable form; and objection — object to processing based on our legitimate interests. Where we rely on your consent (location, usage stats, the waitlist), you can withdraw it at any time, and that doesn't affect anything we did lawfully before you withdrew. You can also complain to a data protection authority — in Germany, the authority of the state where you live. Providing data is voluntary; without your photos the app can't build a wardrobe.

Kleidly is for people aged 16 and over. If you believe a younger person has given us data, tell us and we'll remove it.

If we change this policy, the new version and its date appear here.

The waitlist

If you join the waitlist on this website, we store your email address to send you a confirmation and news about Kleidly, such as when it launches. Alongside the address we note which part of the site you signed up from, the language of that page so our emails reach you in it, the page that linked you to us, and any campaign tags in the link you followed (UTM parameters), to see what's working. The basis is your consent, given when you submit the form.

We keep your address until you ask us to remove it or use the unsubscribe link in one of our emails. Email privacy@trykleidly.com and you're gone, no questions.

This website

This website shows no ads and uses no advertising or tracking cookies. Cloudflare Web Analytics and Umami count visits and button clicks without cookies and without identifying you, on our legitimate interest in seeing what brings people to Kleidly (see “Who we share with”). When you tap a store badge, the store is told the visit came from this website.

Your browser's local storage keeps two things, and only after you act: the language you pick in the language switcher, so a return visit opens in that language, and — once you join the waitlist — your email address, so the page can show that you're already signed up. Neither is sent to us, and clearing this site's data in your browser removes both.

Support messages

When you write to us through the app or this site we store your name, reply-to email, topic, message and any screenshot you attach, and a support reference. The in-app form can also include the app version, OS version and how many pieces are in your wardrobe — you can switch that off before sending. Only the people who handle support can see them, and we use them just to investigate and answer your request. Support messages are stored and answered from our support inbox. We keep them so we can refer back if you write again; ask and we'll delete them.

Contact us

privacy@trykleidly.com.