Selenay · Keycod Studio
Privacy Policy
This policy explains how your personal data is processed when you use the Selenay app (“Selenay: Horoscope & Tarot”). It follows the Turkish Personal Data Protection Law No. 6698 (KVKK) and the EU General Data Protection Regulation (GDPR).
Your privacy choices and the consent texts are in Your privacy choices. The Turkish page also carries the KVKK privacy notice (Aydınlatma Metni): Gizlilik Politikası (Türkçe).
All settings in the app are on the Profile tab; this policy shows them as paths such as “Profile › Privacy”.
1. Who we are
Selenay is developed and provided by Keycod Studio. The controller of your personal data is the party below, called “we” in this policy.
- Name
- Elber Kerim Kısakürek (“Keycod Studio”)
- Address
- Onikişubat, Kahramanmaraş, Türkiye (full postal address on request)
- Representative (Art. 27 GDPR)
- Selenay is not offered in the EU/EEA, UK or Swiss stores, so no representative under Article 27 GDPR has been appointed.
For any privacy question or request, write to destek@keycodstudio.com or use Profile › Support › Data request in the app (section 12).
2. Summary
- You can use Selenay as a guest without signing in; you can link Sign in with Apple or Google whenever you like.
- Your birth date, and your birth time and place if you give them, are used only to calculate your readings and to sync them across your devices.
- The location you use for horary charts never leaves your device.
- Usage analytics and personalized ads run only if you allow them, and never for anyone under 18.
- We do not sell your personal data.
- You can delete your account in the app at any time.
3. Data we collect
3.1 Data you give us
- Birth details: birth date (required, because every reading is built on it), birth time and birth place (optional). You choose a city as your birth place; its centre coordinates are stored rounded to about 1 km. If you choose no place, the time zone used for the calculation is stored.
- Your name (optional), so we know how to address you.
- Your settings: app language, daily and weekly reminder preferences, your daily reminder time and your usage analytics choice.
- Your privacy choices: each choice creates a consent record: the type of choice, whether it is on or off, where you made it, the version of the text shown, language, platform, app version and date, and, if you used Google's consent form, the choices you made there.
- Invite code: the code you enter if you redeem a friend's code (section 8A).
- What you write to us: your support emails and what they contain (for example your account id or a store order number).
3.2 Data created while you use the app
- Account data: your account id (Firebase user id), when the account was created and last signed in, and your device's time zone.
- Credit wallet and history: your balance, daily free credit, welcome gift, rewarded-ad and invite credits, your spends and the items you unlocked (which reading, when, for how many credits).
- Rewarded-ad records: a random session number for each ad, the AdMob transaction number and the verification result.
- Summaries of your horary answers: category, time of the question, tendency (leans yes, leans no or unclear), reasons and timing hint. This summary is synced with your account so your history also shows on your other devices. The question you type, your location, the city and the chart itself never leave your device.
- Account merge records: when you sign in with an account that already exists, we move your guest credits and unlocks to it and keep a redirect from the old guest id to that account, so late purchases or rewards reach the right account.
- Store ids: on iOS, the App Store app-transaction id that identifies your Apple Account for Selenay; on Android, the Google Play install id, only for supervised users (section 14).
- App attestations (Firebase App Check): short-lived confirmations from Apple and Google that requests come from the genuine Selenay app.
- Crash reports (Firebase Crashlytics) and, only if you allow them, analytics events (Google Analytics for Firebase) (section 7).
- Advertising data (Google AdMob): your advertising identifier if you allowed it, coarse location derived from your IP address, device information and ad interactions (section 6).
- Server logs: a shortened hash of your account id, the name of the function that ran, its outcome and duration.
- Invite program records (section 8A).
3.3 Data from partners
- Apple and Google: if you link Sign in with Apple or Google, your email address, display name and your id with that provider. Apple may give us a private relay address instead of your real email. When you link Sign in with Apple, we store a refresh token issued by Apple on our server, so that we can revoke Selenay's access later.
- App Store and Google Play (through RevenueCat): purchase and subscription records: store transaction number, product, dates, subscription and trial status, refund information. We never see your card or payment details.
- Parental consent notices: in some US states (for example Texas), if a parent withdraws consent for the app, Apple notifies us; Google Play provides the same information as a list of installs whose approval was revoked.
- Store age signals: Apple's Declared Age Range and Google Play's Age Signals are read on your device. Only the age band derived from them, the parental consent status and the time of the check are stored on your device; the age range itself is never stored or sent to us or to analytics.
We do not collect special categories of personal data (such as health or religious beliefs). The question text, which could contain such information, never leaves your device. The question you type for a tarot draw and the topic you choose are likewise kept only in your draw history on your device and are never sent to us, to analytics or to crash reports.
4. Data that stays on your device
The following is processed only on your device and is never sent to us:
- the location you use for a horary chart (your approximate location if you allow it; otherwise you choose a city);
- the question you type, the chart itself and your full horary history (only the answer summary in 3.2 is synced with your account);
- your tarot draw history;
- scheduled notifications: they are scheduled on your device, and we collect no token to send you notifications;
- privacy and age flags (for example that you saw the first-launch notice, the under-13 block and the age band derived from the store).
This data stays on your device until you remove the app or delete your account in the app. On iOS it may be included in your device backup (iCloud or computer); on Android, Selenay's data is excluded from device backups.
5. Purposes and legal bases
| Purpose | Data | KVKK | GDPR |
|---|---|---|---|
| Create your account, run the app and sync your data across devices | account id, profile, settings, horary answer summaries, account merge records | Art. 5(2)(c) (entering into and performing a contract) | Art. 6(1)(b) |
| Sign in with Apple or Google and recover your account | email, display name, provider id | Art. 5(2)(c) | Art. 6(1)(b) |
| Calculate your readings | birth details | Art. 5(2)(c) | Art. 6(1)(b) |
| Manage credits, unlocks and rewarded-ad credits; prevent double rewards and abuse | credit wallet and history, rewarded-ad records | Art. 5(2)(c); Art. 5(2)(f) (legitimate interest) for abuse prevention | Art. 6(1)(b); Art. 6(1)(f) |
| Deliver and restore purchases | purchase and subscription records | Art. 5(2)(c); Art. 5(2)(ç) (legal obligation) for record keeping | Art. 6(1)(b); Art. 6(1)(c) |
| Prove your consent and choices | consent records | Art. 5(2)(ç), Art. 5(2)(f) | Art. 6(1)(c) |
| Find and fix crashes and bugs | crash reports | Art. 5(2)(f) | Art. 6(1)(f) |
| Measure how the app is used | analytics events | Art. 5(1) (explicit consent) | Art. 6(1)(a) |
| Show and measure ads | advertising data | explicit consent (Art. 5(1)) for personalized ads; Art. 5(2)(f) for non-personalized ads | Art. 6(1)(a) (Google's consent form); without consent Google shows limited ads only |
| Protect the service and deliver app configuration | app attestations, configuration reads | Art. 5(2)(f) | Art. 6(1)(f) |
| Answer support requests | support emails | Art. 5(2)(c), Art. 5(2)(f) | Art. 6(1)(b), Art. 6(1)(f) |
| Prove that an account was deleted | deletion record | Art. 5(2)(ç) | Art. 6(1)(c) |
| Prevent double credits and refund abuse after deletion | purchase records with the account id replaced by a hash | Art. 5(2)(f) | Art. 6(1)(f) |
| Revoke Sign in with Apple access on unlinking and deletion | Apple refresh token | Art. 5(2)(c), Art. 5(2)(ç) | Art. 6(1)(b), Art. 6(1)(c) |
| Apply parental consent withdrawals reported by the stores | App Store app-transaction id, Google Play install id | Art. 5(2)(ç) | Art. 6(1)(c) |
| Operate and secure our servers | server logs | Art. 5(2)(f) | Art. 6(1)(f) |
| Back up against data loss | database backups | Art. 5(2)(f) | Art. 6(1)(f) |
| Run the invite program | invite code, invite record, credit history | Art. 5(2)(c) (program terms) | Art. 6(1)(b) |
| Prevent fraud in the invite program | invite record, hash of the App Store id and the date it was first seen, wrong-code counter | Art. 5(2)(f) | Art. 6(1)(f) (Recital 47) |
We can send you the balancing test we made for the processing based on legitimate interests, and you have the right to object to it (section 12).
6. Ads and tracking
- The free version shows Google AdMob ads: a banner at the bottom of reading screens, an occasional full-screen ad when you leave a reading, and rewarded ads you can choose to watch to earn credits. Premium has no ads, and the ad software is not started at all.
- Google is an independent controller for AdMob ads. Even with personalized ads off, Google processes your IP address and device information to show and measure ads and prevent fraud. How Google uses this data: How Google uses information from sites or apps that use our services.
- In the EU/EEA, the UK and Switzerland, Google's consent form (IAB TCF v2.2) is shown. Elsewhere, Selenay's “Your privacy choices” screen is shown, and “Personalized ads” starts switched off.
- On iOS, the tracking permission (App Tracking Transparency) is requested only if you turned on personalized ads or agreed to them in Google's form, are an adult and do not use Premium, and always after a short explanation screen. Everything works the same if you say no, rewarded ads included.
- For users aged 13–17, ads are never personalized, Google is told that the user is under the age of consent, and the tracking permission is never requested. Ad content is limited to at most T for adults and PG for ages 13–17 on iOS, and to at most G for everyone on Android.
- For rewarded ads, AdMob receives a random session number created for that ad, never your account id; our server uses it to verify the reward.
- We do not link analytics to AdMob and do not use analytics data for ads.
- If you see an inappropriate ad, tell us through Profile › Support › Report an ad.
Your privacy choices
You can change your choices at any time in Profile › Privacy:
- outside the EU/EEA, the UK and Switzerland: the “Usage analytics” and “Personalized ads” switches;
- in the EU/EEA, the UK and Switzerland: the “Privacy options” button, which opens Google's consent form;
- on iOS: the status of the tracking permission and a link to iOS Settings (this setting is separate from your choice in Selenay);
- the “Crash reports” switch.
Withdrawing consent does not make the processing based on it before the withdrawal unlawful. Both choices start switched off, no feature depends on them, and they are never offered to anyone under 18. These are the texts shown in the app (text version 2026-11-02):
7. Analytics and crash reports
Usage analytics
- Google Analytics for Firebase runs only with your explicit consent and only for adults; it is off when the app is installed.
- What is sent: which screens and features are used (for example opening a reading or purchase steps), general details such as your sun sign, language and Premium status, the app instance id and device information. Google derives a coarse location from your IP address.
- What is never sent: your name, birth date, birth time and place, location, question text, email or account id. We set no user id in analytics.
- Event-level data is kept for 2 months; Google signals and ad personalization are off. When you delete your account, the analytics id on your device is reset.
Crash reports
- Collected with Firebase Crashlytics, based on our legitimate interest in fixing crashes and bugs.
- No report is sent before you have seen the notice on the app's first screen and continued; none is ever sent for users under 13.
- Content: the error log, device model, operating system and app version, an installation id and technical details such as the screen where the error happened. No user id is added to reports.
- Reports are kept for 90 days. You can turn them off at any time in Profile › Privacy › Crash reports.
8. Purchases
- Apple (App Store) and Google (Google Play) take your payments; we never see your card or payment details.
- RevenueCat, Inc. (USA) records and verifies your purchases and subscriptions on our behalf; your account id is used as your customer id at RevenueCat.
- Our server keeps a record of each purchase (store, store transaction number, product, credit amount, dates, refund status), so a purchase is never credited twice.
- When you ask Apple for a refund of a purchase, usage and consumption information about that purchase is shared with Apple, and Apple decides on the refund (Terms of Use, section 7).
8A. Invite program
- What is processed: every adult account has an invite code. When you enter a friend's code, an invite record is created: both account ids, the code, dates, the record's status (pending, rewarded, capped, expired or void), the platform and the credit amounts granted. On iOS, the app-transaction information signed by Apple is verified on our server, and only an irreversible hash of the App Store id is stored. Your credit wallet keeps the date you redeemed a code, your last spend day and that day's wrong-code attempts.
- Why: to recognise the code, give the person who entered it the gift, reward the code's owner when that person opens a reading on a later day than the day they entered the code or makes a purchase, apply the monthly and total limits, and prevent fraud. An account, and on iOS an Apple Account, can redeem an invite code only once.
- Who sees what: the person who shared a code sees only counts (friends pending and friends who earned a reward); they never learn who joined. The person who enters the code sees nothing in the app about the code's owner.
- No contacts, no messages: Selenay does not read your contacts, does not read the pasteboard on its own and never sends invitations. You share your code yourself, with your own message, through your device's share menu; the shared link does not contain the code.
- Retention: an invite record is deleted automatically 90 days after the end of the period in which the person who entered the code can qualify for the reward (currently 14 days). Your invite code is kept while your account exists. The hash of the App Store id is kept for 24 months from the day the code was redeemed, also if you delete your account; otherwise the gift could be claimed again and again by deleting and re-creating an account. That record holds only the hash and dates, no account id.
- If you delete your account: your invite code is deleted and stops working. Friends who joined with your code keep their gift; in their invite records your account id is replaced by an irreversible hash, and those records are deleted when they expire. If you redeemed a code, your own invite record is deleted at once.
- Legal basis: Art. 5(2)(c) KVKK and Art. 6(1)(b) GDPR for running the program (Terms of Use, section 5A); Art. 5(2)(f) KVKK and Art. 6(1)(f) GDPR for fraud prevention.
- No new recipient: invite records are kept in our database in Belgium (europe-west1) like the rest of your account data; the program needs no new recipient and no new transfer abroad.
- The invite program is only for users aged 18 and over.
10. International transfers
Our database and server functions run in the European Union (Belgium, Google Cloud europe-west1); some of our providers process data in the USA and elsewhere in the world. These transfers from Türkiye are subject to Article 9 KVKK. We do not rely on consent for them. The table shows each recipient, where the data is processed and the safeguard actually in place today; it is updated whenever a safeguard changes.
| Recipient | Services | Location | Data | Transfer from Türkiye (Art. 9 KVKK) | Transfer from the EU (GDPR) |
|---|---|---|---|---|---|
| Google Cloud | Cloud Firestore, Cloud Functions, Cloud Logging, Firebase Authentication, Firebase App Check | EU (Belgium): database, functions and server logs; USA: Firebase Authentication | profile, credit wallet, consent records, server logs, account id, email, app attestations | Safeguard: the Board's standard contract (Google Cloud Data Processing Addendum, Appendix 3 “Turkey”). Status: not yet accepted or notified to the Board. | EU standard contractual clauses (Google Cloud Data Processing Addendum); EU-US Data Privacy Framework |
| Firebase Crashlytics | Firebase Crashlytics, Firebase Installations | worldwide, including the USA | crash reports, installation ids | No safeguard: the Firebase Data Processing and Security Terms contain no Turkish standard contract. Status: under legal review. | EU standard contractual clauses (Firebase Data Processing and Security Terms); EU-US Data Privacy Framework |
| Firebase Hosting | this website | worldwide, including the USA | web request logs (IP address, browser information) | No safeguard: the Firebase Data Processing and Security Terms contain no Turkish standard contract. Status: under legal review. | EU standard contractual clauses (Firebase Data Processing and Security Terms); EU-US Data Privacy Framework |
| Google Analytics for Firebase | usage analytics (only with your consent) | worldwide | analytics events, app instance id | No safeguard: Google offers no Turkish standard contract. Status: under legal review. | Google's data processing terms; EU-US Data Privacy Framework |
| Google AdMob | ads (Google is an independent controller) | worldwide | advertising data (never the account id) | No safeguard: Google's controller-controller data protection terms have no Turkey section. Status: under legal review. | Google's controller-controller data protection terms; Google's consent form for ad personalization |
| RevenueCat | purchase records | USA | account id, purchase history | Safeguard: the Board's controller-to-processor standard contract has been requested from RevenueCat. Status: not yet signed. | RevenueCat Data Processing Agreement (EU standard contractual clauses) |
| Cloudflare | forwarding of support emails (Cloudflare Email Routing) | worldwide, including the USA | support emails, in transit | No safeguard: no Board standard contract has been signed with Cloudflare. Status: under legal review. | Cloudflare Data Processing Addendum (EU standard contractual clauses); EU-US Data Privacy Framework |
| Google (Gmail) | the support mailbox (destek@keycodstudio.com) | worldwide, including the USA | support emails and what you put in them (email address, account id, store order ids) | No safeguard: no Board standard contract has been signed with Google for Gmail. Status: under legal review. | EU-US Data Privacy Framework |
11. Retention
- Account data (account id, profile, settings, credit wallet and history, unlocked items, horary answer summaries, consent records, purchase records, Apple refresh token, store ids, account merge redirects): until you delete your account. Guest accounts that never made a purchase are deleted automatically after 24 months without use.
- Email and display name (Apple or Google link): until you unlink the provider or delete your account.
- Rewarded-ad sessions and the session index 7 days, AdMob verification records 30 days; the credit granted stays visible in your credit history while your account exists.
- Purchase notification records (notifications received from RevenueCat): 90 days.
- Account merge tickets: 30 days.
- Invite program: section 8A.
- Crash reports: 90 days. Analytics events: 2 months. Advertising data: under Google's own retention rules.
- App attestations and configuration reads: not stored.
- Support emails: 2 years after the request is closed.
- Deletion record (hash of the account id, date, deletion channel and verification method, RevenueCat and Apple results): 3 years.
- During a deletion, a temporary lock record that stops data from being re-created: at most 2 hours.
- Server logs: 30 days, in a log store in the EU, with the account id hashed.
- Database backups: 7 days.
- Data on your device: section 4.
Kept after deletion: purchase records (store, store transaction number, product, credit amount, date and refund status; your account id is replaced by an irreversible hash) for 3 years to prevent double credits and refund abuse; the deletion record (hash and date) for 3 years; if you used an invite code on an iOS device, an irreversible hash of the App Store id that identifies your Apple Account for Selenay (the hash and dates only) for 24 months, so that the invite gift cannot be claimed again with the same Apple Account; a hash of your account id in the invite records of friends you invited, until those records are deleted 90 days after their reward periods end; encrypted database backups for at most 7 days; server logs for at most 30 days. Apple and Google keep their own purchase records.
The legal basis for the records kept after deletion is Art. 5(2)(f) KVKK and Art. 6(1)(f) GDPR (legitimate interest). Data whose retention period has ended is deleted, destroyed or anonymised.
12. Your rights
Under Article 11 KVKK you can ask us to:
- tell you whether your personal data is processed,
- give you information about it if it is,
- tell you the purpose of the processing and whether the data is used accordingly,
- name the third parties in Türkiye or abroad to whom it is transferred,
- correct it if it is incomplete or wrong,
- delete or destroy it under the conditions of Article 7 KVKK,
- inform the third parties who received it of any correction, deletion or destruction,
- accept your objection to a result against you that comes solely from automated analysis of your data,
- compensate you for damage caused by unlawful processing.
If the GDPR applies to you, you also have the rights of access, rectification, erasure, restriction of processing, data portability, objection to processing based on legitimate interests, and withdrawal of consent.
How to make a request
- In the app, Profile › Support › Data request opens a prepared email that contains your account id.
- You can also email destek@keycodstudio.com; to apply in writing, ask that address for our full postal address.
- We answer free of charge within 30 days. For access and portability requests we email you your account's records as a machine-readable file (JSON).
- To avoid giving your data to someone else, we verify your identity: we ask for your account id together with a store order number of that account, or for a request sent from the email address of the Google or Apple account linked to it. For guest accounts that never made a purchase, the account id is enough.
Complaints
If we refuse your request, if you find our answer insufficient or if we do not answer in time, you can complain to the Turkish Personal Data Protection Board within 30 days of learning our answer, and in any case within 60 days of your request (kvkk.gov.tr). In the EU/EEA you can complain to the data protection authority of your country, in the UK to the ICO, and in Switzerland to the Federal Data Protection and Information Commissioner (FDPIC).
13. Deleting your account
- In the app: Profile › Account › Delete account. Deletion is immediate, and guest accounts can be deleted too. If you have an active subscription, we first show you how to cancel it; deleting your account does not cancel a store subscription.
- If you can't open the app: use the email route on the account deletion page.
- What is deleted: your profile, birth details, settings, credit balance including purchased credits, unlocked items, horary history, consent records, your invite code and invite record, linked sign-in methods and your customer record at RevenueCat. Selenay's Sign in with Apple and Google access is revoked. The app also clears Selenay's data on your device.
Kept after deletion: purchase records (store, store transaction number, product, credit amount, date and refund status; your account id is replaced by an irreversible hash) for 3 years to prevent double credits and refund abuse; the deletion record (hash and date) for 3 years; if you used an invite code on an iOS device, an irreversible hash of the App Store id that identifies your Apple Account for Selenay (the hash and dates only) for 24 months, so that the invite gift cannot be claimed again with the same Apple Account; a hash of your account id in the invite records of friends you invited, until those records are deleted 90 days after their reward periods end; encrypted database backups for at most 7 days; server logs for at most 30 days. Apple and Google keep their own purchase records.
14. Children
- Selenay's account, personal readings, purchases and ad-supported service are for ages 13 and up.
- Under 13: crash reports are switched off and no data is stored or sent to us, apart from technical requests needed to display the sign guide.
- If a birth date shows that the user is under 13, the birth date is not saved and the device shows only the sign guide until the app is reinstalled.
- Ages 13–17: there is no analytics, the tracking permission is never requested, ads are never personalized and their content is limited (section 6), and the invite program is not shown. Purchases are subject to the stores' parental controls.
- If a store reports that a child's parental approval is pending, denied or withdrawn, the account is limited to free content until consent is restored. For this we match only the App Store app-transaction id (iOS) or, for supervised users, the Google Play install id (Android) with the account.
- Parents can email destek@keycodstudio.com to have their child's data deleted.
15. Security
- All connections between the app and our servers are encrypted (TLS).
- Database rules let each user reach only their own records, and only our server functions can write credit movements. Firebase App Check verifies that requests come from the genuine app.
- Secrets are kept in Google Secret Manager; our server functions run under a dedicated service account with only the permissions they need; administrator accounts use two-step verification.
- Server logs are kept for 30 days in a log store in the EU and contain only a shortened hash instead of your account id; they never contain your name, birth details, tokens or receipts.
- If a data breach happens, we notify the Turkish Personal Data Protection Board within 72 hours of learning about it, and the affected users as soon as possible.
16. AI-assisted content
Reading texts are written in advance with AI assistance, following our editorial guide, and ship inside the app. No AI runs while you use the app, and your personal data is never sent to an AI service.
17. This website
This website (selenay.keycodstudio.com) uses no cookies, no analytics, no tracking code and no third-party fonts, and runs no scripts. The pages are served by Google's Firebase Hosting; Google processes technical request data such as your IP address and browser information to deliver the pages and protect the service.
18. Changes
We may update this policy. The version number and effective date of each version are at the top of this page, and the changes are listed in the change log at the bottom. We announce material changes in the app and ask for your consent again where a change requires it.
Change log
- 1.0 · 17 November 2026 · First version.