Privacy Policy

Last updated: 20 October 2026

1. Data controller

The publisher and data controller of the kaydur game and the kaydur.com website is KUTBU, LLC (Delaware, United States). For any question about this policy: destek@kaydur.com

2. Scope

This policy describes the kaydur.com web game and the Kaydur iOS and Android apps. The mobile section below describes iOS and Android features, including ads that are not active on this website. kaydur is a family-friendly word game played in Turkish and English.

3. What we do not collect

The web game and guest-account flow do not request the following; optional sign-in, support correspondence and mobile advertising are described separately below:

• name, age, date of birth, e-mail address or phone number;
• a nickname you type or a password (the nickname in online play is picked from a preset list; the account has no password);
• location, contacts, photos, camera or microphone data;
• an advertising identifier or any cross-device tracking identifier;
• advertising data; optional usage analytics and analytics cookies are described in section 4a.

The game has no chat and no free-text fields. In optional online play, the only contact with other players is a handful of symbol reactions picked from a preset list (section 5).

4. What is stored on your device

So the game can continue where you left off, the following is kept only on your device (on the web in your browser's local storage, on mobile in the app's own storage):

• settings: menu language, word language, sound, vibration, reduced motion, calm mode, touch mode, and a colour-vision preference carried over from an earlier version of the game;
• display and access preferences (per device): theme (like the device / light / dark), text size, easy-read letters, simple words, bigger buttons and more time in timed matches;
• the players on this device (up to four): only a slot number and the preset avatar picked (one of eight drawings); no names are kept;
• level progress, stars and the words you found (the Word Notebook);
• daily puzzle results, the days you completed and your streak;
• badges and the in-game counts they are based on (such as words found, hints and undos);
• a summary of recent Your Turn matches (score, winning side, bot level) and an unfinished game or match (no player names are kept);
• which steps of the tutorial were seen, a marker that the introduction was completed, and the version number of the save format;
• when the game was first opened on this device, the last day it was opened, the number of different days it was opened, and counts of in-game events (for example how many levels were started); these stay on the device and are shown only to you, under Settings → "Play & data". The records themselves are sent nowhere; if you turn on usage data, only coarse ranges derived from them (for example how many days the game has been installed and the range of completed levels) are sent under section 4a;
• your coin balance and coin transactions, your quest and daily gift progress, your streak, your event results; if you joined the leaderboards, results waiting to be sent to the server (section 5a);
• which boards you finished with their extra goal and mini goals, the boards you won with a combo, and in Endless Layers the next board and how many boards and stars you won (board numbers and small numbers only; no word and no time is kept);
• the last good copy of the save, so it can be restored if the save is damaged;

This information is not sent to our servers and does not identify you. (If you turned on online play, what is kept on the device and on the server is in section 5; if you joined the leaderboards, what is sent to the server is in section 5a.) You can delete it at any time; the steps are on the Support page. If you clear your browser data or uninstall the app, we cannot restore your progress, because we hold no copy of it; the one exception is the cloud save you turned on with your online account (section 5a).

The website also keeps a copy of its own files (game code, word lists, fonts) in your browser's cache so it can open without a connection, and asks its own server for a small version file to learn whether a newer version exists. Neither the copy nor that request contains any information about you; the copy is removed when you clear the site's data in your browser. For the same purpose the browser keeps two technical markers: the day on which the open version was last confirmed as current, and the version the page was reloaded for (the second is removed when the tab closes). Both contain only a version identifier and a date.

The website and mobile app request a small settings file from our server to learn which features are switched on. This request includes no account identifier or cookie. As with other server connections, the provider can process the IP address and technical connection metadata described in section 6. The last answer is kept locally so settings can be applied without a connection.

On mobile, your device's own backup (the device backup in your iCloud or Google account) may include the app's data. That backup is in your account and never reaches us; if you restore your device from such a backup, the progress in it may come back.

4a. Optional usage data and diagnostics

To improve the game, usage data is on by default in most countries, Turkey included; when your device's time zone points to the European Economic Area, the United Kingdom or Switzerland (or cannot be read), you are asked on first launch and nothing is sent unless you agree. While it is on, Firebase / Google Analytics receives game events (screens, button categories, modes, level numbers, results, hints and durations), coarse error codes, language/app/content version and progress buckets. Stored local counters, raw words, names, friend and recovery codes, account/session identifiers and free text are never uploaded by this layer. No advertising identifiers, ad personalization or Google Signals are used.

