Privacy Policy

In short: You can use Modadrop without an account; an account is optional. Your tracked list and brand choices stay on your device. If you sign in, your email address and tracked list are saved to your account. Beyond that, our server holds your email address if you gave it for a price alert, and a device-specific notification identifier if you allow push notifications, plus your anonymous install identifier and subscription record if you buy a subscription. Usage statistics (PostHog, hosted in the USA) and ad measurement (Meta and TikTok) start only if you allow them; if you do, the id, brand and price of products you view and track, and purchase events, are sent to those companies. We collect no location, we never share your email address or account with ad companies, and we do not sell data.

1. Who is responsible

The data controller is the operator of Modadrop, called “we” below. For any privacy question or request: support@raizeka.com.

2. What is kept on your device

The following is held in your device's own storage and is deleted when you remove the app. Some of it is also copied to our server in the cases described in section 3 (signing in, notifications, price alerts); exactly what goes is listed there.

the products you follow, the sizes and colours you picked, and your target prices;
the brands you follow, your filters, your language and market (country) choice, your lists and your recent searches;
a randomly generated install identifier (a UUID) for this installation. It contains nothing about who you are (see section 3).

When you scan a barcode or QR code, the camera image is processed on the device; only the resolved product link reaches our server. We do not record or upload photos or video.

3. What reaches our server

Stylist alarms — optional: If you save a Stylist search as an alarm, its filters (product type, colour, price range, size and so on), its short description and the push token it notifies are stored on our server. Deleting the alarm in the app deletes the record.
Stylist (search assistant): The request you type into the Stylist, or the photo you pick, is sent through our server to an AI provider (Anthropic or Google, via OpenRouter) to work out what you are looking for; the answer is turned into search filters only, and the products come from our own database. Requests and photos are not stored on our server. The app asks you before a photo is sent. If someone else is in the photo, get their permission first.
Account — optional: You do not need an account; every feature of the app works without one. If you sign in (with a one-time code sent to your email, or with Sign in with Apple) we store: your email address (with Apple this may be a relay address Apple issues to hide your real one), your sign-in method and the user number Apple generates for you for this app, a hash of your session key so we can recognise your session (not the key itself; valid for at most 90 days), and a copy of the tracked list on your device at the moment you sign in (product ids, sizes, target prices). Even if Apple offers to share your name, your name is not sent to our server. With email sign-in, a six-digit code valid for 10 minutes is sent to your address; we store a hash of the code, not the code. To stop codes being sent to one address too often, the address, the time of the last send and an attempt counter are kept as well. You can delete your account from inside the app (section 10).
Email address (price alert) — optional: Stored when you type it into the app yourself to set up a price alert, alongside the ids, sizes and target prices of the products you follow and your language choice. Single purpose: sending you a price-drop email.
Notification identifier (push token) — optional: If you allow push notifications, we store the notification identifier Apple or Google issues for your device, the platform name (ios/android), your language choice, your device's time zone (for example Europe/Istanbul) and the ids, sizes and target prices of the products you follow — so an alert can be sent to the right device about the right product. We also store your notification preferences (which kinds of alert you want, the minimum discount and your quiet hours), used only to avoid sending alerts you switched off. The time zone is used only to avoid sending notifications during quiet hours: the ones you chose in the app or, if you never chose any, between 22:00 and 08:00 your time. This identifier contains no name, email address or phone number.
Install identifier — if you buy a subscription: So that your subscription can follow you without forcing you to create an account, the random install identifier generated on your device is sent to our server at purchase time; the same identifier is also passed to Apple or Google with the purchase, so the purchase can be tied to this installation. It is not linked to a person: it has no connection to your name, email address or phone number, it is not an advertising identifier, and it is not shared with advertising or analytics providers. Its only job is to say “this subscription belongs to this installation”. One subscription can be linked to at most 5 installations, a limit that exists to prevent abuse. After a purchase it is also sent with your notification sync, together with a signed token proving this installation owns the subscription, so that alerts follow what you have paid for. If you never buy anything, it never leaves your device.
Proof of purchase and subscription status: When you buy, the app sends the store's proof of purchase to our server so we can verify it: on iPhone the transaction record signed by Apple, on Android Google's purchase token. We verify Apple's record and read the details from it; we store Google's token so we can look the subscription up again later. From these we keep the product you bought, the state of the subscription (trial, active, cancelled, expired, refunded), its start and end dates, the store's transaction identifier, and whether the purchase was made in a test environment. We keep this to decide whether Premium is on, to switch access off on a refund or cancellation, and to keep the records the law requires.
Store country: The country code of your App Store / Play account (for example TR, GB). It determines which prices and which plan structure apply. It is not location data — it does not say where your device is.
Technical server logs: Every time the app talks to our server, a short-lived record is left in our infrastructure provider's logs: IP address, timestamp, the address requested and any error. These exist for security and debugging. We do not copy them elsewhere, build profiles from them or use them for advertising. Our own database stores no IP addresses: to rate-limit product-link lookups and email sign-in requests we keep only a salted hash of the IP address (a one-way value that cannot be turned back into the address) for at most one day.

