LINGRID
Privacy Policy
This policy explains how the LINGRID mobile app ("the app") and its developer, Beydanur Dönmez ("we", "us"), handle information. The app has no account system. Our only server is for the shared leaderboard (section 4). It uses advertising and consent services from Google, and advertising from Unity Ads and Liftoff Monetize through Google's AdMob mediation. To measure which of our own ads bring new players, it also uses the Meta SDK (Meta Platforms) and Google Analytics for Firebase (Google) (section 7). On iPhone and iPad it uses Apple's purchase (App Store), iCloud sync and Game Center services; on Android it uses Google Play's purchase (Google Play Billing), Google Play Games and Android backup services, each under the terms described below.
1. Who is responsible
Beydanur Dönmez, the developer and publisher of the app, is responsible for the app and for this policy. You can reach us at lingrid.sandbox@outlook.com.
2. Data stored only on your device
To make the game work, the app stores the following on your device, in the app's own storage: your puzzle progress and best scores, daily puzzle results and streak, your diamond balance and its transaction history, whether you have purchased Remove Ads, which colour themes you have unlocked, the free-puzzle allowance for the day, puzzles you have started, and your sound, music, colour theme and appearance settings. This data does not leave your device through the app, except as described in "Sync and backup" below, and we cannot see it. It is deleted when you delete the app, unless a copy has been kept in your iCloud account through iCloud sync on iPhone and iPad, or in your Google account's backup through Android backup on Android. Your device's own backups (for example iCloud Backup) may also include it under Apple's control. There are three exceptions, kept so that deleting and reinstalling the app on the same device does not lose them: (1) the number of free puzzles and rewarded-ad allowances you have used that day (three numbers and that day's date), so that the daily allowances do not start over; (2) the daily puzzles you have solved with their scores, your streak days and your total score; and (3) your shared-leaderboard device credentials: the random identifier and key the app created for this device, and whether you are on the leaderboard or have left it (section 4). These records are kept in the device keychain on iOS and in Google Play services' Block Store on Android. They do not contain your name, email address or contact details. Records (1) and (2) are used only on your device (scores of solved puzzles reach the shared leaderboard only as described in section 4); record (3) is used only to connect to the shared leaderboard as described in section 4. On iOS they stay on that device and are not synced to iCloud. On Android the app does not add them to your Google cloud backup, but Google Play services may copy them to a new device when you move your data directly from the old one. Record (1) is replaced the next time you open the app on a later day.
3. Game Center (Apple)
If you are signed in to Apple Game Center, the app sends the following to Apple so that leaderboards and achievements work: your daily puzzle score together with that day's puzzle number, your all-time total score, and your achievement progress. Your Game Center nickname and scores can be visible to other players on leaderboards. Game Center is operated by Apple under Apple's Privacy Policy; you can manage or turn it off in your device's Settings. The app uses your Game Center identity only to show whether you are signed in; it does not store it or send it anywhere else.
Google Play Games (Android). On Android, leaderboards and achievements run on Google Play Games services. If you are signed in to Google Play Games on your device, the app sends Google your daily puzzle score (as a number that includes that day's date) with the puzzle number, your all-time total score and the achievements you earn. Your Play Games player name and scores may be visible to other players on the leaderboards. Google processes this data under the Google Privacy Policy. If you do not sign in, the game works the same; only leaderboards and achievements are unavailable.
4. Shared leaderboard
The Leaderboard (Sıralama) tab has a shared leaderboard where iPhone and Android players compete together. Every player is on it automatically from version 1.4.0; the app does not ask first. The first time you open the tab, a short note tells you this. If you do not want to be on it, turn off "Show me on the leaderboard" ("Sıralamada görün") in Settings (Ayarlar) → Leaderboard (Sıralama): your data on the server is deleted and from then on nothing is sent. The game works exactly the same with it off, and you can turn it on again at any time.
What is sent while you are on the leaderboard: the score, time and number of hints of the puzzles you solve; a random identifier the app creates for this device (the app keeps it, with a device key, in the iOS keychain or, on Android, in Google Play services' Block Store, so that after a reinstall on the same device you keep the same leaderboard record; section 2); and, if you are signed in to Game Center or Play Games, your display name there (if you are not signed in, you get an automatic name). Your Game Center or Play Games identity is stored only as a one-way hash. When you are first on the leaderboard (the first launch of version 1.4.0, or when you turn it on again), the scores of puzzles you solved earlier on this device are sent once, so that your total is complete. Your email address, location and contacts are not sent. Your name and scores are visible to other players on the leaderboard.
Why: to show the leaderboard and to remove cheating scores (the server recalculates every score with the game's own formula).
Where: on the servers of Supabase, Inc. in Frankfurt (Germany, European Union), that is, outside Türkiye. When the app connects, your IP address may appear in short-lived technical logs. To confirm a Game Center or Play Games sign-in, the server checks it with Apple or Google.
How long: daily puzzle scores for 35 days; your total score and name until you delete them. Your record is deleted automatically 12 months after your last visit.
Leaving and deleting: Settings (Ayarlar) → Leaderboard (Sıralama) → turn off "Show me on the leaderboard" ("Sıralamada görün"), or tap "Delete my leaderboard data" ("Sıralama verilerimi sil"). Either one deletes everything on the server and takes you off the leaderboard; from then on the app sends nothing to the leaderboard server (if you are offline, only the deletion request is sent once a connection is back). You can turn it on again later. You can also write to us.
5. Advertising (Google Mobile Ads)
The app may show a short, full-screen interstitial ad between puzzles — when you leave the results screen of a puzzle you have just finished — but never while you are actively solving one. It also offers optional "rewarded" ads, shown only when you choose to watch them: on the home screen and in the diamond shop in exchange for diamonds, and on a locked level puzzle to open that puzzle. If you buy Remove Ads, the between-puzzle interstitial ads stop; the rewarded ads stay available because you choose to watch them. These ads are requested through Google's Mobile Ads SDK (Google AdMob). Through AdMob mediation, two other advertising companies can also bid to show an ad, using their own SDKs, which are part of the app: Unity Ads (Unity Technologies; privacy policy) and Liftoff Monetize (Liftoff Mobile, Inc., formerly Vungle; privacy policy). To request, show and measure ads, Google, these companies and their advertising partners may process: an approximate, coarse location estimated from your IP address; non-user performance data such as app launch time, crash reports and hang rate, which is used for diagnostics and may also be used to help decide which ads to show, including by sharing it with other companies that display ads; a device identifier — your device's advertising identifier where allowed, or another app- or developer-bound identifier — used for third-party advertising, our own advertising and analytics; and information about which ads you have seen and how you use the app, such as app launches. Unity's own disclosure also lists a user ID assigned by its SDK, purchase history, other usage data and device details such as language, model, screen and connection type. These lists are the companies' own disclosures of what their SDKs can collect, not our choice; they receive the data directly from their SDKs, and it does not pass through us. See "How Google uses information from sites or apps that use our services" and Google's Privacy Policy. Before showing ads to a user in the EEA, the UK or Switzerland, the app shows Google's consent message (the "UMP" form) so you can choose whether to allow personalised advertising; your choice is passed on to Unity Ads and Liftoff Monetize as well.
6. App Tracking Transparency and non-personalised ads
On iOS, before the app first requests an ad it asks for your permission under Apple's App Tracking Transparency (ATT) framework, shown in Turkish and in English. Outside the EEA, the UK and Switzerland, the app first shows its own consent screen for the measurement of our own ads (section 7) and then Apple's prompt; your ATT choice also decides whether that measurement may use your advertising identifier. If you decline tracking, if you have turned tracking off for the app in your device's Settings, or if UMP consent has not been given, the app does not use your device's advertising identifier for tracking, does not let the measurement SDKs in section 7 collect it, and only requests non-personalised ads — ads chosen without a profile built from your activity in other apps or websites. Non-personalised ads still use the advertising SDK data described above (for example, coarse location and a non-tracking device identifier), because the advertising SDKs need that data to request, serve, measure and protect any ad, personalised or not. You can change your ATT choice at any time in your device's Settings > Privacy & Security > Tracking; where the EEA/UK/Switzerland consent message applies, you can change your choice from the link Google provides inside that message.
Android has no App Tracking Transparency. On Android you can reset or delete your advertising ID in Settings > Privacy > Ads (or Google > Ads); if the advertising ID is deleted or UMP consent is not given, only non-personalised ads are requested. The measurement SDKs in section 7 never collect your Android advertising ID, anywhere.
7. Measuring our own ads (Meta and Google Analytics for Firebase)
We advertise LINGRID in other apps and on websites, for example on Facebook, Instagram and Google. To learn which of these ads bring new players and purchases, the app includes two measurement SDKs: the Meta SDK (Meta Platforms Ireland Limited and Meta Platforms, Inc.; Meta Privacy Policy) and Google Analytics for Firebase (Google; Google Privacy Policy and "How Google uses information from sites or apps that use our services"). They are not used to choose the ads shown inside the app, and we do not build advertising audiences from this data.
Only with your consent: outside the EEA, the UK and Switzerland (on Android and on iPhone and iPad), the app asks for your explicit consent on its own screen before it starts these SDKs. The screen names Meta Platforms and Google, says what is sent and why and that the data is processed abroad, and has two equal buttons, "İzin ver" (Allow) and "İzin verme" (Don't allow). If you do not allow it, the Meta SDK and Google Analytics for Firebase are not started at all, nothing described in this section is sent, and the game works exactly the same. On iPhone and iPad, Apple's ATT prompt (section 6) follows this screen. You can withdraw your consent at any time by turning off "Reklam ölçümü" (Ad measurement) in Settings (Ayarlar); from then on nothing is sent, and you can turn it on again later. Data sent before you withdrew your consent is kept by Meta and Google as described below. In the EEA, the UK and Switzerland, Google's consent message is used instead and the Meta SDK is not used (see below).
What is sent: that the app was installed and opened for the first time; app opens and sessions; purchases (the product, its price and currency, and the transaction number, so that one purchase is counted only once); and that you completed a puzzle (only whether it was the daily puzzle or a level puzzle; no answers, times or scores). The SDKs also record some events on their own, such as an update of the app or of the operating system, on Android the removal of the app, and, in Google Analytics, views of the ads shown in the app. With each event the SDKs send technical data: identifiers they create for this installation of the app, the app version, device and system information (such as model, operating system version, language and time zone) and your IP address, from which an approximate location may be derived. On Android, the app reads from Google Play which link or ad led to the installation (Google Play Install Referrer), and the SDKs send it with the installation. On iPhone and iPad, and only if you have also allowed tracking in Apple's ATT prompt (section 6), Google Analytics for Firebase also uses Google's on-device conversion measurement: de-identified, temporary data about events in the app is used on your device to measure whether a Google ad led to the installation or to a purchase. Your email address, phone number and any other data you enter are never used for this, and it is not active in the EEA, the UK and Switzerland. Your name, email address, contacts, precise location, leaderboard name and your Game Center or Play Games identity are not sent. This data does not name you, but it is not anonymous: it is pseudonymous data tied to this installation of the app.
When your advertising identifier is used: on iPhone and iPad, only if you have given your consent to measurement and also allowed tracking in Apple's ATT prompt (section 6). Meta and Google may then use your device's advertising identifier (IDFA) to connect an installation or purchase to an ad you saw in other apps or on websites. If you did not allow tracking, the advertising identifier is not collected: Meta receives the events marked as "tracking not allowed" and limits its use of them accordingly, and Google Analytics is told that advertising consent was not given. On Android, the measurement SDKs never collect your Android advertising ID. Outside the EEA, the UK and Switzerland, Google Analytics is told that the events may be passed to Google's advertising systems (Google Ads) only to measure our ads, but that no advertising identifier may be stored and that they may not be used for personalised advertising.
EEA, UK and Switzerland: the app does not show its own consent screen there and never starts the Meta SDK; nothing is sent to Meta from there. Google Analytics for Firebase starts only when you agree, in Google's consent message (section 5), to the measurement purposes and to Google as a partner; without that consent nothing described in this section is sent. Your Android advertising ID is not collected there either; on iPhone and iPad, Google Analytics for Firebase may use your device's advertising identifier (IDFA) only if you have also allowed tracking in Apple's ATT prompt (section 6). You can change your choice at any time with "Reklam gizlilik seçenekleri" (Ad privacy options) in Settings (Ayarlar), and turn measurement off with "Reklam ölçümü".
Why: to see which of our ads bring installations and purchases, so that we spend our advertising budget on ads that work. How long: Google Analytics keeps event-level data for 2 months; after that only summary reports remain. Meta keeps the data under its own rules, described in its Privacy Policy. Where: on Meta's and Google's servers, mainly in the United States and in Ireland, that is, outside Türkiye; this transfer rests on your explicit consent (section 14). Meta and Google also use this data under their own terms, for example to keep their advertising systems secure and to improve them.
Your choices: everywhere, the "Reklam ölçümü" (Ad measurement) switch in Settings (Ayarlar): turning it off stops all measurement from then on; on iPhone and iPad, Settings > Privacy & Security > Tracking for your advertising identifier; in the EEA, the UK and Switzerland, the consent message; reinstalling the app gives the SDKs new installation identifiers. Measurement runs only in the versions of the app published on the App Store and Google Play.
8. In-app purchases
The app offers in-app purchases — a one-time Remove Ads purchase and consumable diamond packs. All purchases are handled entirely by Apple through the App Store (StoreKit); we do not run our own store and we never receive your payment details, card number or billing address — Apple processes those under Apple's Privacy Policy. The app only receives confirmation of which product you bought and that the purchase succeeded, and finishes each transaction on your device. See our Terms of Use for what each purchase gives you and how Restore Purchases works.
On Android, all purchases are handled entirely by Google through Google Play Billing; we never receive your payment details, card number or billing address — Google processes them under its own Privacy Policy. The app stores on your device only which product you bought and the purchase key (purchase token) Google Play provides, which prevents the same purchase from being delivered twice. To restore Remove Ads, the app asks Google Play for the valid purchases of your account. When the app opens, the Google Play Billing library sends Google technical diagnostic logs about how the purchase connection is working (such as device model, Android version, language and country, mobile network code and app version); this is separate from the measurement in section 7 and from the consent you give for it.
9. Sync and backup
When iCloud is turned on for the app on your device, the app uses Apple's iCloud key-value storage, part of your own iCloud account, to keep the following in sync across your devices and through a reinstall on the same iCloud account: your puzzle progress (the puzzles you have solved, the puzzles you have opened, your best scores and your daily puzzle results), your diamond balance and its transaction history, whether you have purchased Remove Ads, which colour themes you have unlocked, and your daily streak. This storage is operated by Apple under Apple's Privacy Policy; we cannot see this data. If iCloud is off, or you are signed out of iCloud, this data stays only on your device as described in "Data stored only on your device" above, and is lost if you delete the app. To stop this syncing, open your device's Settings app, tap your name, then iCloud, and turn iCloud off for the app (or turn off iCloud Drive generally).
On Android the app uses Android's own backup (Auto Backup). If backup with your Google account is on, Android copies two of the app's files to your Google account backup about once a day while the device is idle: the local database with your game data (progress, scores, diamond balance and transaction history, Remove Ads, unlocked themes, streak, settings) and a sync copy of them. Android restores these files when you reinstall the app with the same Google account or move to a new phone. Android, not we, makes the backup; we have no access to it. Changes after the last backup may not be restored. You can manage or delete the backup in Settings > Google > Backup.
10. Permissions
The app does not ask for access to your camera, microphone, photos, precise location or contacts. It asks for permission to send notifications only if you choose daily reminders (below). It asks for permission to use your device's advertising identifier under Apple's App Tracking Transparency, only to support the advertising and the measurement of our own ads described above; you can decline this at any time (see "App Tracking Transparency and non-personalised ads").
Daily reminders (optional). The app never asks for notification permission when you first open it. After you finish your first daily puzzle, it asks in its own words whether you would like a reminder; only if you agree does it show Apple's notification permission prompt. Reminders are local notifications: the app schedules them on your device, at most two a day (one at the time you choose and, if you have a streak of two days or more, one later that evening), only for days whose daily puzzle you have not solved yet. No server is involved, no push token is created, and nothing about your reminders or your play is sent to us or to anyone else. You can turn reminders off or change their time in Settings (Ayarlar) at any time, and you can withdraw the permission in iOS Settings or, on Android, in Settings > Apps > LINGRID > Notifications.
On Android, the app's release build declares 15 permissions. Seven are tied to features: internet access; vibration (haptic feedback); Google Play Billing; the advertising ID permission (AD_ID) used by the Google Mobile Ads SDK (the measurement SDKs in section 7 never collect the advertising ID); the Google Play Install Referrer permission (BIND_GET_INSTALL_REFERRER_SERVICE), which lets the app ask Google Play which link or ad led to the installation (section 7); on Android 13 and later, the notification permission (POST_NOTIFICATIONS), asked only if you choose daily reminders; and run-at-startup (RECEIVE_BOOT_COMPLETED) so scheduled reminders survive a restart. The reminder permission is asked after the app's own explanation screen; no exact-alarm permission is requested, so a reminder may arrive a few minutes late. The other eight are technical permissions added by the advertising SDKs and Android libraries that show you no prompt: network state, wake lock, foreground service, Android's ad services (ADSERVICES: advertising ID, topics and attribution; three permissions), one permission added by Liftoff Monetize's SDK (com.amazon.privacypass.ATTEST) and one permission Android uses to keep the app's own internal messages private. There is no camera, microphone, location, contacts, photos or storage permission.
11. Network
Level puzzles, sounds and images are included in the app. The app also downloads small files of four kinds from our website on GitHub Pages (beydadonmezz.github.io/lingrid; versions before 1.4.0 use beydadonmezz.github.io/lingrid-site): the minimum supported app version, the recommended app version together with an optional short notice from us, new daily puzzles, and corrections to puzzle clues. These are plain downloads of public files: the app sends no account, device identifier or gameplay data with them. As with any web request, GitHub, Inc. processes technical request data such as your IP address to deliver the files. If the files cannot be downloaded, the app uses the copies included in it; without the recommended-version file, the app simply shows no update message. To tell you that a newer version is available, on iPhone and iPad the app asks Apple's public App Store lookup service (itunes.apple.com) at most once a day which version of LINGRID is current; the request contains only LINGRID's public app identifier and the store country. On Android the app asks Google Play, through Google Play's in-app update service on your device, whether an update is available; if you choose to update, Google Play downloads and installs it. These checks send no personal data beyond what every internet request carries: your IP address and the device's user agent (a technical description of the app and system). According to Google, its in-app update service uses device information, the app version and the list of the app's installed parts to find out whether an update is available, and does not pass this data on to third parties. The app connects to the internet for: Apple Game Center, as described above; Google's advertising and consent services, to request and show ads and to gather advertising consent, and, through AdMob mediation, Unity Ads and Liftoff Monetize, to bid for and show ads; Meta and Google Analytics for Firebase, for the measurement of our own ads described in section 7 (only after your consent, section 7); and Apple's App Store/StoreKit and iCloud services, for purchases, the version check and sync. On Android the app also connects to Google Play for purchases, the installation source (section 7) and update checks, and to Google Play Games for leaderboards; backup is performed by Android. Unless you turned off "Show me on the leaderboard", the app also connects to LINGRID's leaderboard server (Supabase, Frankfurt) for the data described in section 4. The app shows these legal texts without a connection. When you open their web version, your browser loads it from GitHub Pages, a service of GitHub, Inc., which processes technical request data such as your IP address to deliver the page. This website uses no cookies and no analytics.
If you report a clue with "Bu ipucu yanlış", the app opens your own email app with a prepared message (the puzzle number, the clue and the app version). Nothing is sent unless you send that email yourself; if you do, we receive your email address and what you wrote, and use them only to check and correct the clue and to reply to you.
12. Children
LINGRID is a general-audience word-learning game; we do not direct its marketing at children under 13 and do not knowingly collect personal information from children. A user who has not given tracking consent, of any age, is only ever shown non-personalised ads, as described above. If you believe a child has given us personal information, contact us and we will take appropriate action.
13. Your rights
Apart from the pseudonymous measurement reports described in section 7, the only personal data we hold ourselves is your shared leaderboard record (section 4): you can delete it in the app at any time (Settings → Leaderboard), or write to us to access, correct or delete it. You can delete the data stored on your device by deleting the app; this does not delete a copy kept in your iCloud account, which you control from your device's Settings app under your name, then iCloud. For your Apple ID, Game Center or purchase data, contact Apple. For the advertising data Google's SDK has processed about you, use Google's own controls at myadcenter.google.com, Unity's and Liftoff's choices described in their privacy policies linked above, or the choices described in "App Tracking Transparency and non-personalised ads" above. For the measurement data (section 7), use the choices described there, Meta's controls described in its Privacy Policy (for example "Your activity off Meta technologies" in your Meta account) and Google's controls at myadcenter.google.com. We see this data only in reports that do not contain your name or contact details, so we usually cannot tell which data is yours; if you write to us, we will do what Meta's and Google's tools allow us to do. On Android you can delete the backup copy in your Google account in Settings > Google > Backup, and manage your Play Games data in the Google Play Games app or your Google account. You can still write to us with any privacy question.
14. Additional information for users in Türkiye under the Personal Data Protection Law (KVKK)
Under Law No. 6698 on the Protection of Personal Data (Kişisel Verilerin Korunması Kanunu, "KVKK"), the data controller (veri sorumlusu) responsible for the personal data described in this policy is Beydanur Dönmez, the app's developer. For any KVKK-related request, write to lingrid.sandbox@outlook.com.
Under KVKK article 5, each purpose above rests on one legal basis. Storing your puzzle progress, wallet, daily free-puzzle allowance and settings on your device, handling in-app purchases through Apple or Google Play, sending your score and achievements to Game Center or Google Play Games when you are signed in, and syncing or backing up your data through iCloud or Android backup when you turn it on, are all necessary for the establishment or performance of the contract under which you use the app and the features you choose (article 5/2(c)) — no separate consent is needed for these. Showing personalised advertising and using your device's advertising identifier for tracking or for the measurement of our own ads rest on your explicit consent (article 5/1), given or withdrawn through the ATT and UMP consent screens described above; in the EEA, the UK and Switzerland the measurement in section 7 (there, Google Analytics for Firebase only) rests on that consent. Elsewhere, the measurement in section 7 rests on your explicit consent (article 5/1), which the app asks for before starting it and which you can withdraw at any time in Settings → "Reklam ölçümü". The data the advertising SDKs (Google's Mobile Ads SDK and, through mediation, Unity Ads and Liftoff Monetize) need to request, serve, measure and protect any ad even when you have not consented to tracking (for example coarse location, a non-tracking device identifier, and diagnostic, performance and crash data) rests on our and these companies' legitimate interest in operating and securing the free, ad-supported version of the app, without prejudice to your fundamental rights and freedoms (article 5/2(f)). The shared leaderboard, a feature of the app, rests on the performance of that same contract (article 5/2(c)); removing cheating scores from it rests on our legitimate interest in a fair leaderboard (article 5/2(f)). You can leave it at any time with Settings → Leaderboard → "Show me on the leaderboard".
Yurt dışına aktarım / transfer abroad: Google (Mobile Ads SDK, UMP and Google Analytics for Firebase; on Android also Google Play Billing, Google Play Games, Google Play's install referrer and in-app update services and Android backup), Meta Platforms (measurement of our own ads), Unity Technologies and Liftoff Mobile (advertising through AdMob mediation) and Apple (App Store/StoreKit, Game Center, iCloud and the App Store version lookup) may process the data described above on servers located outside Türkiye, including in the United States. This transfer takes place under KVKK article 9, as amended by Law No. 7499 with effect from 1 June 2024: for personalised advertising and tracking, the transfer rests on your explicit consent; for purchases, Game Center and iCloud sync, and for Google Play purchases, Google Play Games and Android backup, it rests on the transfer being directly related to the establishment or performance of the very service you asked for, one of the exceptional grounds listed in article 9(6). For the measurement of our own ads (section 7), the transfer to Meta and Google rests on your explicit consent (article 9(6)(a)), which the app asks for before starting it. Meta, Google, Unity, Liftoff and Apple receive this data directly from their own SDKs and services in the app; we do not operate a server of our own that receives it. The only exception is the shared leaderboard: its data is stored on the servers of Supabase, Inc. (a company based in the United States) in Frankfurt, Germany; like the services above, this transfer is directly related to the performance of the app's own leaderboard feature (article 9(6)). You can stop it at any time by turning off "Show me on the leaderboard".
Under KVKK article 11, you have the right to: (a) learn whether your personal data is being processed; (b) request information about it if it has been processed; (c) learn the purpose of the processing and whether it is used in accordance with that purpose; (ç) know the third parties, in Türkiye or abroad, to whom your data is transferred; (d) request correction if it has been processed incompletely or incorrectly; (e) request its deletion or destruction, within the conditions set out in the law; (f) request that any correction, deletion or destruction be notified to the third parties to whom your data was transferred; (g) object to a result against you that arises solely from the automated analysis of your data; and (ğ) claim compensation for damage you suffer because of unlawful processing.
To exercise these rights, write to us at lingrid.sandbox@outlook.com; under KVKK article 13 we handle your request free of charge, as quickly as possible and within 30 days at the latest (a fee may apply only for a request that itself requires an additional cost, at the tariff the Personal Data Protection Board sets). If we reject your request, you find our answer insufficient, or we do not answer in time, KVKK article 14 lets you complain to the Personal Data Protection Board (Kişisel Verileri Koruma Kurulu, kvkk.gov.tr) within 30 days of learning our answer and, in any case, within 60 days of your original request.
15. Changes
If the app starts handling data differently, we will update this policy before that version is released and change the date above.
16. Contact
Beydanur Dönmez · lingrid.sandbox@outlook.com