This policy applies to the Hafıza Arena app (Android and iOS). The publisher is Talion Studio; the person responsible for app data is Can Avcılar. Privacy requests: canavcilar77@gmail.com.
In short
- No account, no sign-in. We run no server for this game.
- Your scores, statistics and badges are stored only on this device.
- In-game measurement events stay on the device and are never sent anywhere.
- Ads are served by Google AdMob; consent is requested where required. “Remove Ads” can be purchased.
Contents
Information stored on your device
The game keeps your progress in a local database on the device:
- game records: mode, level, score, duration, number of mistakes, start and end time;
- difficulty state, daily challenge attempts and daily scores;
- badges, journey stops, quests and collection;
- settings (language, sound, vibration, motion) and card back choice;
- ad frequency counters and consent status;
- the “Remove Ads” entitlement (product ID verified by the store, platform and verification time).
This information is not sent to us or to anyone else. Hafıza Arena has no account, no player profile server and no online leaderboard; your progress does not move between devices.
In-game measurement
The app produces event names to understand how the game is used (for example game started, game finished, badge earned, ad shown, purchase completed). In this version events are held only in device memory while the app is open and are not sent anywhere; the app contains no analytics SDK such as Firebase Analytics. If this changes, this page will be updated.
Ads and Google services
The app includes Google Mobile Ads (AdMob) and Google’s ad privacy choices framework (User Messaging Platform). Test builds use Google's test ads; using test ads does not mean that no data is processed. When it runs, the SDK may collect IP address (from which approximate location can be inferred), device or other identifiers (the advertising ID on Android; the IDFA on iOS if you allow it), app interactions and diagnostic information for advertising, analytics and fraud prevention, and share them with Google. This data is processed under Google's own policies; the app does not send it to us.
When are ads shown? There are no ads during play, at launch or in the tutorial. No interstitial ad and no consent form is shown before your first three completed free games; the consent form (where required) appears when you return to the home screen after the third game. Rewarded ads are entirely optional and only give cosmetic rewards that do not affect competition. Ad frequency settings may be read from a remote configuration file; that request contains none of your game data, but as with any internet request your IP address may appear in the logs of the service hosting the file.
Consent. In regions where it is legally required, such as the European Economic Area and the United Kingdom, Google's consent form is shown for personalised ads. You can change your choice later in Settings > Privacy > Privacy preferences (this row appears only where consent is required). If consent cannot be obtained or there is no internet connection, ads that are not permitted are not loaded; the game keeps working. Ad requests do not tag the app as child-directed, because the game is not directed at children.
Tracking permission on iOS (App Tracking Transparency). On iOS, Apple's tracking permission may be requested within Google's consent flow. If you do not allow it, the advertising identifier (IDFA) is not given to the app or the ad SDK; ads may still be shown and the game works the same. You can change this in iOS Settings > Privacy & Security > Tracking.
Advertising ID on Android. You can reset or delete your advertising ID in your device's Settings > Google > Ads (on some devices Settings > Privacy > Ads).
Google Privacy Policy · How Google uses information from apps that use its services · Google Mobile Ads data disclosure (Android) · Google Mobile Ads data disclosure (iOS)
Remove Ads purchase
“Remove Ads” is a one-time, permanent purchase; it removes the interstitial and rewarded ad offers shown by the app, and cosmetics unlocked by rewarded ads become available without ads. If you have purchased it, the ad consent form is not shown. Payment is handled by Google Play or the App Store; your card and payment details never reach us. Your purchase record is kept in your store account; the app only stores on the device the purchase status reported by the store (product ID, transaction state). You can restore your purchase on the same store account via Settings > Restore Purchases.
Device permissions
The app only uses internet access (for ads and purchases). It does not request access to the camera, microphone, location, contacts or photos. On iOS the only permission request is the tracking permission described above.
Deleting data and retention
Settings > Privacy > Delete data on this device removes your scores, statistics, badges and daily challenge history from this device; your purchase and settings are kept. Uninstalling the app deletes all game data on the device. Because we hold no game data about you on a server, there is no account to delete. Details: data deletion.
On-device data stays on the device until you delete it. Retention of data Google processes for advertising is governed by Google's policies, and your purchase records by Google Play's or the App Store's policies.
Recipients
The app does not transfer your game data to anyone. The ad SDK may send the information described above to Google; purchases run through Google Play or the App Store. Processing by these services may involve systems outside Türkiye. If you email support, your email address and message are processed in the support mailbox (Gmail) to answer your request; an exact retention period for support correspondence has not yet been set.
Audience
Hafıza Arena is not designed for children and is not offered in a children's category in the stores. The app makes no clinical or medical claims.
Requests and changes
For questions and requests, write to canavcilar77@gmail.com. Do not send passwords or payment details. When data practices change, this page is updated and its date changes.
Last updated: 28 October 2026