Who is responsible?
Stymigo is a personal wardrobe and outfit assistant. In this policy, Stymigo means the app and its website. Data controller: Ahmet Batuhan Çakmak.
Privacy and data requests: privacy@stymigo.com. General support: support@stymigo.com.
What information is processed?
The information depends on the features you use and the content you add.
| Information | Purpose |
|---|---|
| Account and session | Email address, user identifier, account status and session information; to sign you in, associate records with your account and manage the account. |
| Photos and item details | Clothing, care-label and brand-label photos you add; item category, colours, pattern, fabric, fit and similar attributes. To build your wardrobe, edit details and create outfits. |
| Style and usage preferences | Lifestyle, style directions, features you avoid, comfort preferences, favourite brands and approximate budget; to assess suggestions against your preferences. |
| Outfits and feedback | Saved outfits, wear records, dates, relevant occasion and weather context, feedback and notes; to remember choices and improve suggestions. |
| Derived images and assessments | Cleaned or edited item images, visual similarity vectors and pair assessments; to display photos and match clothing. |
| Technical and permission records | Capture, review and verification timings, retake counts, processing queues, errors, usage/quota records and permission decisions; for reliability, security, operation tracking and recording your preferences. |
| Support correspondence | Contact details, messages and attachments you send; to understand the issue and respond to your request. |
| Approximate location | Weather. If you allow location access, your device location is rounded to 0.1° (about 11 km) and used only to show the weather for that area. |
How is information collected?
Information is collected electronically through choices and details you enter, photos you take or select, the sign-in service and technical records created while the app runs. Some attributes and images are produced automatically. They can be wrong, and editable details can be corrected in the app.
Camera and photo access depend on device permissions. Starting with version 1.3, if you allow location access, weather is based on your approximate location: your device coordinate is rounded to 0.1° (about 11 km), sent only to our server for a weather request, used to fetch the weather for that area from Apple WeatherKit, and is not stored or logged by us. Weather data is provided by Apple Weather; the app shows the Apple Weather mark and a link to its data sources next to the weather. If you do not allow location access, the city in your device’s time zone is used instead; if that cannot be resolved either, Istanbul is used. Versions before 1.3 always used a fixed city coordinate configured on the server.
For product detection in a screenshot, the entire resized image can be sent before cropping to Anthropic. Other products, prices, seller names or personal details visible in that image are part of the content. This feature uses the item-analysis permission.
If you search for a city by name instead of using device location, the text you type is sent the same way to the GeoNames search service (geonames.org), only to answer that search. City data © GeoNames, licensed under CC BY 4.0.
Which services receive information?
Server services operate accounts, store data and provide the features below. The content shared depends on the operation.
- SupabaseEmail and account information, wardrobe data, photos, preferences and app records; for authentication, the database, synchronisation and private file storage.
- Hostinger · our serverClothing photos; for background removal and visual similarity vectors. Our hosting infrastructure also serves this website and separately managed recovery backups.
- AnthropicFor item analysis on the Pro plan, clothing and any label photos plus item details; screenshots for product detection. Also used for item analysis and outfit explanations when the Google route is unavailable.
- Google (Gemini)For item analysis on the Free and Plus plans (and on Pro after the first 60 items), clothing and any label photos plus item details; on Pro's first 60 items, the clothing photo to determine the category when it is left blank; for Turkish-language outfit explanations, clothing attributes and outfit context. Explanation requests do not include photos or an account identifier.
- OpenAIThe original clothing photo and editing instructions, to create an edited item image. This operation uses the OpenAI image-editing service directly.
- TypeSafeClothing attributes such as category, colour, pattern, texture, silhouette, fit and formality, plus outfit context, to rank outfit suggestions and assess how two garments work together. The request content does not include photos or an account identifier.
- Apple (WeatherKit)Weather (version 1.3 and later): your approximate location rounded to 0.1° if you allow location access, otherwise the city in your device’s time zone, plus time zone. The request is sent by our server, not your device, and contains no account identifier.
- GeoNamesCity search: the city name you type, sent by our server to find matching cities with their coordinates and time zones. No account identifier is sent.
- Open-MeteoWeather in versions before 1.3, and as a fallback if Apple WeatherKit or GeoNames is unavailable: the same approximate location or city coordinate plus time zone, or the city name you type. Open-Meteo’s own service retains request logs, including coordinates, for up to 90 days for troubleshooting.
- SentryCrash and error reports (version 1.4 and later; can be turned off in the app): technical error details such as the error stack, device model and app version, processed in the European Union by Functional Software, Inc. No account identifier, email address, photo or location is sent.
- Email servicesEmail address, message content and delivery information are processed by email infrastructure to deliver sign-in codes and handle support or privacy correspondence.
These services can have infrastructure in different countries. Depending on the feature, information may be processed outside your country. Providers’ own service records and retention practices are subject to their applicable service terms.
AI and device permissions
Use AI permissions in your profile to manage item analysis and item-image editing. Without permission for these photo-processing features, their associated sharing does not take place. You can save an item or edit its details manually without enabling these features.
Outfit ranking and pair assessment may send clothing attributes and relevant outfit context to TypeSafe, and Turkish-language explanations may send them to Google; when the Google route is unavailable, explanations are sent to Anthropic. The request content does not include photos or an account identifier. This sharing requires the “Outfit assessment” permission. You can manage it in Profile > AI permissions. Turning it off prevents new assessment requests from being sent to AI providers for this purpose.
Turning off a permission does not delete records produced earlier or content already sent. Revoking camera or photo access also does not remove saved photos. Use the deletion options below for stored data.
How long is information kept?
Account, wardrobe, photo, outfit and preference records do not have a fixed automatic expiry period. Records are kept to provide the service; you can initiate deletion of items or your account in the app. Technical records and support correspondence are retained separately for operation tracking, security and handling your request.
Active records and recovery backups are different. Previously created recovery backups are managed separately; account deletion does not automatically erase those copies. Shared attribute assessments and technical caches kept separately from account records may also fall outside the same deletion operation.
Providers’ own records and backups may have different retention conditions. Contact privacy@stymigo.com to ask about retention or deletion of your information.
Deleting your account and data
Go to Profile → My account → Delete my account and read the final confirmation. Deletion is irreversible; a waiting period with an account-restoration option is not offered.
Account deletion includes closing sessions, removing account-related photos and application records from active storage, and cleaning device copies. Recovery backups are managed separately as explained above. This does not mean every copy held by every provider is erased at the same moment.
If deletion does not finish, check the message in the app and retry, or write to privacy@stymigo.com. Uninstalling the app does not delete your server account. If you use Sign in with Apple, you can separately manage the app’s access in your Apple account settings.
Your data rights
Depending on applicable law, you can ask whether your data is processed, request information about that processing, learn its purpose and whether it is used accordingly, and learn which recipients receive it domestically or abroad. You may request correction of incomplete or inaccurate information; where the relevant conditions apply, request erasure or destruction and notification of those actions to recipients; object to an adverse outcome based solely on automated analysis; and seek compensation for damage caused by unlawful processing.
Send requests to privacy@stymigo.com. Information needed to confirm that a request relates to the correct account may be requested. Do not send a password, one-time sign-in code or identity document in your first message.
For information about personal data rights in Türkiye, see the Personal Data Protection Authority.
Website and technical records
The public marketing, support and privacy pages do not use cookies or load advertising pixels or visitor analytics. The administration panel uses necessary session cookies for sign-in and request security; behavior in that panel is not measured. Fonts, logos and page files are served from our own domain. Language selection is kept in the page URL; it does not use persistent browser storage.
The hosting infrastructure may process standard connection records, such as IP address, requested page, date/time, browser and response status, to deliver pages and maintain security. Technical measurements in the app are separate from website visitor analytics. When you open email or an external link, the relevant service’s data practices apply.
Notifications and optional usage measurement
The notification centre is available inside the app. Push notifications also require operating-system permission and your in-app category preference. If enabled, we store the device push address, platform, time zone and notification preferences. Notification text and a destination identifier are sent through Expo and Apple or Google push infrastructure. Wardrobe photos are not included in push content. You can turn notifications on or off in Profile → Notification preferences → Allow notifications. From version 1.4.1, the Wear reminder is also there; it is scheduled on your device and its content is not sent to push infrastructure. By default, notifications from our servers are not sent between 22:00 and 08:00 in your time zone; a notification that expires in that window may not be sent at all.
Usage measurement is off by default and separate from AI permissions. With your explicit permission, our own server processes account-linked screen and step names, random session and journey identifiers, completion or cancellation outcomes, limited error categories, app version and time spent while the app is in the foreground. Measurement events do not include your name, email, photos, brands, item identifiers, entered text or raw error messages. The management panel shows aggregate results.
Raw usage events are retained for up to 30 days. You can withdraw permission in Profile → Usage analytics. Collection stops on the device immediately; events for the account are deleted when the server receives the withdrawal. An offline change completes when connectivity returns. The record of your permission decision is retained separately. Declining does not restrict app features.
Crash and error reports (version 1.4 and later). When the app closes unexpectedly or an error occurs, we send the technical details of the error to Sentry so we can find and fix the problem: the error stack, device model, iOS and app version, time zone, the screen transitions shortly before the error, the addresses and status codes of network requests, and whether the session ended without a crash. Email addresses, account and item identifiers, photos, location and the parameters and contents of network requests are removed from reports; IP addresses are not stored, and reports are not linked to your account or used for advertising or tracking. A randomly generated installation identifier that is not linked to your account may be used to measure app stability. Reports are processed in the European Union (Frankfurt) and kept for up to 90 days. You can turn crash reports off at any time in Profile → Privacy and support → Crash reports; while they are off, no report is sent.
Security and updates
Account-based access controls, private file storage and time-limited photo links are used. These measures are not a guarantee that errors or unauthorised access can never occur.
This policy is updated when features, providers or data practices change. Its latest update date appears at the top. Reading this page does not itself grant permission for AI sharing.