Privacy Policy — Lettover
1. Introduction
Lettover ("we," "us," "the Game") respects your privacy. This Privacy Policy explains what personal data the Lettover app actually collects, why, who we share it with, and the rights you have over it. It describes our real, current practices — not aspirational or planned features.
Please read this carefully. If you do not agree with this Policy, please do not use the Game.
2. Who Is Responsible? (Data Controller)
proprietorships operate under the owner's own name; there is no separate trade name or company) Nilüfer/Bursa, Türkiye
For data subject requests (access, correction, erasure, etc.), see §10.
3. What Information Do We Collect?
3.1 Account & sign-in
You can play entirely anonymously — no account, email, or real name is required. If you choose to sign in, Lettover supports:
- Apple Sign-In (name on first authorization only; Apple never shares a photo)
- Google Sign-In (name, email, profile photo from your Google account)
- Facebook Login (name, email, and profile photo via the Facebook Graph API)
- Email + password
Whichever method you use, Firebase Authentication issues you a unique account ID (UID); this ID is the key everything else in this Policy is organized around.
3.2 Profile
- Display name / nickname (chosen by you; required to play under an identity)
- Avatar: either a built-in avatar ID, or a photo you upload from your device's photo library
(resized and stored as
avatars/{your-id}/avatar.jpg) - Locale (device language)
- Friend code, friends list (if you add friends — a paid feature)
- Gameplay stats (wins, losses, games played, scores), rating per language, league tier and season standing
- Coin balance and owned cosmetics (profile frames, tile themes)
3.3 Gameplay & in-game communication
- Game state: board, moves, scores, timestamps, outcome — needed to run and sync multiplayer games
- In-game "quick chat": a fixed set of preset friendly phrases only (e.g. "Good game!"). There is no free-text chat. Messages are stored as part of the shared game record (sender ID, phrase code, timestamp) so both players can see the exchange during and after the game.
3.4 Push notifications
If you enable notifications, we store an Expo push token (an opaque device identifier issued by Apple/Google through Expo's push service) so we can notify you about your turn or a game invite. We do not collect any other device information for this purpose.
3.5 Purchases
If you buy coins or a one-time unlock (ads removed, extra features, cosmetics), we record the product ID, a transaction/order ID, and the entitlement granted. We never receive or store your card number or the raw receipt/purchase token — those stay with Apple or Google, who process the payment and verify the purchase on our behalf.
3.6 Advertising
If you choose to watch a rewarded ad, or see an interstitial ad, the Google AdMob SDK collects advertising identifiers and ad-interaction data as described in §7 and §8. We send your account ID to AdMob only as a fraud-prevention token tied to the specific ad you watched (so we can verify the reward server-side) — not for ad personalization.
3.7 Crash diagnostics
If a crash-reporting service is active (see §9), a crash report may include an error message, a stack trace, your device's OS and app version, and the app name — but never your account ID, email, or any other identity information.
3.8 What we do not collect
We do not ask for or store your birthdate, age, phone number, precise location, contacts, photos other than the avatar you choose to upload, or any government ID. We do not run a behavioral-analytics SDK: see §6 ("In-house analytics").
4. Data Categories, Purpose, Legal Basis & Retention
| Data | Purpose | Legal basis (KVKK Art. 5 / GDPR Art. 6) | Retention |
|---|---|---|---|
| Account ID (UID), sign-in email/name/photo (if you link a provider) | Authentication, account identity | Contract (KVKK 5/2-c; GDPR 6(1)(b)) | Until account deletion |
| Profile (nickname, avatar, locale, stats, rating, league tier) | Core game functionality, multiplayer display | Contract | Until account deletion; see §11 for what persists in other players' records |
| Friends list | Social feature (paid unlock) | Contract | Until account deletion |
| Game state & quick-chat messages | Running and syncing multiplayer games | Contract | Until account deletion; the shared game record (including your past quick-chat and in-game identity) remains visible to your opponent afterward — see §11 |
| Push token | Turn / invite notifications (opt-in) | Consent | Until you disable notifications, uninstall, or delete your account |
| Purchase records (product ID, transaction ID, granted entitlement — never a raw receipt) | Fulfilling purchases, fraud prevention | Contract; legal obligation (bookkeeping) | Until account deletion; a global anti-replay record of the transaction (product ID, transaction ID, a one-way cryptographic hash of your account ID — never the account ID itself) is kept indefinitely to stop the same purchase receipt being redeemed again on a different account — see §11 |
| Advertising identifier & ad-interaction data (AdMob) | Serving ads, verifying rewarded-ad completion | Consent (ATT on iOS; UMP in EEA/UK) | Controlled by AdMob/your device settings — not stored by us beyond the reward-verification callback |
| Crash diagnostics (error, stack trace, device/app version — no identity) | Fixing bugs and crashes | Legitimate interest | Governed by the crash-reporting provider's retention once enabled (see §9) |
5. Processors & Third Parties
We use the following service providers. We do not sell your personal data to anyone, and we do not run our own advertising-attribution or marketing-analytics SDK.
| Provider | What it does for us | Their privacy policy |
|---|---|---|
| Google (Firebase: Authentication, Firestore, Cloud Functions, Storage) | Backend hosting, account auth, game/profile data storage, server logic | https://policies.google.com/privacy · https://firebase.google.com/support/privacy |
| Google AdMob | Serves interstitial and rewarded ads; ad-identifier processing | https://policies.google.com/technologies/ads |
| Expo (push notification delivery, build infrastructure) | Delivers push notifications via the Expo push service | https://expo.dev/privacy |
| Apple (Sign in with Apple; App Store purchases) | Sign-in; processes and verifies your App Store purchases | https://www.apple.com/legal/privacy/ |
| Google Play (Google Sign-In; purchases) | Sign-in; processes and verifies your Play Store purchases | https://policies.google.com/privacy |
| Meta / Facebook Login | Optional sign-in method, if you choose it | https://www.facebook.com/privacy/policy/ |
| Sentry (crash reporting) | Only active once a project DSN is configured (not yet live at the time of writing); see §9 | https://sentry.io/privacy/ |
Our backend (Firebase project) runs in Google's europe-west1 (EU) region.
6. In-House Analytics (what we actually do, not what a typical app does)
Lettover's own in-app analytics code does not use any third-party analytics SDK (no Firebase Analytics, no Google Analytics, no Mixpanel, no AppsFlyer, no Facebook Pixel). In development builds, events are only logged to the on-device debug console. In production builds, events are held in a small in-memory buffer on your device and are never transmitted anywhere — they exist only for on-device debugging during that session and are discarded when the app closes.
7. Advertising & Tracking
Lettover shows interstitial ads and optional rewarded-video ads through Google AdMob. No banner ads are shown.
- iOS (App Tracking Transparency): on iOS 14.5+, you will see Apple's standard tracking permission prompt before any ad-identifier (IDFA) collection: "This lets us show ads that are more relevant to you. Your data is never sold." You can allow or deny this at any time in your device's Settings → Privacy → Tracking.
- EEA/UK (consent, via Google's User Messaging Platform): if you're in the EEA or UK, a consent dialog from Google's UMP SDK appears before ads are shown, letting you choose your ad-consent preferences.
- Personalized vs. non-personalized ads: we do not run a separate ad-personalization toggle of our own. Whether AdMob serves personalized or non-personalized ads to you follows directly from the choice you make in the ATT prompt (iOS) or the UMP consent dialog (EEA/UK), per Google's standard AdMob behavior.
- Rewarded-ad verification: when you complete a rewarded ad, your account ID is sent to AdMob solely as a server-side verification identifier, together with a one-time transaction ID, so our server can confirm the reward and credit your account without that ID being used for ad targeting.
You can also reset your device's advertising identifier at any time in your device settings.
8. International Data Transfers
Our backend is hosted by Google Firebase in the europe-west1 (EU) region. However, Google,
Apple, Meta, Expo, and (if enabled) Sentry are global providers and may process data on
servers outside Turkey and outside the EU/EEA — including in the United States — as part of
delivering their services to us.
- GDPR: where applicable, transfers outside the EU/EEA rely on the receiving provider's own GDPR safeguards (e.g. Standard Contractual Clauses), as published in the privacy policies linked in §5.
- KVKK (Article 9): transferring personal data abroad requires your explicit consent, an adequacy decision, or a written undertaking (such as standard contractual clauses) between the parties. By creating an account and using the Game, you provide explicit consent to this transfer, which you can withdraw at any time by deleting your account (see §11).
9. Crash Reporting
Lettover's crash-reporting code is built to send error reports to Sentry, but it is completely inactive unless a Sentry project key is configured — no code path exists that sends crash data anywhere until that is turned on. If and when it is enabled, a crash report contains only: an error message, a stack trace, your device's OS platform, the app version, and the app name — never your account ID, email, nickname, or any other identifying information.
10. Your Rights
10.1 KVKK Rights (Turkey — Law No. 6698, Article 11)
You have the right to:
- Learn whether your personal data is being processed, and request information about it
- Request correction of incomplete or inaccurate data
- Request erasure or destruction of your data (subject to legal retention obligations, e.g. purchase/tax records)
- Object to a result that is to your detriment arising solely from automated processing
- Claim compensation for damage arising from unlawful processing
- Lodge a complaint with the Turkish Personal Data Protection Authority (KVKK Kurumu)
10.2 GDPR Rights (where applicable)
Under GDPR Articles 15–21, you have the right to access, rectify, erase, restrict, port, and object to the processing of your data, and to lodge a complaint with your national data protection authority.
10.3 How to exercise these rights
- In-app: Settings → Delete account (immediate, see §11)
- Web: https://lettover.app/delete-account
- Email: privacy@lettover.app — we aim to respond within 30 days
11. Account Deletion & Data Retention
There is no automatic deletion for inactivity. We keep your account and its data for as long as the account exists. You control when it ends.
Deleting your account (Settings → Delete account, or https://lettover.app/delete-account) removes you from matchmaking, cancels your own pending invites, and automatically ends any game you still had in progress (crediting your opponent with a win, so no one is left waiting — this never affects any other data belonging to your opponent). It then, immediately and permanently:
Your profile (display name, nickname, avatar, locale, coins, entitlements)
Your friends list, and every entry other players made for you on their own friends list
Your purchase/coin-grant ledger
Your push notification token(s)
Your avatar image
Your pending outgoing invites and incoming match-request inbox
Your daily-challenge leaderboard entries (score, words, placements)
Your league-season entries for any season that is still open or in the process of closing
Your sign-in credentials (email/password, linked Apple/Google/Facebook)
Your nickname/@handle reservation — held for 30 days before another player can claim it (so no one can immediately register your old handle and impersonate you), then freed.
Your display name, photo, and avatar in any game record — in-progress games you were just forced to forfeit, and any of your previously finished/forfeited games — so your opponent's own game history still shows a result, just not your name or photo.
Your display name, photo, and avatar in a league season that has already closed before you deleted your account (its final standings are a shared, settled historical record).
When you delete your account, the other player's copy of a finished or forfeited game — and any quick-chat exchanged during it — is not removed, because it is also your opponent's own game history, not solely yours; your name and photo on it are replaced with "Deleted player" as described above. For the same reason, standings for a league season that has already closed are kept (pseudonymised) rather than purged. We do this so deleting your account never erases another player's own game history, while still removing your identity from it.
A global, anti-replay fraud record is kept indefinitely for any purchase you ever made: the product ID, the transaction/order ID, and a one-way cryptographic hash of your account ID (never your account ID itself, and never reversible back to it) — so the same purchase receipt can't be redeemed again on a different account after you delete yours. Your own purchase/coin-grant ledger (readable, tied to your account) is still deleted as listed above; only this anonymous anti-fraud record survives.
If you can't access the app, you can request deletion by emailing privacy@lettover.app; we aim to complete email-requested deletions within 30 days.
12. Children
Lettover is not directed at children under 13 and we do not knowingly collect personal data from children. We do not ask for or store a birthdate or age, and there is currently no age verification or parental-consent mechanism in the app. If we learn that a child under 13 has created an account, we will delete it on request — email privacy@lettover.app. Parents or guardians who believe their child has provided personal data to us should contact us at the same address.
13. Security
- All communication between the app and our backend is encrypted in transit (TLS/HTTPS, via the Firebase SDKs).
- Firestore security rules enforce that sensitive data (profiles, games, league standings, purchase/economy records) can only be written through our server-side functions, never directly by a client — the one exception is the fixed-phrase quick-chat message, which is rate-limited and restricted to a short allow-list of preset phrase codes.
- We never store your raw purchase receipt or purchase token — only the verification result and the entitlement it granted.
- We do not store payment card details; those are handled entirely by Apple/Google.
If we discover a data breach affecting your personal data, we will notify affected users and the relevant authority without undue delay, consistent with KVKK and (where applicable) GDPR.
14. Changes to This Privacy Policy
We may update this Policy as the app's features or data practices change. Material changes will be reflected by updating the "Last updated" date above and, where appropriate, an in-app notice. Continuing to use the Game after an update means you accept the revised Policy; if you disagree, you can delete your account (see §11).
15. Contact Us
Nilüfer/Bursa, Türkiye
16. KVKK Madde 10 Uyarınca Aydınlatma Metni (Türkçe Özet)
Sayın oyuncu, Lettover uygulamasını kullanırken kişisel verileriniz (hesap kimliği, oluşturduğunuz takma ad/avatar, oyun verileri, isteğe bağlı bağlanılan e-posta/Apple/ Google/Facebook bilgileri, isteğe bağlı satın alma kayıtları ve bildirim jetonu) KVKK madde 5 kapsamında; oyun hizmetinin sunulması ve sözleşmenin ifası, hesabınızın doğrulanması, satın alımların doğrulanması ve yasal muhasebe yükümlülüklerinin yerine getirilmesi amaçlarıyla işlenmektedir. Reklam gösterimine ilişkin reklam kimliği verileri, cihazınızdan alınan açık rızanıza (iOS'ta Uygulama Takibi İzni, AB/İngiltere'de Google UMP onay ekranı) dayanılarak işlenir.
Verileriniz, hizmet aldığımız Google (Firebase, AdMob), Apple, Meta ve Expo gibi yurtdışı kaynaklı hizmet sağlayıcılarla, yalnızca hizmetin sunulması amacıyla paylaşılabilir; bu paylaşım nedeniyle verileriniz Türkiye dışına aktarılabilir. Bu aktarım, KVKK madde 9 kapsamında açık rızanıza dayanmaktadır; hesabınızı silerek bu rızayı geri çekebilirsiniz.
Verileriniz, hesabınız var olduğu sürece saklanır; otomatik bir süreyle silme uygulamıyoruz. Hesabınızı Ayarlar → Hesabımı Sil yoluyla veya https://lettover.app/delete-account adresinden anında silebilirsiniz; silme sırasında ne kadar verinin silindiği ve rakibinizin oyun geçmişine ait paylaşılan kayıtların neden kaldırılmadığı yukarıdaki §11'de açıklanmıştır.
KVKK madde 11 kapsamındaki haklarınızı (bilgi talep etme, düzeltme, silme, itiraz ve şikayet dahil) kullanmak için privacy@lettover.app adresinden bizimle iletişime geçebilir veya Kişisel Verileri Koruma Kurumu'na başvurabilirsiniz.