Firebase uses a pseudonymous installation identifier; on the web Google Analytics may set first-party analytics cookies. Google processes connection metadata to provide its service; we add no IP-derived data. These data are not linked by Kaydur to your online account or used for cross-app advertising tracking. They are not anonymous data. Google may process data internationally. See Firebase privacy information.

You may turn Usage data off at any time without losing access to the game. New collection stops and pending application events are discarded; local gameplay counters continue on your device. On the web, turning it off also deletes the Google Analytics cookies from this browser and asks Firebase to delete the installation identifier; if you turn it on again later, a new identifier is created. Opting out does not automatically erase previously received Google Analytics data. Contact us about data rights. Retention and international-transfer arrangements are being reviewed before activation; our proposed event-data retention is two months.

5. Online play (optional)

You can play kaydur without an account. If you want to play live with your friends, you can open an online account from "Play with friends" on the home screen. The account is created when you tap "Get started"; until you do, none of the data in this section is collected.

What we do not ask for. Opening an account never asks for an e-mail address, phone number, name, password, age or date of birth. Because we do not ask for an age, we do not know the age of the person who opens an account.

Your account identifier and online gameplay records are linked to your account. The absence of a real name does not make these records anonymous.

What is stored on our server, and for how long.

• account ID: a random number we generate, and the time the account was opened;
• nickname and avatar: you do not type the nickname; it is picked from a preset word list and only the positions in that list are stored. The avatar is one of the preset drawings. The language you chose is stored too;
• your friend code: the six-symbol code you share with friends. You can renew it at any time; the old code stops working at once;
• your friends list and the players you blocked;
• friend requests: who you sent a request to, who sent one to you, and the outcome. An unanswered request expires after 7 days; the record of a closed request is deleted after 30 days;
• online match records: who you played with, the moves made, the score and the result. The record of a finished match is deleted after 30 days;
• correspondence matches: so play can continue while the app is closed, the participants, language, boards, moves, score, result and move times of ongoing matches are stored on our server. This record is kept while the match is ongoing and for 14 days after it ends; an archive copy of the finished match is kept for 30 days after it ends;
• The match settings also retain the rule version used when the match started, so saved moves keep the same scoring and turn order. It follows the same retention and deletion rules as that match.
• correspondence invitations: the sender, recipient, language, status and times are stored on our server. A pending invitation expires after 72 hours; a closed invitation is kept for 14 days after closure;
• the correspondence random-opponent queue: your account, language, reading preference and waiting times are stored on our server until you are matched, cancel or 72 hours pass;
• random-opponent skill rating: from the results of finished matches opened by the random-opponent queue, a hidden skill rating and the number of counted matches are stored on our server for each language and match type. It is only used to pair you first with a waiting player near your level; it is not shown to you or to other players during play. It is kept while your account exists, deleted when you delete the account, and included in the "Download my data" copy. The marker that says which match counts (match identifier and marking/application times) is deleted after 30 days from creation, even when skill matching is disabled;
• reports: if you report a player, who reported whom and for which preset reason. Deleted after 30 days;
• session: only a digest of the session key that recognises your device (not the key itself) and the day it was last used. A session lasts at most 365 days, or 60 days if it is not used at all; the record of a closed session is deleted after 30 days;
• if you back up your account: only a digest of your recovery code. We do not store the code itself; if you lose it, we cannot see it either;
• the version number of the notice shown when the account was opened, and the time;
• the day the account was last used (not the time of day) and your "ready to play" visibility preference.

An online account that is not used at all for 180 days is deleted automatically.

Correspondence turn, invitation and queue timers pause while the feature is off. Expired records are removed by regular cleanup; if the feature is off or cleanup is delayed, records may remain longer than the periods above. A finished match whose archive copy could not yet be created is kept until the copy is created.

