Privacy Policy: efSahne
DRAFT — legal review required. Company name, address and contact details are placeholders: [COMPANY NAME], [ADDRESS], [EMAIL]. Every item in square brackets is awaiting a decision or verification. This text must be reviewed by a lawyer (and a tax advisor where relevant) before publication. It will be published on a website and linked from inside the app (Profile > Privacy policy) and from the store listings.
Last updated: [DATE] · Version: 0.1 (draft)
Turkish version: gizlilik-politikasi.tr.md · Terms of use: terms-of-use.en.md
1. Who we are (data controller)
This policy explains how personal data is processed when you use the efSahne mobile app (iOS and Android). The company operating the app and acting as data controller is:
- Legal name: [COMPANY NAME]
- Address: [ADDRESS]
- Email: [EMAIL]
- Turkish KVKK contact (registered e-mail, KEP): [KEP ADDRESS]
EU/EEA or UK representative under Article 27 GDPR, if required: [REPRESENTATIVE: decision pending].
2. What data we collect
The app has no sign-up form. On first launch a guest account is created in the background. We collect only what is needed to run the app.
| Category | Data | Source | Status |
|---|---|---|---|
| Account | Random user ID (including guest accounts); if you sign in with Apple or Google, the e-mail address that provider shares (with Apple's "Hide My Email", the relay address Apple provides) | You / Apple / Google | Guest: live. Apple/Google: [when sign-in is configured] |
| Profile | App language, VIP end date, account creation and update dates | App | Live |
| Content usage | Episodes you unlocked and how (coins, ad or VIP), watch progress (episode, position, completed flag), your watchlist | App | Live |
| Coins and rewards | Coin transactions (purchase, spend, reward, bonus, refund), daily reward streak and claim day (UTC calendar day), ad-unlock records (transaction ID, ad unit, day) | App / server | Live (ad records: [when ads go live]) |
| Purchases | Product purchased, transaction ID, subscription end date, event type (purchase, renewal, refund, cancellation). We never receive your payment card details; payment is handled by Apple or Google | App Store / Google Play, RevenueCat | [When the store is connected] |
| Errors and performance | Crash and error reports, device model, operating system version, app version, technical state at the time of an error. The app does not attach your e-mail, name or IP address to reports; only the random user ID is added | App | Live (Sentry, when the DSN is configured) |
| Analytics | Only if you turn it on in Settings (off by default): in-app events (e.g. screens, starting an episode, opening the store) with a random pseudonymous user ID. No e-mail, name, search text or IP-based location is sent | App | PostHog (EU Cloud), when configured and you opted in |
| Advertising | Advertising identifier (on iOS only if you allow tracking), ad preferences, consent from the Google UMP form (EEA/UK). Ads in Türkiye are requested as non-personalized. For rewarded ads, Google sends your random user ID and the unlocked episode ID to our server, signed, to verify the reward | Google AdMob | [Built into the app; live with the first store release] |
| Notifications | Device push token, if notifications are offered | App | [Planned] |
| On-device storage | Language choice and session token (kept in secure storage). This stays on your device | App | Live |
| Support | Information and attachments you send us by e-mail | You | Live |
Data we do not collect: location, contacts, photos, microphone or camera access, health data, user-uploaded content (there is no upload feature), or payment card numbers.
Search: [Are search queries stored? To be verified.]
3. Why we process data and on what legal basis
| Purpose | Data | GDPR basis (EEA/UK) | Turkish KVKK basis |
|---|---|---|---|
| Create and manage your account, unlock episodes, save watch progress and list, daily reward | Account, profile, content usage, coins and rewards | Performance of a contract (Art. 6(1)(b)) | Establishing or performing a contract (Art. 5/2-c) |
| Grant coins and VIP, verify purchases, handle refunds, accounting and tax duties | Purchases, coin transactions | Contract (Art. 6(1)(b)); legal obligation (Art. 6(1)(c)) | Contract (Art. 5/2-c); legal obligation (Art. 5/2-ç) |
| Find and fix crashes, keep the app secure, prevent abuse | Error reports, technical data, user ID | Legitimate interests (Art. 6(1)(f)) | Legitimate interests (Art. 5/2-f) |
| Measure and improve how the app is used (analytics) | In-app events, user ID | Consent (Art. 6(1)(a)) | Explicit consent (Art. 5/1) |
| Show advertising and measure ads | Advertising identifier, ad preferences | Consent (Art. 6(1)(a)); UMP consent in EEA/UK; ATT on iOS | Explicit consent (Art. 5/1); ATT permission |
| Respond to legal claims and disputes | Relevant records | Legal obligation or legitimate interests (Art. 6(1)(c), (f)) | Establishing, exercising or protecting a right (Art. 5/2-e) |
Where consent is the basis, you can withdraw it at any time. Withdrawal does not affect processing carried out before it.
4. Who we share data with
We do not sell your data. We share it only with the service providers below, which process it on our behalf and only to provide the service. Where personal data is processed on our instructions, these providers act as processors under data processing terms.
| Provider | Purpose | Data | Status |
|---|---|---|---|
| Supabase | Database, authentication, server functions (hosting) | Account, profile, content usage, coin records | Live. Region: [DATA REGION] |
| Sentry | Error and crash monitoring | Error reports, user ID | Live (when DSN is configured) |
| RevenueCat | In-app purchase and subscription management | User ID, purchase records | [When the store is connected] |
| Apple (App Store) and Google (Google Play) | Payments, subscriptions, in-app purchases; sign in with Apple/Google | Purchase and sign-in data | Governed by their own policies |
| Google AdMob | Rewarded ads | Advertising identifier, ad preferences, technical data; for reward verification, the random user ID and the unlocked episode ID | [Built into the app; live with the first store release] |
| PostHog | In-app analytics (only if you opt in) | Events, random user ID | EU (PostHog EU Cloud) |
| Expo (EAS) | Building and updating the app | Technical files; no user data | Live |
| Video hosting provider [MUX / BUNNY: decision pending] | Playing episode videos | IP address and playback technical data | [Choice pending] |
| Push notification services (APNs, FCM) | Sending notifications | Device token | [Planned] |
We will not disclose your data to third parties except where required by law, a court order or a valid request from a competent authority.
5. International transfers
Some providers (for example Supabase, Sentry, RevenueCat, Google, Apple and Expo) may process data outside your country, including outside the EEA/UK. Such transfers rely on the safeguards required by GDPR (Art. 44 et seq.) and Turkish KVKK (Art. 9): adequacy decisions, standard contractual clauses, or the provider's data processing terms. [Legal basis for each transfer: lawyer to confirm.] You can ask us for details of the safeguards at [EMAIL].
6. How long we keep data
| Data | Retention |
|---|---|
| Account, profile, coin ledger, unlocked episodes, watch progress, list | Until you delete your account |
| Daily reward and ad-unlock records | Until you delete your account |
| Purchase event records (transaction ID, product, amount, date, outcome) | [RETENTION DECISION PENDING]. Anonymised in the same step when you delete your account: your user ID and other identifiers are removed; only amount, date, product and event/transaction IDs are kept for accounting |
| Error reports (Sentry) | [X] days, per the provider's retention setting |
| Analytics events (PostHog) | [X] months (PostHog project setting) [deleting the PostHog record on account deletion will be added before release] |
| Records that tax and accounting law requires us to keep | As set by law [lawyer to confirm] |
| Guest account that has been inactive for a long period | [DECISION PENDING: no automatic deletion / after [X] days] |
When retention ends, data is deleted or irreversibly anonymised.
7. How to delete your data
- Signed-in account (signed in with Apple or Google): in the app, go to Profile > Account > Delete account. You confirm twice. Your account, profile, coin records, unlocked episodes, watch history and list are permanently deleted. If you signed in with Apple, you are asked to confirm with Apple again and the app's access to your Apple account (token) is revoked; if you signed in with Google, the permission you gave the app is revoked. Your purchase event records are anonymised in the same step (see section 6). If you allowed analytics, the analytics ID on your device is reset.
- Guest account: Profile > Delete my data. Your guest account and all data linked to it are deleted, and a new empty guest session starts.
- If you cannot open the app: request deletion at [WEB DELETION REQUEST URL] or by e-mail at [EMAIL]. We may ask for information to verify the request.
What is not deleted: purchase receipts and subscription records held by the App Store and Google Play remain there, and the corresponding purchase records remain with RevenueCat. Records we must keep for legal reasons stay for the legally required period (see section 6). If Apple's access cannot be revoked because of a temporary problem on Apple's side, we tell you; you can still delete your account and remove the access yourself in iPhone Settings > Apple ID > Sign in with Apple.
8. Children
The app is intended for users aged [MINIMUM AGE: e.g. 16+ / 18+, per the age rating result]. It is not directed at children under 13, and we do not knowingly collect personal data from children under 13. If we learn that we have collected such data, we will delete it. The age of digital consent in the EEA varies by country; where a user is below that age, parental consent will be required [lawyer to confirm]. Parents can ask us to delete their child's data at [EMAIL].
9. Security
Data is transmitted over encrypted connections (HTTPS). The database uses row-level security, and critical operations such as coin spending and unlocks run only on the server. Session data is kept in secure device storage. No system is completely secure; if a personal data breach occurs we will notify affected users and authorities within the timeframes required by law.
10. Your rights
Under Turkish KVKK (Art. 11) you have the right to:
- learn whether your personal data is processed;
- request information about the processing, if it takes place;
- learn the purpose of processing and whether it is used in line with that purpose;
- know the third parties to whom data is transferred domestically or abroad;
- request correction if data is incomplete or inaccurate;
- request erasure or destruction under the conditions in KVKK Art. 7;
- request that correction and erasure be notified to third parties to whom data was transferred;
- object to a result against you that arises from analysis of data exclusively by automated systems;
- claim compensation for damage caused by unlawful processing.
Under GDPR (EEA and UK users) you also have the rights of access, rectification, erasure, restriction of processing, data portability, objection, and withdrawal of consent at any time. You may lodge a complaint with your local supervisory authority.
How to exercise your rights:
- E-mail: [EMAIL] (we may ask for information to confirm your identity)
- KEP: [KEP ADDRESS]
- Written request: [ADDRESS]
We respond within 30 days (KVKK Art. 13; GDPR allows one month). Requests are free of charge, although a fee may apply where a request is manifestly unfounded or excessive [lawyer to confirm].
11. Changes
We may update this policy. For material changes we will notify you in the app and at [WEBSITE URL]. If we start collecting a new type of data or using data for a new purpose, we will obtain any required consent again.
12. Contact
For any privacy question: [EMAIL]