Drobe Privacy Policy
Effective date: {{EFFECTIVE_DATE}}
Drobe lets you save your wardrobe from photos, get outfit suggestions for tomorrow's weather, and try selected clothes on your own photo with AI. This policy explains what personal data we process and why, who receives it, how long we keep it and how you can exercise your rights. Türkçe sürüm
1. Who is responsible
Drobe is published by {{CONTROLLER_NAME}}, an individual developer, who is the controller of your data.
- Email: iletisim@getdrobe.app
- Postal address: {{CONTROLLER_ADDRESS}}
2. In short
- We do not sell your data or use it for advertising, and the app contains no advertising or analytics tools.
- We do not read your device location; for weather we only use the city you pick from a list.
- Live scan frames are not stored; from a scan, only the clothing images you choose to save are kept.
- Virtual try-on is optional. Your photo is sent only when you tap "Üzerimde dene" (Try it on me), to an image-generation service provider that works on our behalf and is located outside Türkiye. You can switch try-on off in Profile → Hesap ve gizlilik. Try-on photos and results are kept on our server for at most 7 days. Where the app offers it, you can pick one of Drobe's AI-generated ready models instead of your own photo; your photo is then not sent at all.
- Free welcome try-on credits are given once per person. For that we use only keyed hashes (made with a secret key) of your email address, your phone's app-specific ID and your sign-up IP address, never the values themselves; the IP hash is deleted after 48 hours.
- You can delete your account in the app at any time, or request deletion on the web.
3. What we process and why
| Data | Purpose | Legal basis (GDPR Art. 6) |
|---|---|---|
| Email address, password (only a one-way hash is stored), account number | Create your account, sign you in, keep the account secure | Contract (Art. 6(1)(b)) |
| Session data (session id, expiry, hash of the refresh key) | Keep you signed in, sign-out and session security | Contract; legitimate interests (security) |
| Failed sign-in attempts (keyed hashes of the account and the IP address, times; in server memory only, 15 minutes) | Slow down password-guessing attacks | Legitimate interests (security) |
| Registration attempts (keyed hash of the IP address, times; in server memory only, 1 hour) | Stop extreme bursts of new accounts from one network | Legitimate interests (security) |
| Acceptance of the Terms of Use (the moment you accepted them when registering, and the version) | Be able to show you accepted the terms (including the 18+ rule) | Contract; legitimate interests |
| Clothing photos you save, the copies with a transparent background made from them for the outfit card's collage, and clothing details (name, brand, size, category, colour, style, warmth and rain suitability) | Build and show your digital wardrobe | Contract |
| Live scan frame (including the background) | Detect and crop clothes; the frame is not stored | Contract (you start the scan with "Taramayı başlat" (Start scanning); the frame goes only to our own server for the recognition you asked for) |
| The city you choose (fixed coordinates of the city centre) | Get tomorrow's weather forecast | Contract |
| Outfit suggestions, your like/pass votes and the forecast of the day an outfit was chosen for (temperature, precipitation; not a location) | Rank suggestions to your taste, avoid repeating outfits, swap a piece under the same rules | Contract |
| The outfit you mark as worn ("Bunu giyiyorum": its day, pieces and that day's forecast) and your optional "Dün nasıldı?" answer the next day (cold / fine / hot / did not wear it) | Improve suggestions from what you actually wore, work out your warmth setting | Contract |
| Warmth setting (at most ±3 °C; shown and reset in Profil) | Choose warmer or lighter outfits for someone who felt cold or hot | Contract |
| The optional reason you pick after passing an outfit (too formal, too casual, colours, too cold, too hot, dirty / not ironed), the piece you swap and the piece you mark "not ready" | Suggest similar outfits less often; leave a dirty or unironed piece out for a few days | Contract |
| During the closed test (pilot) only: your optional answer to "Without Drobe, would you have chosen a different outfit?" (yes / no) | Measure, in totals only, whether the app helps | Legitimate interests (improving the service) |
| The colour theme you pick (Profil → Tema; the theme's name only) | The theme is applied on your phone; the server copy measures, in totals only, which themes people like | Legitimate interests (improving the service) |
| The days you used the app (date only; one record per day, no time, screen or request) | Measure, in totals only, how many people use the app and how many come back the next day and a week later | Legitimate interests (improving the service) |
| Your Stil DNA quiz answers (which sample outfits you liked or passed, and when) | Show your style profile and rank suggestions to your style | Contract |
| The type of your plan for tomorrow (for example "Job interview") and its date | Pick that day's suggestions for the plan | Contract |
| The photo you upload for try-on (none if you pick a ready model), copies of the selected clothes and the generated result | Produce the try-on you asked for and show it to you | Contract (the virtual try-on service in the Terms of Use; you start each try-on and can switch it off in Profile → Hesap ve gizlilik) |
| Try-on job record (status, selected items, provider job number, consent version, timestamps, a one-way hash of the inputs) | Track the try-on and avoid charging the same request twice; open a finished result for the same photo (or model), pieces and settings again without a new credit | Contract; legitimate interests |
| Reports you send about an AI result (reason, optional note, review status) and, while they still exist, the photos of the reported try-on | Have a person review inappropriate or wrong results, improve filters | Legitimate interests (preventing misuse of AI output; Google Play's rules require us to act on reports) |
| Moderation decisions (the outcome of a report: no action / warning / restriction, lifting a restriction; date and the reviewer's short note) and whether the account is restricted | Decide consistently, see repeated reports, stop an abusive account from sending new try-ons and photos | Legitimate interests (preventing abuse) |
| A keyed hash of the email address of an account deleted while restricted, and the day of deletion (only in that case) | Stop a restriction from being bypassed by deleting the account and registering the same address again | Legitimate interests (preventing abuse) |
| Try-on credit counters | Apply free try-on credits and the system's daily spending cap, prevent abuse | Legitimate interests |
| When you first completed the Stil DNA quiz | Give the Stil DNA bonus try-on credit once per account | Contract |
| Email verification (when it was verified; only a hash of the one-time code, numbers of codes sent and attempts) | Confirm the email address is yours, give welcome credits to verified addresses | Contract; legitimate interests (preventing abuse) |
Welcome credit record: a keyed hash of your email address (spellings of the same mailbox — upper/lower case, +tags, dots in Gmail — count as one address), the day credits were first given, how many later claims were refused | Give free welcome credits once per email address | Legitimate interests (preventing abuse) |
| Device signal: a one-way hash, made on your phone, of the Android ID that is specific to this app (ANDROID_ID); the server keeps only a keyed hash of it | Hold welcome credits for a person to review when the same phone asks for them a second time | Legitimate interests (preventing abuse) |
| Sign-up IP address: only a keyed hash (for IPv6, of the first 64 bits) and the time of sign-up; the address itself is not stored | Hold welcome credits when many accounts are created from one address in a short time; sign-up and the app are never blocked | Legitimate interests (preventing abuse) |
| Server logs (request time, requested path without query parameters, status, duration) | Run the service, find errors, security | Legitimate interests |
If you register on the website you may optionally enter your name; the Android app does not ask for it.
Learning from use: "Bunu giyiyorum" (I'm wearing this), "Dün nasıldı?" (how was yesterday), pass reasons and "Bu parçayı değiştir" (swap this piece) are optional; none is needed to use the app. From them we derive a bounded, visible adjustment with ranking rules: your warmth setting stays within ±3 °C, is shown in Profil and can be reset; outfits like the ones you passed drop by a few points at most; a piece you mark "dirty / not ironed" is left out for 3 days (or until you mark it ready in Gardırop). None of this is sent to a third party. Pilot metrics are totals only (for example "share of outfits worn", "people back the next day"); no result is produced about a single person. For this we keep the days you used the app, as dates only (one record per day).
Style preferences: the Stil DNA quiz is optional. Its sample outfits are images prepared by Drobe, not your photos. Your style profile (for example "Minimal 45%") is not stored; it is recalculated from your answers each time. The "Women / Men / All" choice stays on your device. If you type your plan, the server maps the sentence to a plan type and discards it; only the plan type and date are stored, and each new plan replaces the previous one. You can delete your answers at any time in Profile → Stil DNA → "Cevaplarımı sil" (Delete my answers).
Protecting welcome credits: new accounts get a small number of free virtual try-on credits; each try-on costs us money, so these credits are given once per person. When email verification is on, the credits unlock once you enter the 6-digit code we email you; the rest of the app works without verification. If the same email address already received the credits (even through an account that was deleted and created again), the new account can use everything but does not get welcome credits a second time. If many accounts are created from the same phone or the same IP address in a short time, the credits are held until a person reviews them. An IP address alone is never a reason to block anyone: on school and work networks and with mobile operators many people share one address. These checks run automatically at sign-up; if you think one is wrong, write to iletisim@getdrobe.app and a person will review it.
Data we do not process: device location (GPS), contacts, microphone, advertising ID, payment details. The Android app has no advertising, analytics or crash-reporting tool.
Server error records: when an error happens on our server, a technical record is sent to the error-monitoring service Sentry so we can find and fix it: the type of error and the related lines of code, the request method and path (without query parameters) and the name of the requesting client (browser type, or the name and version of the network library the app uses; not your device model). Your email, IP address, account details, photos, request contents and the coordinates of your city are not included; text that looks like an email address or access key is removed before sending. Legal basis: legitimate interests (keeping the service secure and working).
4. AI processing
- Clothing recognition: a scan frame or uploaded photo is processed by models on our own server: the garment is cropped, its background removed, and category, colour and style are predicted. You can see and change the predictions. From each photo you save, a copy with a transparent background is also made and kept next to it; the outfit card uses these to lay the pieces out side by side, like a magazine page. Nothing is sent to a third party for this.
- Outfit suggestions: your clothing details, tomorrow's forecast, your like/pass votes, the outfits you wore, your warmth setting, the reasons you gave when passing and, if given, your Stil DNA quiz answers and the plan you chose are combined with explicit rules; "Neden bu kombin?" (why this outfit) shows only reasons that were used. These are suggestions; no automated decision with legal or similarly significant effect is made. The percentages in your style profile summarise your answers; they are not a scientific measurement.
- Photo safety check: before a try-on photo is sent to the provider, our server checks it automatically for nudity. A small copy is processed in memory only and not stored. Photos with explicit nudity are refused. Ready models are Drobe's own images; each goes through the same check once, when it is added to the app.
- Virtual try-on: the result is generated by AI; it is not a real photograph and may not show exactly how the garment would look on you.
5. Virtual try-on
You start each try-on: the request is sent when you choose your photo (or a ready model) and clothes and tap "Üzerimde dene" (Try it on me); the app does not ask for a separate confirmation each time. This is the virtual try-on service in the Terms of Use you accepted at sign-up; under those terms you may use only your own photo or photos you have permission to use. The image is generated by an image-generation service provider that works on our behalf and on our instructions and is located outside Türkiye (see sections 6 and 7). You can switch try-on off at any time in Profile → "Hesap ve gizlilik" (Account and privacy) → "Sanal deneme onayını geri al"; while it is off no try-on request is sent, and you can turn it back on there. This choice is kept only on this phone, under a one-way hash of your email address (not the address itself): it stays when you sign out and back in with the same account, and is removed when you delete your account in the app or uninstall the app.
Ready models: where the app offers it, you can pick one of Drobe's AI-generated ready models instead of your own photo. They are not real people and are marked "AI ile üretilmiş model" (AI-generated model) in the app. With a ready model the service provider receives the ready model's image and your selected garment images, not your photo; our server stores no photo of you, and the try-on record keeps only which model was used.
- The service provider receives only the photo and garment images (re-encoded, with file metadata such as location removed) and the garment category — never your name, email or account details.
- According to the provider's published terms, submitted images are used only for the request and deleted when it finishes (with an automatic clean-up within one day); with the method Drobe uses, the generated image is held there for 60 minutes after completion; request records without image data (time, parameters, status) are not deleted automatically; the provider states it does not use customer content to train models.
- The result, your photo and the garment copies are kept on our server for 7 days and then deleted automatically. You can delete them earlier from your try-on history.
- If a result is inappropriate, offensive or misrepresents a real person, use the Report button in the app.
How reports are reviewed, and account restriction: a person at Drobe reviews reports. If the images have not been deleted yet (at most 7 days), the reviewer may look at the reported try-on's photo, garment copies and result; for this a temporary copy is placed in a folder only the reviewer can access and is deleted once a decision is made. The decision (no action, warning or restriction), its date and a short note are kept with your account. If AI output is found to be misused (for example a try-on with someone else's photo without their consent), the account can be restricted: a restricted account cannot start new try-ons or upload or scan new photos; you can still see, edit and delete your wardrobe and try-ons, request your data and delete your account. The app shows the restriction with the message "Hesabın inceleme nedeniyle kısıtlandı" (Your account has been restricted after a review); to appeal, write to iletisim@getdrobe.app and a person will review the decision again.
6. Who receives your data
We do not sell your data or share it for advertising. Only these providers, acting on our behalf, process what they need to deliver the service:
| Provider | Receives | Why |
|---|---|---|
| Image-generation service provider (outside Türkiye) | Your try-on photo (or the ready model's image you picked) and the selected garment images (only when you start a try-on) | Generate the try-on image |
| WeatherAPI.com | Rounded coordinates of the chosen city and a date; nothing identifying you, the request comes from our server | Weather forecast |
| Hosting provider ({{HOSTING_PROVIDER}}) | All data held on the server | Infrastructure |
| Sentry | Server error records only (the technical records described in section 3, without identity data) | Find and fix errors |
| Cloudflare (R2 storage) | An encrypted daily backup of the database; the key is held only by us, not by Cloudflare. Photos are not backed up | Backup against data loss |
| Email delivery provider ({{EMAIL_PROVIDER}}) | Your email address and the email containing the verification code (only when email verification is used) | Deliver the verification code to you |
We may disclose information to competent authorities where the law requires it.
7. International transfers
Our servers are located in {{SERVER_COUNTRY}}. The image-generation service provider and its sub-processors operate outside Türkiye (including countries outside the European Union). When you use try-on, your photo (with a ready model, only your garment images) is processed abroad. Server error records are kept in Sentry's {{SENTRY_REGION}} region and encrypted database backups in Cloudflare R2 ({{BACKUP_REGION}}); verification emails are sent through {{EMAIL_PROVIDER}}. We rely on the following safeguard for these transfers: {{TRANSFER_SAFEGUARD}}.
8. How long we keep data
| Data | Retention |
|---|---|
| Account, clothes, clothing photos and their transparent copies, suggestions, votes, reports | Until you delete your account or the item |
| Stil DNA quiz answers | Until you delete your answers or your account |
| Outfits you wore, your "Dün nasıldı?" and pilot answers, pass reasons, swapped pieces, the days you used the app, the colour theme you picked | Until you delete your account |
| Warmth setting | Until you delete your account or reset it in Profil |
| "Not ready" mark | 3 days; you can remove it earlier in Gardırop |
| Plan for tomorrow (type and date) | Until you enter a new plan, remove it or delete your account (only the latest plan is kept) |
| Try-on photo, garment copies and result | At most 7 days (you can delete them earlier) |
| Try-on job record without photos | Until you delete your account |
| Moderation decisions and notes, restriction status | Until you delete your account |
| Copy of images taken to review a report | Deleted once the decision is made |
| Email hash of an account deleted while restricted | 12 months from the day of deletion; if an account is created with the same address, the restriction moves to it and the hash is deleted |
| Live scan frame, safety-check copy | Not stored (in memory only while processed) |
| Weather region cache | 30 minutes, without identity |
| Try-on credit counters | Kept after account deletion (see below) |
| Email verification code | Valid for 15 minutes and once; deleted when used, otherwise at most 1 day after it expires |
| Daily verification email counters (a separate keyed hash of the mailbox and a count) | 2 days |
| Device hash on a held account | Until the credit decision is made or you delete your account |
| When your email was verified, welcome credit status, when the Stil DNA bonus was given | Until you delete your account |
| Failed sign-in counters (keyed hashes of the account and the IP address, in server memory only) | 15 minutes |
| Registration attempt counters (keyed hash of the IP address, in server memory only) | 1 hour |
| Sign-up IP hash | 48 hours; if you delete your account earlier its link to the account is removed at once and the hash is still deleted after 48 hours |
| Welcome credit record: email hash | 24 months from the day credits were first given; kept after account deletion (see below) |
| Welcome credit record: device hash | 12 months from the day credits were first given; kept after account deletion |
| Server logs | {{LOG_RETENTION_DAYS}} days |
| Expired or signed-out session records | Deleted by an hourly clean-up |
| Server error records in Sentry | {{SENTRY_RETENTION_DAYS}} days |
| Encrypted database backups | Daily backups 7 days, weekly backups 4 weeks; deleted data remains in backups for at most about 4 weeks |
If deleting a file is interrupted, the system retries automatically.
9. Deleting your account and data
- In the app: Profile → "Hesap ve gizlilik" (Account and privacy) at the bottom → "Hesabımı ve verilerimi sil" (Delete my account and data) → enter your password → confirm.
- Without the app: follow the steps on the account deletion page, or email iletisim@getdrobe.app from your registered address with the subject "Account deletion".
Deletion removes your account, sessions, email verification data, clothes and their photos, suggestions and votes, the outfits you wore, your "Dün nasıldı?" answers, warmth setting, pass reasons, the days you used the app and your colour theme, Stil DNA answers and plan, try-on records, reports and the moderation decisions about your account; access to photos ends immediately and the files are removed by the clean-up queue. You can delete your account while it is restricted, too. Only these remain: the try-on credit counters (your former account number and how many credits were used; no email, name or photo) and, if your account received welcome credits, the welcome credit record (keyed hashes of your email address and your phone, the day the credits were first given and how many later claims were refused; it does not contain your email address itself, your name or your account number; the email hash is deleted after 24 months, the device hash after 12 months). We keep them, based on legitimate interests, so that deleting and re-creating an account cannot be used to get new free credits or bypass the system's spending cap. You can create an account again with the same address and use the whole app; only the welcome credits are not given a second time. If your account is restricted when it is deleted, a hash of your email address made with a separate key and the day of deletion are also kept for 12 months (no decision, note, reason or account number); during that time an account created with the same address starts restricted. We keep it, based on legitimate interests, so that a restriction cannot be bypassed by deleting and re-creating the account. The sign-up IP hash, no longer linked to any account, is deleted within 48 hours. Deleted data stays in the encrypted database backups for at most about 4 more weeks and is then removed by the backup rotation; backups are only used to recover from data loss. Images sent to the image-generation service are already deleted automatically under the provider's terms (see section 5); the request records left there contain no images, name or email.
10. Your rights
You can ask whether we process your data and for a copy of it, ask us to correct or delete it, object to or restrict processing, receive your data in a portable format, withdraw consent at any time (this does not affect earlier processing), and object to a decision based solely on automated processing. Under Turkish law (KVKK Art. 11) you can also learn the purpose of processing and the third parties data is transferred to, and claim compensation for damage caused by unlawful processing.
How: email iletisim@getdrobe.app from the address registered with Drobe, or write to {{CONTROLLER_ADDRESS}}. We may ask for information to verify your identity. We answer free of charge within 30 days. You may also complain to the Turkish Personal Data Protection Board or, in the EU/UK, to your local data protection authority.
In the app you can correct clothing details and delete individual clothes and try-on results.
11. Age limit
Drobe is only for people aged 18 and over; its Google Play target audience is "18 and over". Do not create an account if you are under 18. If we learn that an account belongs to someone under 18, we delete it; you can tell us at iletisim@getdrobe.app. The 18+ rule is part of the Terms of Use, which you must accept when you register; the time of acceptance and the terms version are stored with your account and deleted with it.
12. Security
- All traffic between the app and our server is encrypted with HTTPS.
- Your password is stored only as a one-way hash; your session key is encrypted on your phone with Android Keystore.
- Database backups are encrypted before they leave the server.
- In the app your photos open only with your own account; they have no public address.
- No system is completely secure. If a data breach occurs, we will inform you and the competent authority as the law requires.
13. Changes
When we change this policy we update the effective date and announce important changes in the app.
14. Contact
Questions and requests: iletisim@getdrobe.app