4. Payments

Subscription purchases run entirely through Apple or Google. We never see and never store your card number, your name, your billing address or your payment method. All we receive is the proof of purchase and subscription status described in section 3. In that transaction Apple and Google act as independent controllers under their own privacy policies.

5. Usage statistics and ad measurement

We ask first. The app asks for your permission before it starts any of the three services below. If you say no, PostHog, Meta and TikTok are never started and nothing is sent to them; nothing about the app changes — tracking, notifications and price history work exactly the same. You can change your decision later from inside the app. On iPhone, Meta and TikTok additionally need iOS's own “tracking” permission; without both, neither kit starts.

In app versions released before this permission screen, PostHog runs without asking; Meta and TikTok start on iPhone only if iOS tracking permission was granted, and on Android as soon as the app opens. Once you update, the choice is yours again.

Separately, our own server keeps a plain daily count of how many times the app is installed, opened and opened from a notification, how many installs reach key steps (for example the feed loading, a product being tracked, a later return) and how often something goes wrong (for example a screen failing to load, a search finding nothing, or repeated taps on something that did not respond), per platform and app version. It is a number, not a record: no identifier, no IP address, no search text or product, nothing that points to you or your device, and it is never sent to anyone.

Usage statistics (PostHog) — only with your permission

We use PostHog to see which parts of the app are used and where people get stuck. What is sent: the screens you open, the buttons you tap, the app being installed, opened and sent to the background; a few key events — viewing a product, tracking or untracking it, moving on to a brand's site, setting a price alert, searching, finishing the introduction, buying a subscription — and, on product events, the product's id, brand and price (for a search only the length of the query is sent, never the text); your app language, chosen market, whether you are a subscriber and how many products you track; your device model, operating system and app version; and, if the app crashes or hits an error, an error report (the error's type, message and the screen it happened on). We also record a session replay showing how the screens are used; in it, everything you type into a text field — your email address, your search text — is masked and cannot be read. All of this is sent with a random anonymous analytics identifier generated on your device; it is not linked to your account, name, email address, notification identifier or advertising identifier. The data is held on PostHog's servers in the United States and your device's IP address is not stored. We do not use it for advertising, combine it with other companies' data, or sell it.

Advertising identifier and app events (Meta, TikTok) — only with your permission

We promote the app with Meta (Facebook/Instagram) and TikTok ads. To measure which ad works we use these two companies' software development kits (SDKs). If you allow it, they share with Meta and TikTok: your device's advertising identifier (IDFA on iPhone, the Google advertising ID on Android); the fact that you installed and opened the app; and events such as viewing a product, tracking it, moving on to a brand's site, searching (only the length of the query) and finishing the introduction — product events carry the product's id, brand and price; and buying a subscription (Meta's kit records store purchases by itself: product, amount and currency; TikTok is sent the code of the plan bought). Your IP address, device model and operating system version reach them in the process.

iPhone: besides the app's own permission screen, you must also allow it in iOS's “tracking” prompt; if you choose “Ask App Not to Track”, neither kit is started. You can change your decision at any time in Settings → Privacy & Security → Tracking.
Android: the kits start only if you allow them on the app's permission screen. You can also reset or delete your advertising identifier in the Ads section of your phone settings (on most devices Settings → Google → Ads); once deleted, the kits cannot recognise your device by it.

This measurement shows which ad an installation came from and what is done in the app, not who you are. Your email address, account and notification identifier are never shared with Meta or TikTok; your tracked list is not sent to them as a whole, but if you allowed it, each product you view or track is reported individually through the events above. We show no ads inside the app. Meta and TikTok also process this data under their own privacy policies.

Our website: Meta Pixel (only /indir, when you arrive from a Meta ad)

Our website carries no analytics or advertising code, with one exception: the download page opened from the link in our Meta ads (its address starts with /indir?p=meta_…). That page loads the Meta Pixel and tells Meta that the page was viewed, that the App Store or Google Play button was tapped, and which ad campaign the visit came from; your IP address, browser details and a cookie Meta sets in your browser reach Meta in the process. Visitors who reach the page any other way do not get the Pixel. You can block cookies in your browser or use Meta's own ad settings.

6. What we do not collect

No precise or approximate location, no contacts, no photos. We do not share your name, email address, account or notification identifier with our analytics or advertising providers. We do not link usage statistics to who you are. If you did not give permission, the app sends nothing to PostHog, Meta or TikTok. There are no ads inside the app. We do not sell your data.

7. Price data

Prices are collected from brands' publicly accessible websites and refreshed roughly every 90 minutes; a purchase is always completed on the brand's own site. Modadrop is not affiliated with any brand. Once you move to a brand's site, that site's privacy policy applies.

8. Who processes your data

We do not sell data. To run the service we use these providers:

Hetzner (Helsinki, Finland) — the server hosting our database. Accounts, sessions, email addresses, notification identifiers, install identifiers and subscription records live here.
Vercel (Vercel Inc., USA) — the platform running the website and the app's APIs; technical server logs are produced here.
GitHub Actions (GitHub / Microsoft, USA) — where our price collector and alert sending run.
Apple (APNs) and Google (FCM) — the infrastructure that delivers push notifications to your device; the notification identifier and the alert text pass through them.
Resend (USA) — the provider that sends sign-in code emails and price-alert emails; your email address and the email's content pass through it.
Apple — if you choose Sign in with Apple, Apple verifies who you are and passes us only the user number and email address described above. Apple acts as a controller in its own right in doing so.
Apple and Google — subscription sales and verification. On the payment side these two act as controllers in their own right, not on our behalf.
OpenRouter (OpenRouter Inc., USA) and the Anthropic (USA) / Google (USA) models it routes to — to turn a Stylist request or photo into search filters (section 3). Processed on our behalf; not stored on our server.
PostHog (PostHog Inc., USA; data hosted in the USA) — with your permission, usage statistics, error reports and session replays (section 5). Processes it on our behalf and only for us.
Meta (Meta Platforms Ireland Ltd., Ireland / Meta Platforms, Inc., USA) and TikTok (TikTok Technology Limited, Ireland / TikTok Pte. Ltd., Singapore) — ad measurement (section 5), only with your permission; Meta also for the Pixel on the /indir page. These two companies also process what they receive under their own policies and in their own right.

Beyond these, we share data only where we are legally obliged to (a lawful request).

9. How long we keep it

Account and the tracked list saved to it: until you delete the account. Sessions are valid for at most 90 days; signing out deletes the session record at once.
Email sign-in code record: a code expires after 10 minutes and is voided the moment it is used. The address, the time of the last send and the send counter are kept to limit abuse; write to support@raizeka.com if you want them deleted.
Price-alert email address and alert list: until you delete it. The “unsubscribe” link in an alert email, or a message to support@raizeka.com, is enough.
Notification identifier and alert list: as long as the device keeps receiving notifications. When you revoke notification permission or remove the app the identifier becomes invalid; Apple or Google tell us so on the first send attempt and the record is deleted from our server automatically.
Subscription and installation records: while the subscription lasts, and afterwards for as long as our tax and accounting obligations require (10 years). We can break the link between an installation and a subscription earlier on request.
Technical server logs: for the provider's own retention period; we do not archive them separately. IP hashes kept for rate limiting are deleted after at most one day.
Usage statistics (PostHog): events for at most 12 months, session replays for at most 90 days; then deleted automatically.
Ad measurement (Meta, TikTok): we do not keep this data on our own server. How long Meta and TikTok keep it is set by their privacy policies.

10. How to delete your data

Account: “Delete my account” on the account screen (under the Account tab) deletes your account, your sessions and the tracked list saved to it from our server, immediately and permanently. Removing the app does not delete the account. If you cannot reach the app, write to support@raizeka.com from the address on the account.
Price-alert email: the “unsubscribe” link in your alert email deletes the address and the tracked list attached to it from our server. If you do not have the link, write to support@raizeka.com.
Notifications: revoking notification permission in your phone settings, or removing the app, invalidates the identifier; the server record is deleted automatically on the next send attempt.
Everything on the device: removing the app deletes your tracked list, your preferences, the install identifier and the anonymous analytics identifier. If you reinstall, a new analytics identifier is generated and is not linked to the old one.
Usage statistics and ad measurement: withdraw your permission from inside the app; on iPhone you can also switch off Modadrop's permission in Settings → Privacy & Security → Tracking, and on Android delete the advertising identifier in your phone settings. For data Meta and TikTok already hold, you can also use their own privacy settings.
Subscription record: to cancel, use your store account settings (see the Terms of Use). If you want the record deleted, write to support@raizeka.com and we will delete everything except the minimum we must keep for accounting. For us to act on the request you need to send us the install identifier shown in the app or the store transaction id (it is on your Apple/Google purchase receipt) — we have no other way of knowing which record is yours.

11. If you live in the EU or EEA (GDPR)

This section applies to users in the European Union and the European Economic Area under the General Data Protection Regulation. The controller is named in section 1.

Purposes and legal bases:

Providing your account (email address, sign-in method and user number, sessions, the tracked list saved to the account, the sign-in code record) — performance of a contract, Art. 6(1)(b): opening the account you asked for and recognising you. The counter that limits code sends — legitimate interests, Art. 6(1)(f): preventing abuse.
Sending price-drop emails (email address, tracked list) — consent, Art. 6(1)(a). You can withdraw consent at any time; the “unsubscribe” link in the email is enough.
Sending push notifications (notification identifier, platform, language, time zone, notification preferences, tracked list) —consent, Art. 6(1)(a), given by granting notification permission on the device and withdrawn in the same place.
Providing and maintaining the subscription (install identifier, proof of purchase, subscription status, store country) — performance of a contract, Art. 6(1)(b). Without this data we cannot switch Premium on.
Keeping subscription records — legal obligation, Art. 6(1)(c) (tax and accounting law).
Preventing abuse (capping how many installations one subscription can unlock) — legitimate interests, Art. 6(1)(f).
Security and debugging (technical server logs, IP hashes for rate limiting) — legitimate interests, Art. 6(1)(f): keeping the service up and protected against attack.
Usage statistics, error reports and session replays (PostHog) — consent, Art. 6(1)(a), given on the app's permission screen and withdrawable at any time from inside the app.
Ad measurement (sharing the advertising identifier and app events with Meta and TikTok) — consent, Art. 6(1)(a), given on the app's permission screen and, on iPhone, also in the iOS tracking prompt; withdrawable at any time.
App versions released before the permission screen — in those, PostHog and ad measurement on Android rest on legitimate interests, Art. 6(1)(f): fixing the app and measuring which installations our ad spend brings in. To object under Art. 21, update the app and decline, delete the advertising identifier on Android, or write to support@raizeka.com.
The Meta Pixel on /indir (visitors arriving from a Meta ad) — legitimate interests, Art. 6(1)(f): measuring whether our ads turn into downloads. To object, block cookies in your browser or write to support@raizeka.com.

Your rights. You have the right of access (Art. 15), rectification (Art. 16), erasure (Art. 17), restriction of processing (Art. 18), data portability (Art. 20) and objection (Art. 21), and where processing rests on consent you may withdraw it at any time (Art. 7(3)). Write to support@raizeka.com and we will answer within one month.

We verify your identity by matching your request to the data itself: write from the email address in question for account and email data, use the in-app feedback link for notification data, and send the install identifier or the store transaction id for subscription data. This is to avoid handing someone else's data to the wrong person; if we cannot match a request to data we hold, we may be unable to act on it (Art. 11). Because usage statistics and ad-measurement data are not linked to your name, account or email address, we may be unable to find a past record of them as yours.

International transfers. Our database sits on a server in Finland, inside the EU. Vercel, GitHub, Resend, Apple and Google are US-based companies and data may be accessed from the USA; in addition, because the controller is based in Türkiye, data is accessed from Türkiye, for which there is no adequacy decision. We rely on our providers' standard contractual clauses for these transfers; you can request a copy of the transfer mechanisms at support@raizeka.com. Usage statistics are held on PostHog's servers in the USA, under PostHog's standard contractual clauses. Meta and TikTok may process the ad-measurement data sent to them in countries outside the EU, including the USA and Singapore; for these transfers they rely on their own standard contractual clauses and, in Meta's case, also the EU-US Data Privacy Framework.

Complaints. You may lodge a complaint with the data protection authority in your country.

No automated decision-making. We take no automated decisions with legal effect about you and do not build a profile of you. If you allowed ad measurement, Meta and TikTok may use the shared advertising identifier and app events in their own advertising systems under their own policies; that is their responsibility.

12. If you live in Türkiye (KVKK)

Under Law no. 6698 on the Protection of Personal Data, the controller is the person named in section 1. You can exercise your rights under Article 11 (information, rectification, erasure, learning the third parties data was transferred to, compensation) by writing to support@raizeka.com. Requests are answered within 30 days at the latest. Usage statistics and ad measurement rest on the explicit consent you give on the app's permission screen, which you can withdraw at any time from inside the app.

13. Children

Modadrop is not aimed at children and we do not knowingly collect data from them. If you believe a child has entered their email address or opened an account, write to support@raizeka.com and we will delete the record.

14. Changes to this policy

If what we collect changes, we update this page and announce material changes in the app. The current version is always here, with its date at the bottom.

15. Contact

Modadrop
Email: support@raizeka.com

Last updated: 11 October 2026