KelimeYAP Privacy Policy
KelimeYAP English · Last updated: 9 October 2026
The short version
KelimeYAP English has no accounts. You never give us your name, email, phone number or password, and there is no sign-in of any kind. The app creates a random anonymous identifier on your device so your learning progress can be saved, and that is the only thing your progress is attached to. Two things you type yourself are also stored: an optional nickname, and any question you send to Kulabuz, the guide inside the app. You can erase everything from inside the app at any time under Settings → Delete My Data.
This policy explains exactly what KelimeYAP English processes, why, where it
is stored and what control you have over it. It covers the mobile app
published as KelimeYAP English on the App Store
(com.furkanyanteri.kelimeyap-en-tr) and Google Play
(com.furkanyanteri.kelimeyapentr).
1. Who is responsible for your data
The data controller is the developer of KelimeYAP, as listed on the App Store and Google Play, Ankara, Türkiye. For any question about this policy or about your data, write to info@obliquex.com.
2. No account, no personal information
There is no registration in KelimeYAP English. We do not ask for an email address, phone number, name, username or password, and there is no "Sign in with Google", "Sign in with Apple" or Facebook login. This is a deliberate product decision, not a feature we have yet to build.
When you first open the app, it creates an anonymous identifier in the background, a randomly generated UUID. It is not derived from anything about you, it is not linked to your real identity, and it cannot be traced back to you as a person. Everything described in section 3 is attached to that random identifier and nothing else.
The identifier is specific to one device. If you install the app on a second device, a completely new and independent identifier is created there; the two are not connected and we have no way to recognise that they belong to the same person. If you want to carry your progress across, the app has an optional transfer-code feature you trigger yourself (see section 3).
The one thing you can type about yourself is an optional nickname, offered when you first open the app. It is a display name you choose, not a login credential and not your real name, and leaving it blank changes nothing about how the app works. Section 3.1 describes how it is stored.
3. What we process
3.1 Stored on our servers
All of the following is attached to your anonymous identifier. We ask for nothing that identifies you; the only free text in the list is what you choose to type yourself, the nickname, your questions to Kulabuz and the short note you write in a problem report.
- Nickname, an optional display name you pick for yourself. It is used only to address you inside the app. We do not ask for your real name, we do not verify what you type, and we do not share it with anyone. You can leave it blank at the start and change or clear it later under Settings → My Profile.
- Learning progress: how well you know each word (a confidence score from 1 to 5), and the dated history of how that score changed over time.
- Quiz statistics: number of quizzes completed, total questions answered, correct answers, accumulated points and the time of your last quiz.
- Missed words: words you answered incorrectly, so the app can ask them again later.
- Kulabuz conversations. Kulabuz is the guide inside the app. When you send it a question, that question and the answer it gives are stored on our servers. To produce the answer, the text of your question, your app settings (such as language and notification preferences) and a summary of your progress in the app (such as your credit balance and quiz and word counts) are sent to Anthropic (the Claude API), which acts as a service provider for us: this data is not sold, and it is not used for advertising or analytics. If Kulabuz offers to forward an issue to our support team and you agree, that conversation is stored together with your app version, Pro status and credit balance so that our support team can read it. This record is deleted by "Delete My Data" in the app. If you never ask Kulabuz anything, no such text is collected.
- Problem reports. When you report an image in the app or one of Kulabuz's answers, we store which content you reported, the reason you selected, and, only when you choose "Other", the short note you write. These records are used solely to improve our own content. They are not shared with third parties and are not used for advertising or analytics.
- Question quality ratings. When you mark a quiz question as helpful or unhelpful, we store that rating, which word and question type it belongs to, and the content that was shown to you in the question. These records contain no text written by you. They are used solely to improve the quality of our own question content. They are not shared with third parties and are not used for advertising or analytics.
- In-app credits: your credit balance and the records of credits earned, including the single-use verification codes used for Google's server-side rewarded-video check.
- Progress transfer: the transfer code you generate yourself to copy your progress to another device, and records of transfer attempts, kept to detect abuse of the feature.
- Abuse protection: counters for image and quiz requests (per-minute and per-hour rate limits), and a record of a temporary restriction if unusual usage is detected.
- Notification token. If you allow notifications, we store the notification token that your device's operating system assigns to the app, together with your anonymous user ID, so that we can send you notifications. This token is used only for app notifications, never for advertising or analytics, and is deleted when you turn notifications off or delete your data. Some notifications are scheduled on your device itself and do not need this token.
Please do not type personal information into Kulabuz. Ask it about words, levels, quizzes or how the app works. What you write there is stored and is passed on to generate the answer, so it is not the place for your name, address, phone number, payment details or anything else you would rather not have kept.
3.2 Stored only on your device
This never leaves your phone and is never sent to our servers:
- App settings: language preference, sound and haptics on/off, auto-pronunciation, card behaviour preferences.
- A local copy of the word database, so the app works offline.
- Badges and peak milestones.
- Session counters such as your daily card count and streak.
Deleting the app removes all of this local data. Please read section 9 for an important difference between iOS and Android.
3.3 Technical data the advertising SDK collects
The free version shows ads through Google AdMob, and the AdMob SDK sends Google technical information about your device and about each ad request so that an ad can be delivered and checked. Google Play's data safety form calls this diagnostics, under "App info and performance". It covers things such as the device model, the operating system and app version, language and region, the IP address the request comes from, and whether an ad loaded and was displayed correctly. This data goes to Google rather than to us. It is not part of section 3.1 and it is not attached to your anonymous identifier on our servers. Section 6 explains how your consent affects it.
3.4 Error and crash reports
From version 3.1.0, when the app runs into an error or crashes, an error report is sent to our service provider Sentry so that we can find and fix the problem. The report contains the technical detail of the error (which line of code it happened in) and technical information about the device (device model, operating system and app version). It contains no identifier: not your anonymous identifier, not your nickname and not any device-specific ID. Every report carries the same fixed value, so a report cannot be tied to a person or a device. The IP address of the connection the report arrives on is not stored by Sentry. Reports are kept inside the European Union (Germany) and are deleted automatically after 30 days. No screenshots, screen recordings or text you typed are sent.
4. What we do not collect
To be explicit, KelimeYAP English does not collect or have access to:
- Your name, email address, phone number or postal address.
- Location data: the app does not use GPS and does not perform IP-based location tracking.
- Your contacts, photos, files, microphone or camera.
- Health, financial or biometric data.
- Your device's contact list or the list of apps you have installed.
- Your messages or anything you type outside the app.
The app also does not use any third-party analytics or product-usage tracking SDK. The diagnostic data described in section 3.3 is sent by the advertising SDK to Google as part of serving ads, and it is not a usage-analytics product of ours.
5. Why we process it, and the legal basis
| Data | Purpose | Legal basis (GDPR) |
|---|---|---|
| Anonymous identifier | Attaching your progress to your device so it is not lost | Performance of a contract (Art. 6(1)(b)) |
| Learning progress, quiz statistics, missed words | Providing the core function of the app: spaced learning | Performance of a contract (Art. 6(1)(b)) |
| Credits and rewarded-video records | Running the in-app credit system and validating rewards | Performance of a contract (Art. 6(1)(b)) |
| Transfer codes and attempt records | Moving your progress between devices, and preventing abuse | Performance of a contract (Art. 6(1)(b)); legitimate interests (Art. 6(1)(f)) for abuse prevention |
| Rate-limit counters and restriction records | Keeping the service available and preventing misuse | Legitimate interests (Art. 6(1)(f)) |
| Personalised advertising | Showing ads relevant to you in the free version | Your explicit consent (Art. 6(1)(a)) |
| Subscription status | Removing ads for subscribers and restoring purchases | Performance of a contract (Art. 6(1)(b)) |
| Nickname | Addressing you by the name you chose inside the app | Your consent (Art. 6(1)(a)); it is optional and can be left blank |
| Kulabuz questions and the answers given | Answering what you ask about the app and keeping the conversation available to you | Performance of a contract (Art. 6(1)(b)) |
| Support requests (the Kulabuz conversation you agree to forward, app version, Pro status, credit balance) | Looking into the issue you reported | Your explicit consent (Art. 6(1)(a)); a request is only opened if you agree |
| Notification token | Sending you app notifications | Your explicit consent (Art. 6(1)(a)), given when you allow notifications yourself |
| Diagnostic data sent by the advertising SDK | Delivering ads, confirming they were displayed and detecting ad fraud | Your explicit consent (Art. 6(1)(a)) where ads are personalised; legitimate interests (Art. 6(1)(f)) for delivery and fraud prevention |
| Error and crash reports | Finding and fixing errors in the app | Our legitimate interest in providing a working and secure app (Art. 6(1)(f)) |
6. Advertising and your consent
The free version of KelimeYAP English shows ads through Google AdMob. There are three placements: a native ad inside the card deck, rewarded video you choose to watch, and a banner in the example-sentence panel. There are no full-screen interstitial ads.
Whether those ads are personalised depends entirely on your consent:
- In the EU, the UK and Switzerland, the app shows a consent screen through Google's User Messaging Platform (UMP) before personalised advertising is enabled.
- On iOS, the app additionally asks for Apple's App Tracking Transparency (ATT) permission.
- If you decline, ads are not personalised. You see contextual ads instead.
- Declining does not restrict any feature of the app. Nothing is locked behind giving consent.
You can change your choice at any time: the consent screen can be reopened from the app's settings, and ATT can be changed under iOS Settings → Privacy & Security → Tracking. For how Google uses data from apps that use its advertising services, see Google's policy on how it uses information from partner sites and apps.
7. Subscriptions and payment
KelimeYAP English offers an ad-free Pro subscription. Purchases are handled by the App Store and Google Play; subscription state is managed through RevenueCat.
Your payment details never reach the app. Card information is processed by Apple and Google and we never see it. What RevenueCat receives is your anonymous identifier and your subscription status, nothing more.
8. Third-party services
| Service | What it does | What it receives | Policy |
|---|---|---|---|
| Supabase | Database, anonymous authentication, file storage | The anonymous identifier and the data in section 3.1 | Privacy |
| Anthropic (Claude API) | Generating Kulabuz's answers | The text of the question you send to Kulabuz, your app settings (such as language and notification preferences) and a summary of your progress in the app (such as your credit balance and quiz and word counts) | Privacy |
| Google AdMob | Advertising in the free version | Advertising identifiers and ad-request data, subject to your consent choice | Policy |
| RevenueCat | Subscription management and receipt validation | Anonymous identifier and subscription status | Privacy |
| Apple App Store | App distribution and subscription payments | Payment details, handled entirely by Apple | Privacy |
| Google Play | App distribution and subscription payments | Payment details, handled entirely by Google | Privacy |
| Expo / EAS | App builds and over-the-air updates | Technical data needed to deliver an update to the app | Privacy |
| Sentry | Collecting error and crash reports (European Union, Germany) | The identifier-free error report described in 3.4; IP addresses are not stored | Privacy |
| Expo Push Service | Sending notifications to your device | The notification token and the notification being sent | Privacy |
| Apple Push Notification service | Delivering notifications on iOS | The notification token and the notification being sent | Privacy |
| Firebase Cloud Messaging | Delivering notifications on Android | The notification token and the notification being sent | Privacy |
We do not sell your data and we do not share it with anyone for marketing purposes. The three notification services receive your notification token only to deliver notifications; it is not used for advertising or analytics.
9. Where your data is stored, and international transfers
Our database is hosted on Supabase in the Germany (Frankfurt) region, inside the European Union. If you are in the European Economic Area, the data described in section 3.1 stays within your region. If you are in the United Kingdom or Switzerland, it is transferred to the European Economic Area, which both countries recognise as providing adequate data protection. For users in Türkiye, it is a transfer abroad.
That transfer is covered by the European Commission's Standard Contractual Clauses together with the technical and organisational measures applied to the data: the data is pseudonymous by design, it holds no identifying information about you, and access to it is restricted by row-level security rules tied to your anonymous identifier.
The text of a question you send to Kulabuz, together with your app settings and a summary of your progress, is also passed to Anthropic, a company based in the United States, so it is processed outside the European Economic Area, the United Kingdom, Switzerland and Türkiye. Anthropic handles this data as our service provider, under its own data processing terms, for the single purpose of producing the answer you asked for.
The error reports described in 3.4 are also kept by Sentry inside the European Union (Germany). For users in Türkiye this is likewise a transfer abroad, made on the same basis as above.
Ad, subscription, distribution and notification partners listed in section 8 operate their own global infrastructure and process data under their own policies, linked above.
10. How long we keep it
Your learning data is kept for as long as it is useful to you, which means until you delete it. There is no fixed expiry, because losing your progress without asking would defeat the purpose of the app. You decide when it goes, and you can do that at any time from inside the app.
Your nickname and your Kulabuz conversations are kept on the same basis. They stay until you remove them, either by clearing the nickname in Settings or by using Delete My Data.
Your notification token is kept until you turn notifications off or delete your data. A token that has become invalid is deleted when a notification is sent to it.
Error and crash reports are kept by Sentry for 30 days and are then deleted automatically.
Rate-limit counters and transfer-attempt records are short-lived and are kept only as long as they are needed for the abuse check they support.
11. Deleting your data
The app has a Delete My Data button in Settings. It permanently erases all of your data on our servers. You do not need to email us, fill in a form or wait for a reply. You do it yourself, and it takes effect immediately.
- Open KelimeYAP English.
- Go to Settings.
- Tap Delete My Data and confirm.
This cannot be undone. Your progress, statistics, nickname, Kulabuz conversations, support requests, credits, transfer codes and notification token are gone for good.
Error and crash reports (3.4) are outside the scope of this action, because they carry no identifier and we have no way to tell which ones are yours. They are deleted automatically within 30 days.
Deleting the app itself also removes the local data described in section 3.2. But there is one difference between platforms you should know about:
On iOS, deleting the app does not reset your anonymous identity. The session is stored in the iOS Keychain, and Apple deliberately keeps Keychain entries when an app is removed. So if you delete KelimeYAP English and install it again on the same device, your progress comes back.
On Android, the session is removed together with the app's data, so reinstalling gives you a fresh start.
If you want everything gone on iOS, use Settings → Delete My Data inside the app before deleting it.
12. Your rights
Because we hold no information that identifies you, the fastest way to exercise most of these rights is the in-app delete described above. We cannot look up "your" data by name or email, because we do not have either.
If you are in the EEA, the UK or Switzerland (GDPR / UK GDPR), you have the right to access your data, to have it corrected, to have it erased, to restrict or object to processing, to data portability, and to withdraw consent at any time where processing is based on consent. Withdrawing advertising consent is done in the app and has no effect on the lawfulness of processing before you withdrew it. You also have the right to lodge a complaint with your national data protection authority.
If you are in Türkiye (KVKK, Law No. 6698), you have the rights set out in Article 11: to learn whether your personal data is processed, to request information about it, to learn its purpose of processing, to know the third parties it is transferred to at home or abroad, to request correction or deletion, and to object to a result arising from automated analysis. You may also apply to the Personal Data Protection Authority (KVKK).
If you are in California or another US state with a comparable law, you have the right to know what is collected, to request deletion, and to opt out of the "sale" or "sharing" of personal information. We do not sell your personal information and we do not share it for cross-context behavioural advertising unless you have given consent to personalised ads, which you can withdraw at any time in the app.
For anything you cannot do yourself in the app, contact info@obliquex.com.
13. Children's privacy
KelimeYAP English is not directed at children under 13. We do not knowingly collect data from anyone under 13, in line with the Children's Online Privacy Protection Act (COPPA) and equivalent rules elsewhere. Since the app has no accounts and asks for no personal details, we have no way to identify a user's age. If you believe a child under 13 has used the app and you want their data removed, use the in-app delete or write to info@obliquex.com.
14. Changes to this policy
If what the app does with data changes, this page changes with it, and the "last updated" date at the top is revised. If a change is significant, we will say so in the app and ask for your permission where the law requires it.
15. Contact
The developer of KelimeYAP (as listed on the App Store and Google Play), Ankara, Türkiye
info@obliquex.com