What other players see. Your friends, and your opponent in an online match, see your nickname and avatar during and after a match. If you choose Random opponent, you may be matched with someone you do not know. You can block or report your opponent. Someone who knows your friend code can send you a friend request; when they send it, they see your nickname and avatar. You do not become friends unless you accept; you can decline the request, block the sender or report them. Unless you turn the preference off, your friends can see that you are "ready to play" while the game is open; no last-seen time is shown. There is no player search. Unless you join the leaderboards you have no public profile and no leaderboard row; if you join, what becomes visible is described in section 5a.

In a correspondence match, your opponent also sees your moves, score and move times. While you wait in the random-opponent queue, your identity is not shown to other waiting players.

No free-text messaging. Online play has no chat, messages, voice or photos. During a match only a handful of symbol reactions from a preset list can be sent; reactions are not stored and can be turned off at any time.

What is kept on your device. On the device where you turned on online play, your account ID, friend code, session key, nickname and a summary of your recent online matches are kept. This record is removed when you sign out or delete the account.

What we use this data for. Only to provide the online play you asked for, to recognise your account and your friends, and to prevent abuse. We do not use it for advertising, profiling or sale. To limit abuse, your IP address is processed briefly in the server's memory; it is not written to the database. When notifications are enabled and you have given permission, you may receive invitations, turn alerts, deadline reminders and match results while the app is closed. These notifications contain no nickname, account or match identifier, or score.

Deleting the account. In the game, go to Play with friends → Account → "Delete account". Your account, sessions, friends list, blocks and friend requests are deleted at once. In match and report records your account ID is blanked; those records are deleted when the periods above run out. If our hosting provider keeps backups, deleted data may remain in those backups for a period set by the hosting provider.

Deleting the account also deletes your correspondence invitations and queue entry. Ongoing correspondence matches end; the result is void unless each player has played at least one word. Your account link is removed; the opponent's match history and shared move record remain for the retention periods above.

If you backed up your account, you can also delete it without your device, with your recovery code, at kaydur.com/#/hesap-sil. If you have no access to your device and did not back up the account, we cannot verify that the account is yours, because we do not know your e-mail address or name; such an account is deleted automatically once it has not been used for 180 days. You can get a copy of your data with "Download my data" on the same screen.

The download also includes summaries of your retained ongoing and finished correspondence matches, invitation records and queue entry; it does not include your opponent's account identifier, profile or session information.

5a. Leaderboards, leagues, coins and cloud save (optional)

Even with an online account, the data in this section is not sent to our server unless you join. When you open a new account, "Start" also covers joining and the account card says so; for an account opened earlier the game asks once, "Join" / "Not now". Until you join, no score is uploaded and there is no coin balance and no cloud save on the server.

What is stored on our server once you join, and for how long.

