Privacy Policy

Last updated: November 4, 2026. This policy covers the Castle of Numbers iOS app and this website.

In short

  • There are no accounts. We do not ask for your name, email, phone number, location, contacts, camera or microphone.
  • The only ads are optional rewarded ads (Google AdMob), and they are non-personalized for everyone. We do not track you across apps and websites, we do not show Apple's "Allow tracking" prompt and we do not use the advertising ID (IDFA).
  • To improve the game, the app can send usage measurements without your name or any user ID (Google Firebase). You can switch it off at any time in Settings › Privacy › Analytics; in the EU, EEA, UK and Switzerland it is off by default.
  • Your game progress stays on your device.
  • This website uses no cookies and loads no third-party scripts, fonts or analytics.

1. Controller and contact

The controller is the independent developer of Castle of Numbers: Osman ASCI (bireysel geliştirici) · iletişim: destek@numcastle.com. For any privacy question: destek@numcastle.com.

2. Data that stays on your device in the app

This is not sent to the developer. Deleting the app removes it from your device (the Keychain marker depends on how Apple handles the Keychain). "Reset progress" in Settings deletes your local progress, generates a new random local ID and empties the unsent analytics queue; it does not change your Analytics switch.

3. Usage measurement (analytics)

While Analytics is on, the app sends usage events with Google's Firebase Analytics (without the advertising ID). The only purpose is improving the game: seeing difficulty balance, bugs and where players get stuck. No user ID, name, email or advertising ID is attached to events. We do not call this "fully anonymous": Firebase keeps a persistent app instance ID for the installation, and events arrive with it.

Types of data sent while Analytics is on
DataWhat it contains
Game eventsSession start and end, tutorial steps, battle start and result, which modes are used, setting changes, hint use, daily puzzle and quest events, ad events (offer, start, completion, failure).
Store eventsStore screen views, purchase attempts and outcomes: product ID, price and currency. Your payment details never reach us; Apple handles the payment.
Event and user propertiesApp version, build number, session number, days since install, install week, the race you chose, how far you have got, whether you own the Commander's Seal, experiment group.
What Firebase itself collectsPersistent app instance ID, approximate location derived from the IP address (country or region level), device model and iOS version, language and time zone.

What we do not send: name, email, user ID, free text, device name, advertising ID (IDFA), vendor ID (IDFV), precise location, contacts, photos. Ad personalization signals and advertising ID collection are switched off.

Consistency with the App Store "Privacy Details": Because these data types arrive with persistent device and app identifiers, the app's App Store privacy label cautiously marks them as "linked to you". This does not mean the data is linked to your name or email.

Retention: Analytics data is kept in Firebase for 14 months and is then deleted automatically.

Your choice: The Settings › Privacy › Analytics switch is off by default in the EU, the EEA, the UK and Switzerland, and wherever your region cannot be determined, and on by default elsewhere. The region comes from your device's region setting. Once you change the switch, your choice is kept and the region is no longer consulted. When you turn it off, the event queue is emptied, user properties are deleted, Firebase stops collecting, and Firebase's local analytics data and app instance ID on the device are reset.

4. Ads (Google AdMob) and consent

The app has rewarded ads only: you watch one if you want to, in return for a hint, star protection or a reward multiplier. This version shows no ads between levels; if they are added, this policy will be updated before that version is released. Ads are served by Google AdMob.

5. Remote configuration

The app connects to Google's Firebase Remote Config to fetch game settings (balance values, experiments, the switch that turns ads off). This is an app function that works independently of the Analytics switch. For Remote Config, Firebase creates a random Firebase Installations ID for your installation; it is sent to Google even while Analytics is off. The request sends Google your device's country code, language, time zone, iOS version and app identifiers; Google states it does not link this request data to a user or device identifier.

6. Purchases

Purchases go through Apple's App Store (StoreKit). Your card or payment details never reach us. If Analytics is on, we see a purchase only as an event (product ID, price, currency). To restore purchases on another device, use "Restore Purchases" on the store screen.

7. Sharing

Sharing is always your decision; the app sends nothing on its own and what you share is not uploaded to a server of ours. When you open the iOS share sheet, we do not see which app you send it to.

8. Third parties

We do not sell your data and do not share it with data brokers. Google AdMob is the only ad network; if another advertising service is added, this policy will be updated before that version is released.

9. Children

The app is not directed to children and does not ask your age. It creates no accounts and asks for no personal information such as name, email or location. Ads are non-personalized for everyone and their content is capped at "PG". If you are a parent or guardian and have a concern, write to us.

10. This website

11. Legal basis and transfers abroad

12. Your rights

Under applicable data protection law (for example KVKK article 11 in Turkey, or the GDPR in Europe) you may have the right to access, correct or delete your data, to object to processing, to withdraw consent and to complain to an authority. The easiest way to withdraw consent is to turn off Settings › Privacy › Analytics; for your ad consent you can use "Ad privacy options". Because we do not link analytics data to your name or email, finding the records of one particular device may not always be possible; we will still consider your request and explain if we cannot fulfil it. For requests: destek@numcastle.com.

13. Changes

If the app's data practices change, this policy is updated before the change takes effect and the date above changes.