Operator and contact
Dental Battle is operated by Didar Shakir / Дидар Шакир, an individual located in Almaty, Kazakhstan. For data requests, contact didar5shakir@gmail.com.
Deletion and your data controls
You can request account deletion in Settings → Account → Delete account. Without the app, email didar5shakir@gmail.com. Requests undergo ownership verification and processing; completion is confirmed separately. Periodic cleanup follows the periods below. You can change optional profile information and notifications in settings.
Sign-in and account information
For Google, Apple or email-code sign-in, Supabase Auth stores your email address, account ID, linked sign-in methods, provider identifiers and verification status. Your first successful sign-in can create an account automatically. Linking sign-in methods helps you return to the same game profile.
Google sign-in does store the provider profile name and photo URLs in authentication data, including name, full_name, picture and avatar_url. They are present in user metadata and the linked Google identity. Additional name components may be supplied by the provider. The game does not use them instead of your game nickname or avatar. Cleanup of these decorative fields is not enabled; another sign-in may supply them again.
For Apple, the app requests an email address, which may be an Apple relay address, and receives a sign-in identifier. No name or photo was found in the Apple records checked; the app does not request a name or copy one into the game profile. This does not mean Apple itself has no such information.
Sessions and tokens restore sign-in; the session stored on your phone may include provider information. The authentication service also processes IP addresses, browser or device information and sign-in times for security. If a password has been separately set for an account, Supabase stores a protected representation. The game does not receive your Google or Apple Account password.
Profile and visibility
We store your game nickname, language, account status, creation and update dates, statistics and rating. The game displays a game avatar, not your Google photograph. Your nickname and the game statistics shown in relevant screens are visible to other players.
Country, region, university, professional role and specialty are optional. You choose a country independently of your university; it is not inferred from your IP address, language or GPS. Visibility settings control publication of optional details. You can see your own choice; a hidden country and its flag are not disclosed to other players. New profiles use the current visibility settings, which you can change.
Friends, invitations, rematches and teams require related player IDs, request status, membership and roles. There is no in-app chat.
Games and analytics
The server stores match and practice history, assigned question versions, answers, attempt times, results and rating events. This supports equal questions for opponents, timing and result checks, resuming games and viewing history.
First-party app analytics uses player IDs, activity days, language, platform, version and game history. Geography in these reports comes from profiles, not location detection. Advertising analytics and cross-app tracking are not connected.
Notifications
With your consent, game push notifications cover friend requests, match and rematch invitations, turns and completed matches; separate reminders depend on your chosen categories. Phone permission and consent for that device are required. You can change categories in settings. An explicit refusal is not replaced by consent.
Delivery uses a push token, installation ID, account binding, permissions and category choices. Expo, Apple APNs and Google FCM process delivery information and notification text, which may include a game nickname. Diagnostics and delivery markers help fix failures and prevent duplicates. Requests and invitations remain available inside the game without push.
Reports, blocks and support
A personal block records the players involved to prevent new approaches. A report contains the participants, reason, comment, public nickname snapshot, status and decision. Only the authorised owner can access the private review queue; a single report does not automatically penalise a player.
Support receives the sender address, message and voluntarily supplied error details. Do not send passwords, sign-in codes, tokens, keys, identity documents, medical information or other people’s personal information. A description, game nickname and app version are usually enough to start.
Services and processing locations
Frankfurt describes the database region, not all processing. Email, push, updates, logs and providers’ infrastructure may be processed in other countries, including the United States. We do not promise that all data stays in the EU or Kazakhstan. International processing arrangements and applicable requirements remain to be resolved before public release.
These pages have no sign-in, data collection forms, advertising, embedded analytics, external fonts or tracking cookies set by us. Cloudflare still processes service information to deliver and protect the site.
- Supabase
- Database, authentication, server processing and file storage. The working database region is Frankfurt, Germany (eu-central-1).
- Google and Apple
- Your selected sign-in method and push delivery, with their own services and logs.
- Resend
- Service-generated sign-in emails sent through SMTP: recipient address, sender, subject, message content and delivery records. Resend stores data in the United States; Tokyo is the selected sending region. The app does not read your mailbox.
- Expo
- App updates and push handoff to APNs/FCM, with technical device and delivery information.
- Gmail
- The support inbox and correspondence.
- Cloudflare Pages
- Hosting these public pages and delivering files. Cloudflare processes technical request information, including IP address, page address and browser information, to operate and protect its network.
Retention periods
Account information and necessary game records are kept while your account exists. Once deletion is confirmed and carried out, personal data is removed without an artificial waiting period. Signing out or sending an email does not mean deletion is complete.
Request processing and periodic cleanup run every five minutes. Temporary failures are retried with a delay; an unfinished deletion is not marked successful. Contact support if completion is delayed. We do not promise erasure of all information and provider backups within 24 hours.
Periods for individual categories
- Profile, authentication and settings
- Until account deletion; personal data, sessions, push bindings, personal analytics and social links are then removed.
- Match history for a remaining opponent
- Necessary results remain under “Account deleted”, without the former nickname, avatar, country or access to the profile.
- Match after both players are deleted
- Residual detail: 90 days after both deletions complete, then cleanup without recalculating other players’ ratings.
- Activity linked to a player ID
- Up to 13 months, earlier on account deletion. Individual records are removed; new anonymous aggregates are not currently generated.
- Push diagnostics
- 30 days after a final state. Minimum match deduplication markers: through match completion plus 30 days.
- Inactive push bindings
- 90 days; minimal choice records preserve explicit consent and refusal rather than turning notifications back on.
- Closed directory submissions
- 90 days before removing the submission containing personal details and its author link; the approved directory remains.
- Closed reports
- 180 days after the last decision. Open cases need manual review; an active restriction lasts until lifted or the account is deleted, with manual review every 180 days.
- Support
- Approved manual periods: correspondence, 12 months after closure; diagnostic attachments, 30 days. There is no automated Gmail cleanup, and operation of the manual routine has not yet been verified.
- Deletion receipts
- 30 days after completion, without the former account ID.
- Operator-controlled protected backups
- A 7-day window; a separate minimal erasure ledger, 8 days, with unfinished entries kept until processing completes. Regular creation and expiry of all operator backups are not automated yet.
Service backups and logs
A protected database and file backup was created before the limited deletion test. A database backup alone does not guarantee recovery of a deleted authentication account. The prepared restore procedure checks application data, Auth and files separately and replays completed erasures to avoid bringing back a deleted profile.
The checked free Supabase project has no available automatic project backups. A service’s log-viewing window does not prove when all internal copies are physically erased. For our Resend Free plan, the provider specifies 30 days for email data, including message content, and separately 30 days for logs. Resend states a seven-day backup window. These are provider terms, not independently verified physical-erasure deadlines. The backup window does not mean an email is deleted seven days after sending; we have not verified the maximum time for a particular message to disappear from all backups. Deleting a game account does not itself confirm erasure from Resend logs or backups. Internal backup periods for Gmail and other providers have not been independently verified. We therefore do not promise immediate erasure of all provider logs and backups along with an account.
Access, correction and deletion
Contact didar5shakir@gmail.com to request access, correction or deletion, appeal a moderation decision or ask about retention. Support will arrange safe ownership verification without requesting a password or one-time code. Our initial-response target is three working days, not a promise to resolve every request within that time. Mandatory applicable deadlines are handled separately.
After deletion, an opponent keeps necessary history stripped of the former profile. Context may let them remember the player: replacing a technical ID does not establish complete anonymity. The deleted profile and its progress will not return. Signing in again may create a new profile or open another existing account with the same verified email. See the deletion page for the steps and consequences.
Age and policy updates
Dental Battle is intended for users aged 16 and over. We do not collect dates of birth or request an age-confirmation checkbox. This is an age condition of use, not age or identity verification. Store content age ratings are separate, as are additional requirements in individual countries.
We will update this page and its date when processing changes. It describes the current test service; publishing it is not a claim of full legal compliance in every country.