• your daily puzzle and event results: score, word count, stars, how long you took to solve the puzzle (the server measures the time) and the log of the moves you made. The move log is only used to verify the score and to look into cheating; it is not shown to other players. Deleted after 35 days;
• your Layers level results (stars and word count): kept while the account exists; the move log of these results is deleted after 35 days;
• leaderboard entries: daily entries are kept for 35 days, weekly entries for 8 weeks, event entries subject to a 30-day retention limit once settlement has completed, and Layers stars while you remain joined. Legacy local stars can be imported once per language, up to three stars per published level; this import gives no coins or league XP;
• run start tickets: unused daily and event tickets are kept for 4 days, unused weekly puzzle tickets for 14 days to preserve their original clock and following-week eligibility; submitted tickets for 35 days after submission;
• your weekly points, your league tier and your rank in your league group: weekly records are deleted after 8 weeks; your tier is kept while the account exists;
• coins for the mini goals of a level: the server replays the move list it received, works out by itself which mini goals were met, and writes coins only once for each mini goal of each level (recorded with the same fields as other coin transactions; these once-only receipts, including zero-coin receipts at the balance limit, are kept until account deletion);
• Puzzle of the Week: the result of your first win of the week (stars, words and score) on your device; with an account, this result is checked by the server like the daily puzzle and shown on the weekly leaderboard (the same fields and the same 35-day retention as daily results);
• gems: which boards' gems you collected, on your device; with an account, the server replays the move list, works out the gems by itself and writes coins only once for each gem (these entries are kept until your account is deleted, so the same gem is never paid twice);
• Themes: which theme boards you finished and with how many stars, on your device only (never sent to the server);
• your coin balance, your coin transactions (kind, amount, day) and the looks you unlocked with coins or as rewards: other transaction records are deleted after 180 days. The records of the three rewards that are given only once per account (the welcome coins, the move of this device's coins to the account, the level rewards) are kept for as long as the account exists, so that the same reward cannot be given again. Coins are not sold for real money and cannot be transferred to another player;
• bonus words: the coins for the extra words you find on a board after winning its level are paid only by our server, after it checks every word again. For each level we keep its verified board reference and coded word records identifying words used to win and words already rewarded. Bonus transaction keys also use coded records rather than the words themselves. These account-linked records remain for the life of the account, including after leaving the leaderboards, to prevent repeat or ineligible rewards. They are included in your data download and removed when the account is deleted. Coded records are not anonymous. Without an account, or if you have not joined the leaderboards, the bonus words you find stay on your device only and are not sent to our server;
• quest and chest reward claims (period, slot and reward), and daily gift claims, are recorded in the coin ledger. Detailed quest progress stays on your device; a cloud save can contain claimed reward keys and cumulative engagement counters;
• cloud save: a summary of your game progress (level stars, the daily puzzles you solved, badges, in-game counts, the looks you wear). The Word Notebook, unfinished games and settings are not part of it. Kept until you delete it, leave the leaderboards, or delete the account. Turning off cloud save stops uploads but does not delete the existing copy;
• your player card: your level, your avatar frame, up to three badges you put on your showcase; an identifier that marks your row on leaderboards and is used in place of your account identifier; your "Appear on leaderboards" and "Cloud save" preferences.

What other players see. If you joined and "Appear on leaderboards" is on, the other players who joined the leaderboards — including players you do not know — see your nickname, avatar, level, league badge, avatar frame, showcase badges, score and how long you took to solve the daily puzzle, and the number of event boards completed. If you turn the preference off, only your friends see you on leaderboards (the preference takes effect at once; on the screen of a player who has a leaderboard open at that moment an already loaded row can remain until that screen refreshes). Non-friends see an unnamed league position ("Hidden player") and cannot open your card; mutual friends can still see your league identity and card. On the road map, only mutual friends can see your level, only while "Appear on leaderboards" is on. A block in either direction excludes the other player from the road map and card. Your account identifier, friend code, friend list and last-seen time are not shown on any leaderboard or card. No friend request can be sent and nothing can be written from a player card; a player who sees the card can only block or report you.

If you have no account or did not join. Quests, the daily gift, coins and the event can still be played; their records are kept only on your device (section 4) and are not sent to our server.

Turning it off and deleting. In the game, under Play with a friend → Account, you can turn off "Appear on leaderboards" and "Cloud save", and delete your cloud save with "Delete the copy on the server". "Leave leaderboards" deletes your engagement profile, leaderboard scores, coin balance and cloud save; your online account and friends stay. Move logs are cleared. League assignments remain to prevent repeated allocation (unfinished membership XP is reset to zero), with no public identity while you are away. Their normal 8-week retention applies after settlement. Results, start tickets and coin ledger rows retain the periods listed above; leaving does not keep all of them forever. Owned looks, Layers result marks, once-per-account reward records and a leaving record (league tier, best tier, imported languages and leaving time) remain until account deletion; the leaving record is moved back into the profile on rejoining. Your coin balance restarts at zero. Account deletion removes all account-linked engagement records in the same transaction. "Download my data" includes the stored cloud save, result logs and retained records, including those kept after leaving.

Cleanup runs hourly while the server engagement feature is enabled. Disabling it pauses automatic cleanup until it is enabled again; account deletion still works. Unsettled league groups and event leaderboard entries wait for settlement before cleanup. Match and event reward ledger records can remain past 180 days while their source records are retained, to prevent duplicate payment during recovery.

This data stays on our game server (section 7); it is not used for advertising, profiling or sale. If you turned on usage data (section 4a), your nickname, score or coin balance are not part of those records; when a league week closes your rank is recorded only as a range (1, 2–3, 4–10, 11 and beyond), and the coins you earn and spend only as a range as well.

My family (groups). If you joined the leaderboards you can start a small group or join one with a group code or an invite link. Any signed-in account with the code can preview the group's preset name, picture, size and whether it is full; the preview contains no member identities. The server stores the group's code, a name and a picture picked from fixed lists (Family, Class…; no free text, no upload), the online accounts of the founder and the members, and when they joined. On the member list every member sees the others' nickname and avatar; a member with a block between you, or a suspended one, shows as "Hidden player" without name or picture. Scores appear only on the group's ranking: you can see your own scores, your friends' scores, and scores of other members who opted into leaderboard visibility. A block, suspension or withdrawal from the leaderboards prevents those scores being shared. The founder can remove a member, hand the founder role to another member and change the group's name and picture. You can send a friend request from the group; joining a group never makes anyone your friend. Leaving or being removed deletes your membership; closing the group as its current founder deletes the group. Deleting an account removes its memberships and any groups it currently owns (a group already transferred to someone else stays); your data download lists your groups (name, picture, member count, when you joined).

Online stats and announcements. Your own match stats are computed on request from the matches already kept for 30 days; nothing new is stored and only you see them. In-game announcements arrive with the remote configuration; which ones you have seen is remembered on your device only.

Optional device notifications. If you enable notifications, we store your native APNs (iOS) or FCM (Android) device token, platform, language, notification preferences and registration activity with your online account. This identifier is used for app functionality, not advertising tracking. Apple Push Notification service or Google Firebase Cloud Messaging processes the token and generic notification content to deliver invitations and turn reminders; these providers may process data internationally. Disabling notifications, signing out or deleting the account removes the registration when the server can be reached; offline removal is retried. Registrations not refreshed for 60 days are removed by regular cleanup. Local daily reminders are scheduled on the device and do not require a server token.

6. Technical logs when you open the site

kaydur.com runs on our hosting provider, Railway Corp. (USA). When you open a page, or when online play connects to our server, the provider's systems process the following in technical logs, as happens with any website:

• IP address;
• date and time of the request, the address requested and the response status;
• browser and device type information (user agent).

These logs are used only to deliver the site, keep it secure and fix faults. They are not used to identify anyone, to build profiles or for advertising; they are not combined with other data and are not sold. How long these logs are kept is set by the hosting provider; we keep no separate copy of them.

Legal basis: our legitimate interest in delivering the site securely (GDPR Art. 6(1)(f); Turkish KVKK Art. 5/2-f).

7. International transfers

Our hosting provider, Railway Corp., is based in the United States; its servers are outside Türkiye and may be outside your own country, including in the United States. The technical logs in section 6 and, if you turned on online play, the account data in section 5 are therefore processed and stored abroad. If you turned on usage data, the data in section 4a may be processed abroad by Google (Firebase / Google Analytics). Player-visible sharing is described in sections 5 and 5a. Apart from that sharing and the service providers described in this policy, we do not share or sell your data.

8. Audience and children's privacy

Kaydur is a general-audience, family-friendly game; it is not positioned as child-directed. The game does not ask for an age, a name or contact details (the mobile app asks an age range before its first ad; see the mobile release notice below):

• The game played without an account never asks for a name, age, e-mail or photo, and sends only the coarse game events listed in section 4a while usage data is on; you can turn it off in Settings.
• Nobody needs to register, share anything or turn on usage data in order to play.
• In the web game there are no ads or cross-app advertising tracking; mobile advertising follows the age and consent controls in the mobile section below.

Online play. Opening the optional online account (section 5) does not ask for an age, and the game has no parental gate; we therefore do not know who opens an online account. Guest accounts have no real names, e-mail addresses, phone numbers, photo uploads or free text. Optional Google sign-in may show your profile photo to other players, with the hide control described below. Section 5 describes the online account data. If you do not want your child to have an online account, you can delete it on your child's device with Play with friends → Account → "Delete account"; no account is opened unless "Get started" is tapped in "Play with friends".

Usage data. Usage data (section 4a) is on by default in most countries; in the EEA, the UK and Switzerland it is asked for first. Turning it on does not ask for an age either, so we do not know who turned it on. If you do not want it to stay on on your child's device, you can turn off Settings → "Usage data".

COPPA (United States): in the game played without an account, while usage data is off, we do not collect personal information from children under 13. The technical logs in section 6 are used solely to support the internal operations of the service.

GDPR (EU/UK) and KVKK (Türkiye): the usage data of section 4a is sent in the EEA, the UK and Switzerland only with your consent (the first-launch question); elsewhere it relies on our legitimate interest in improving the game and can be turned off in Settings at any time. While it is off, nothing of that section is sent. This page also serves as the information notice.

We ask children not to e-mail us and to ask a grown-up for help instead. If we notice that a child has sent us personal information, we delete it. If you have a question about your child, or about your child's online account, write to destek@kaydur.com. This audience change and the optional analytics notice remain subject to legal review.

9. If you e-mail us

When you write to our support address, we use your e-mail address and the content of your message only to reply to you; messages are handled through our e-mail service provider. We do not keep the correspondence longer than needed once your request is resolved, and you can ask us to delete it at any time. On the website, the "Report a problem" and "Report a word" links in Settings open a new message in your own e-mail app; the message is prefilled only with the game's version, the menu and word language, and the number of the last puzzle opened. Nothing reaches us unless you send the message.

10. Mobile apps and app stores

The mobile apps work the same way: no account is needed, and when you play without one, progress stays on the device (see section 4 for your device's own backup); optional usage data is described in section 4a; online play is optional on mobile too, and section 5 applies in full. The store you download the app from (Apple App Store, Google Play) processes download records under its own privacy policy.

11. Your rights

Depending on where you live, you have the right to access your personal data, to have it corrected or deleted, to object to its processing and to complain to the competent authority (in the EU, your national data protection authority; in Türkiye, KVKK Art. 11 and the Personal Data Protection Board).

When you play without an account we keep no record that identifies you; game data is on your device and can be deleted there. If you turned on usage data, section 4a applies; you can turn it off in Settings at any time. If you have an online account, you can get a copy of your data with "Download my data" in the game and delete the account with "Delete account" (section 5). Send requests to destek@kaydur.com; we reply within 30 days at the latest.

12. Changes

On 16 October 2026, account linkage, technical requests and cloud-save support were clarified, a duplicate coin-retention entry was removed, and the mobile release notice below was added.

This policy was updated on 12 October 2026 for optional online play (section 5 was added; sections 3, 7, 8, 10 and 11 were corrected to match) and for the optional, off-by-default usage data (section 4a was added; the sentences about the parental gate were removed because the gate is gone). On the same day it was also updated for the optional leaderboards, leagues, coins and cloud save (section 5a was added; sections 4 and 5 were corrected to match). On 13 October 2026, section 5a was clarified to match stored records, retention exceptions, friend visibility and data export. On the same day, section 5 was updated to explain server storage of correspondence matches, invitations and queue entries, their retention, deletion and export. On 14 October 2026, section 5 was updated for the hidden skill rating used to pair random opponents. On 14 October 2026, section 5a gained the coin ledger record of bonus words and how long it is kept. On 17 October 2026, it was stated that Google sign-in is available in the web game, and the mobile release notice gained the age range question, the consent options and how rewarded ads pay coins. On 18 October 2026, Google profile photo storage, visibility to other players and the account hide setting were added. On 20 October 2026, usage data became on by default in most countries and asked for first in the EEA, the UK and Switzerland (section 4a). If the game gains any other feature that processes data, this policy will be updated and its date changed. The current text is always at this address.

Mobile app: advertising and consent

Google sign-in is available on web, iOS and Android; Sign in with Apple is available on iOS. The mobile app uses Google AdMob for interstitial ads and optional rewarded ads. The web game has no ads. This release has no in-app purchases or paid Remove Ads product.

• Google sign-in: the sign-in flow verifies Google's signed account document and stores a keyed digest of the Google account identifier and a masked e-mail hint. It also stores your verified Google profile photo URL. It does not store your profile name, full e-mail address or raw Google account identifier, and does not receive your Google password. These records remain linked to your account until you remove the sign-in method or delete the account. Other players cannot see the identity digest or masked hint; the profile photo follows the setting below.
• AdMob: the SDK can process IP-derived approximate location, device identifiers, ad views and interactions, crash and performance information for advertising, measurement and fraud prevention. On iOS, starting with version 1.0.0 build 6, ads are not personalized and Kaydur does not use data for tracking across other companies' apps or websites. The app does not request Apple's tracking permission. Publisher first-party advertising identifiers and publisher ad personalization are disabled, and all iOS ad requests request non-personalized ads. This does not mean that advertising processes no data. Google consent forms remain available where required, and consent may result in non-personalized or limited ads, or no ads. On Android, personalized ads are offered only in supporting builds to users who chose 18 or older, have not turned personalization off, and grant the consent required in their region. In that case, advertising identifiers and ad interactions may be combined with data from other companies for advertising. Before the first ad, the app asks a neutral age range question (under 13, 13–17, 18 or older, rather not say); it does not ask for a date of birth. The answer stays on the device; Google receives only the matching age treatment. Children, teens and users who do not state their age do not receive personalized ads. The Android personalization switch is on by default for eligible adult users and can be turned off in Settings → "Ads and privacy". Consent can be changed or withdrawn there on both platforms. Changed choices invalidate previously loaded ads; if a required consent check fails, no ad is requested. Optional rewarded ads and their coin rewards remain available subject to ad availability and daily limits. See Google's AdMob data disclosure and Google's Privacy Policy.
• Rewarded ads: watching is optional; the button shows the coins before you watch; it can be watched at most three times a day, and you are told when that is used up. If the ad is not watched to the end, fails to load or is closed, nothing is given. Without an account, or if you have not joined the leaderboards, the coins go to the wallet on your device. For a joined account only our server writes the coins, after Google confirms with a signed message that this ad was completed: the app attaches a single-use encrypted ticket that expires within two hours and contains no readable account identifier, and Google sends it back to our server with its own transaction number. The same ad is never paid twice; the coin transaction is kept for the period in section 5a. No e-mail, nickname, friend code or readable Kaydur account identifier is sent to Google through this ticket.
• Purchases: no in-app purchases are offered in this release; Kaydur receives no payment-card details.

Optional sign-in and progress saving

You may save your progress by linking Google sign-in on web, iOS or Android, or Sign in with Apple on iOS. E-mail-code sign-in is not offered. Apple sign-in requests neither your name nor your e-mail. We store a keyed digest of the provider account identifier; Google sign-in also keeps a masked address hint. Removing a method or deleting the account removes its linked identity record. Tokens are processed temporarily; replay-prevention digests expire with them.

Signing in on another device merges your saved single-player progress. If you explicitly switch between accounts, progress and server-verified wardrobe items come along; the previous account’s coins, friends and groups stay there. Cloud saving that you deliberately disabled remains disabled. A reminder stores only its last display time on this device, at most once a week. Clearing app/site data removes that time. If you enabled usage data, reminder actions and login method are measured without addresses, tokens or account identifiers.

Google profile photo. When you sign in with Google, we store your verified profile photo URL on your account; we do not store the image file on our server. The photo replaces your avatar for you, friends, opponents and other players on leaderboards and in groups, including strangers. “Show profile photo” in account settings is on by default; turn it off to hide the photo from everyone and show your preset avatar. Hidden-player rows never show a photo. Each Google sign-in refreshes the URL; a missing photo clears it. Removing Google sign-in or deleting the account removes the URL. Hiding does not delete the URL. Previously loaded screens may keep an old image until refreshed. Images load directly from Google's image server, which may receive your IP and connection information; web image requests send no referring page. Your Google name, full e-mail address and raw Google account identifier are not stored or shown to other players.

Google and Apple process the sign-in request under their own privacy policies. Apple sign-in is offered only on iOS; web Apple sign-in is not offered. E-mail-code sign-in is not offered.

Word meanings

Word definitions and inflected-word lemma mappings are dictionary content, not personal data. Meanings are shipped with the game and shown from the device. Only when the shipped data has no meaning for a word you open (for example after a dictionary update) does the game, while online, ask our server for that one word, without sign-in, cookies or any account or device identifier; like every request, it reaches our hosting provider with your IP address and the requested address (section 6). We do not store the looked-up word with your account or keep a search history, and it is not sent to usage analytics. Opening a meaning in an online match does not send that word to our server again. If you tap the Wiktionary link, the page for the word or its lemma opens in an external browser; that visit is subject to that site’s privacy rules.