Zontact Privacy Policy

Last updated: 18 November 2026

This policy explains how Blumesoft Ltd ("Blumesoft", "we", "us") handles personal data when you play Zontact (the "game") on Android or iOS. It applies only to the game. Our website has its own policy at https://www.blumesoft.co.uk/en/privacy-policy.

We wrote this in plain language. If anything is unclear, write to us at info@blumesoft.co.uk.

1. The short version

  • You don't need an account to play, and we never ask for your name, email address or phone number. Apart from the optional league profile below, we don't collect personal data directly: your progress and settings are stored on your device (and in your device's own backup, if you have turned backups on), not sent to us.
  • The game is free and shows ads from Google AdMob. To show and measure ads and to prevent fraud, Google collects data from your device, such as your device's advertising identifier, your IP address, device information and how you interact with the game and its ads.
  • In the UK, the EEA and Switzerland (and wherever else the law requires it), the game asks for your consent with Google's consent form before Google can personalise ads, and your choices there also decide whether Google Analytics may store identifiers on your device. You can change your choice at any time: open the game's Settings and tap Privacy options. Elsewhere on Android you are not asked, and you can turn off ads personalisation in your device settings (section 9).
  • On iOS, the game asks for your permission through Apple's App Tracking Transparency prompt before your device's advertising identifier (IDFA) can be used. If you say no, you still get ads, but the IDFA is not used.
  • We use Google Firebase services. Google Analytics for Firebase helps us understand how the game is played (for example, which levels are started, won or lost, where players stop and how long a level takes); it starts collecting only after the consent step has run (section 3.5). Firebase Crashlytics sends us crash and error reports. Firebase Remote Config lets us adjust game settings, such as how often ads appear, without an app update, and Cloud Storage for Firebase delivers new or updated level files. They use random identifiers for each installation of the game, not your name.
  • Our own ads for the game: we advertise Zontact, for example with Google Ads. To learn which of our ads bring players, Google Analytics shares the game's installs and a few of its events (such as finishing the tutorial) with our Google Ads account (section 3.5).
  • Leaderboards: where the game offers its leaderboards (through Game Center on iOS or Google Play Games on Android) and you are signed in to that service, your scores (the number of levels you have solved, your time on the daily puzzle and, if you play Challenge mode, your Challenge points this week and in total) are posted there. Other players can see them with your player name. Apple and Google run these services under their own terms.
  • The weekly leagues are optional: you can play without them, and without an account. If you join, we create an anonymous league profile (no password, email address or sign-in) on Google's servers in the USA, with the name the game makes up for you and your weekly points, which the players of your weekly group see. You can delete it at any time in the game (section 3.15).
  • The daily reminder is optional. If you turn it on, your phone shows one notification a day when the new daily puzzle is ready. It is scheduled on your device: nothing is sent to us or anyone else to deliver it (section 3.10).
  • Buying us a coffee is optional: an in-app purchase that Google Play or the App Store handles and takes the payment for. We never see your card or payment details (section 3.14).
  • We don't sell your personal data for money. Personalised ads may count as "selling" or "sharing" under some US state laws; section 10 explains how to opt out.
  • Zontact is not directed at children under 13.

2. Who is responsible for your data

The data controller is:

  • Blumesoft Ltd, registered in England and Wales, company number 12483514
  • Registered office: Unit Da2 Sutherland House, Sutherland Road, London E17 6BU, United Kingdom
  • Email: info@blumesoft.co.uk
  • ICO registration number: ZC283419

We are based in the United Kingdom, so the UK GDPR and the Data Protection Act 2018 apply to what we do with personal data. Our supervisory authority is the Information Commissioner's Office (ICO). We have not appointed a data protection officer; please send all privacy questions and requests to the email address above.

Google acts as our service provider for some processing (Google Analytics for Firebase, Firebase Crashlytics, Firebase Remote Config and Google BigQuery, and, for the weekly leagues, Firebase Authentication, Cloud Firestore, Cloud Functions and App Check) and as an independent controller for other processing (for example, when it uses data from ad requests for its own advertising services). Google's own privacy policy applies to that processing: https://policies.google.com/privacy. Google explains how it uses data from apps that use its services at https://policies.google.com/technologies/partner-sites.

Apple (Game Center) and Google (Google Play Games) run the leaderboard services as independent controllers, under their own terms and privacy policies (section 3.8).

3. What data is processed

3.1 Data that stays on your device

The game keeps the following on your device; it is not sent to us: which levels and daily puzzles you have solved, your daily streak, your time on each daily puzzle and whether you used a hint on it, the last level you played, how many attempts each level took, how long you have played a level you have not solved yet, the mode you play in (Normal or Challenge), your Challenge points (per level, this week and the week before) and, for a level you have not cleared yet in Challenge mode, its clock and mistakes so far, when the game last asked for a store rating, whether it has shown you the "buy me a coffee" card, how many coffees you have bought and the store's transaction numbers of the ones it has thanked you for, whether the consent step has run, and your settings (such as sound, language, theme and color shapes). Google's consent software also stores your consent choices on your device. Only if you join the weekly leagues does the game send the points that count for them to our league server (section 3.15).

Device backups. If backups are turned on for your device, this information is also included in them: on Android in the backup that Android keeps in your Google account, and on iOS in your iCloud or computer backup. We can't access these backups; Google and Apple keep them under their own terms. On Android, the backup is restored automatically when you install the game again, so your progress, settings and consent choices come back. On iOS, they come back only if you restore your device from a backup.

Uninstalling the game (or clearing its data) deletes this information from your device, but not from a backup that already exists.

3.2 Advertising (Google AdMob)

The game shows full-screen ads between levels (and sometimes when you restart a level, or when you choose Restart or Home after running out of hearts) and offers optional rewarded ads (for example, watch an ad to get a hint or an extra heart). The ads are provided by Google AdMob. According to Google's disclosures for the Google Mobile Ads SDK, the SDK collects, automatically:

  • IP address, which may be used to estimate the general location of your device (coarse location, for example the city or country);
  • device and advertising identifiers: on Android, the advertising ID and the app set ID; on iOS, the advertising identifier (IDFA) only if you allow tracking, and other identifiers limited to an app or a developer;
  • product interactions, such as app launches, taps and video views;
  • advertising data, such as which ads you have seen;
  • diagnostic and performance information, such as app launch time, hang rate, energy usage and crash logs related to the ads SDK;
  • general device information, such as device model, operating system and language.

Google uses this data to serve ads, limit how often you see the same ad, measure ad performance, prevent fraud and abuse, and show ads personalised to your interests. In the UK, the EEA and Switzerland, ads are personalised only if you consent in the consent form, and on iOS your IDFA is used only if you allow tracking. Elsewhere on Android you are not asked: ads can be personalised unless you delete your advertising ID or turn off ads personalisation in your device settings (section 9).

Personalised and non-personalised ads. Personalised ads are chosen using information about you, such as your past activity. Non-personalised ads are chosen using context, such as the app you are using and your general location, and are not based on your past behaviour; Google may still use identifiers or cookies for frequency capping, aggregated ad reporting and fraud prevention. In the UK, the EEA and Switzerland, if you don't give consent in the consent form, Google may show only non-personalised or "limited" ads.

When you start the game, Google's User Messaging Platform (UMP) checks whether a consent message applies where you are. In the UK, the EEA and Switzerland, it shows a consent form (based on the IAB Europe Transparency & Consent Framework) before ads are requested. The form lists Google and the ad partners and lets you accept, decline or choose purposes one by one. Your choice is stored on your device and sent with ad requests. Your choices also apply to Google Analytics (section 3.5): if you don't consent, Analytics stores no identifier on your device and keeps only counts without one (Google's "consent mode").

To change your choice at any time: open Settings (the sliders button at the top right of the home screen or of a level), then tap Privacy options at the bottom. This link is shown whenever Google's consent software says that a privacy choice is available for your region.

3.4 App Tracking Transparency (iOS)

On iOS, the game may first show a short Google message explaining why it asks, and then Apple's App Tracking Transparency prompt. If you tap Allow, the Google Mobile Ads SDK can use your IDFA for advertising, which can involve linking data about you with data from other companies' apps and websites ("tracking"). If you tap Ask App Not to Track, the IDFA is not available to the game or to Google, and you still see ads. You can change this at any time in Settings > Privacy & Security > Tracking.

3.5 Analytics (Google Analytics for Firebase)

We use Google Analytics for Firebase for product analytics: to understand how the game is played so we can balance levels, fix problems and decide what to improve. On a first start, Google Analytics collects nothing until Google's consent software has answered: in the UK, the EEA and Switzerland, until you have answered the consent form (section 3.3); elsewhere, until it has said that no consent is needed where you are. The game events of those first moments wait on your device until then; if there is no answer (for example, offline), they are not sent. It records:

  • a random app instance ID that Analytics assigns to each installation (it is not your name, email address or phone number);
  • game events we send, for example: a level was started or finished, whether it was won or lost and why, how many taps and attempts it took and how long it lasted, how far into a level the game was left (the move) and how long a level was played in all until it was solved, which screen was open (for example the lobby, Settings or a level) and when the game went to the background, how smoothly a moving board was drawn (its frame rate), when the tutorial was started and completed, when a hint was used, when an ad was offered, shown, rewarded or failed to load, when you signed in to or opened the leaderboard, whether you turned the daily reminder on or off and whether your phone allows its notifications, when you opened the game from a reminder, when the game offered an update or asked for a store rating, when you tapped Share (where, whether the message carried a level or a daily puzzle, and whether the share window opened), when the game showed the "buy me a coffee" card and what you tapped on it, whether a coffee went through, was cancelled or is waiting for payment, which mode you play in (Normal or Challenge) and when you switched it, the points of a level you cleared in Challenge mode (with its time, the time to beat and your mistakes), when the game offered you the weekly leagues and whether you joined, your league, your place in your group, a week's result and whether you deleted your league profile (never your league player ID, player code or name), how many levels you have solved, and your language and sound settings in the game;
  • events Analytics collects automatically, such as first open, sessions, engagement time, app updates and ad impressions, and in-app purchases (the product, its price and currency; see section 3.14);
  • device and app information, such as device model, operating system version, app version and language, and an approximate location (country, region or city) that Google derives from your IP address;
  • where the analytics software has access to it, your device's advertising identifier (on iOS, only if you allow tracking).

Measuring our own ads. We advertise the game, for example with Google Ads. Our Google Analytics is linked to our Google Ads account, so that we can see which of our ads led to installations and whether those players went on to play, and so that Google can show our ads to people more likely to enjoy the game. For this, Google Analytics shares with Google Ads the installation (first open) and a few of the game events above, such as finishing the tutorial, with the campaign information Google Play passes to a new installation (on Android) and, where the analytics software has access to it, your device's advertising identifier (on iOS, only if you allow tracking). In the UK, the EEA and Switzerland this follows your choices in the consent form (section 3.3). Google Ads shows us the results in aggregate, for example "how many players finished the tutorial after this ad"; it doesn't tell us who you are.

We look at this data mostly in aggregate reports (for example, "how many players finished level 20"). To see where players get stuck, we sometimes look at the order of the game events of a single installation, which is known to us only by its random app instance ID. We also copy these events into Google BigQuery, Google's database service in our Firebase project, to answer such questions (section 7 says how long we keep them). We don't use this data to identify you, and we don't send Analytics your name or contact details, because we don't have them.

3.6 Crash and error reports (Firebase Crashlytics)

We use Firebase Crashlytics to find and fix crashes and errors. When the game crashes, or when an error happens in the game's code, Crashlytics sends us a report with:

  • the crash stack trace (the technical details of where in the code the problem happened) and the error message;
  • the state of the app and the device at that moment, for example device model, operating system version, app version and available memory;
  • a random Crashlytics installation identifier, used to count how many installations a problem affects, and the Firebase installation ID (section 3.7). Neither is your name, email address or phone number;
  • where you were in the game at that moment (the screen, the level, the attempt, the mode (Normal or Challenge), the game's language and version, the set of levels and, if you joined the weekly leagues, your league) and the game's own log of what happened just before: its game events (the ones of section 3.5), your taps on the board, screen changes, the game going to the background and back, and ads opening and closing. This log is kept on your device and sent only with a crash or error report, also if you did not consent to analytics, because it contains no identifier; we use it only to find the cause of a problem.

Crash reports are not linked to the Google Analytics app instance ID. With analytics consent, Crashlytics can also show the Google Analytics events recorded just before the crash. If we change a setting gradually with Remote Config, a report can also show which version of the settings you had. We don't add your name or contact details to crash reports, because we don't have them.

3.7 Game settings (Firebase Remote Config)

We use Firebase Remote Config to change some game settings without releasing an update, mainly how often ads appear (for example, from which level full-screen ads start and the minimum time between them). When the game starts, it asks Firebase for the current settings. For this, Remote Config uses:

  • the Firebase installation ID, a random identifier for this installation of the game (not your name, and not a device identifier);
  • your country, language and time zone, your operating system version, and the game's app ID and version, so that settings can be chosen for a region or an app version.

Because the game also uses Google Analytics, Remote Config can use Analytics information, such as when you first opened the game, to choose settings.

Remote Config can also point the game to a newer set of levels. The game then downloads that level file from Cloud Storage for Firebase. Like any download, this needs your device's IP address, which Google uses only to deliver the file; the request contains no account, identifier or game progress, and we don't receive your IP address.

3.8 Leaderboards (Game Center and Google Play Games)

The game can show these leaderboards: Levels solved, the number of different levels you have solved; Daily puzzle time, the time you took to solve the day's puzzle for the first time (sent only if you solved it without a hint); and, for Challenge mode, Challenge points this week and Challenge points in total, the points you scored by clearing levels in Challenge mode (sent only if you play in Challenge mode). It uses Game Center on iOS and Google Play Games on Android. We don't create an account for you; the leaderboard uses the player profile you have with Apple or Google.

  • iOS: the game asks Game Center to sign you in when it starts (Apple may show its sign-in screen if you aren't signed in yet). When you are signed in, the game sends Apple your scores.
  • Android: if you have a Google Play Games profile, Play Games signs you in automatically when the game starts. If you don't have one, Google may offer to create one. When you are signed in, the game sends Google your scores.

Apple and Google store your scores with your player ID and show them on the leaderboards with your player name (your Game Center nickname or Play Games gamer name) and your avatar:

Apple and Google process this data as independent controllers, under their own terms and privacy policies. The game itself doesn't store your player name or ID and doesn't send them anywhere else. We run no server for the leaderboard. If you don't sign in, the game works the same, just without the leaderboards.

3.9 Crash and diagnostic reports from Apple and Google

If you have agreed in your device settings to share diagnostics with app developers, Apple (App Store Connect) and Google (Google Play Console) may give us crash reports and aggregated statistics about the game, such as device model, operating system version and the technical details of a crash. These reports don't identify you. You control this in your device settings.

3.10 Daily reminder (optional)

The game can remind you when a new daily puzzle is ready. It is off until you turn it on: the game asks you once, after you first solve a daily puzzle, and you can turn it on or off at any time in Settings > Daily reminder. On iOS and on newer Android versions, your phone also asks whether the game may show notifications.

The reminder is scheduled and stored on your device. The game asks your phone's own notification system to show one notification a day, at most seven days ahead, and renews them when you open the game. Nothing is sent to us or to anyone else to deliver the reminders: the game uses no push notification service. Your choice is stored on your device with your other settings.

To stop the reminders, turn them off in Settings > Daily reminder, or turn off the game's notifications in your phone's settings. Uninstalling the game removes them too.

Whether the game has asked you, whether you turned the reminder on or off, whether your phone allows the game's notifications, and when you opened the game from a reminder (how many minutes after its time) are part of the game events we send to Google Analytics (section 3.5).

3.11 Contacting us

If you email us, we receive your email address, your message and anything you attach, and we use them to answer you.

If you write to us from the game (Settings > Contact us), your mail app opens with our address, and the mail already contains the game's version, your phone's system and its version (for example "Android 15"), the game's language and how far you are in the game (your level, how many levels you solved, your daily streak and the level set) and, if you have joined the weekly leagues, your player code, so that we can find your league profile (section 3.15). You can change or delete these lines; nothing is sent until you send the mail yourself.

3.12 Store ratings

When the game asks for a rating, the window is Google Play's or the App Store's own. Your stars and review go to Google or Apple under their terms; we see them only as a public review in the store. The game only records on your device when it last asked.

3.13 Sharing the game

You can share the game after you solve a level, from the "buy me a coffee" card and from Settings > Share Zontact, to race your friends. The game opens your phone's own share window with a short message and a link to the game. The message says what you just did (for example the level you cleared, or your time on the day's puzzle) and challenges your friends; you choose the app and the people, and you send it there, so the message goes only where you send it. The game doesn't see your contacts or what you send. Your phone tells the game which app you picked; the game doesn't keep or send that. Sharing gives you nothing in the game. Whether you tapped Share, where, whether the message carried a level or a daily puzzle and whether the share window opened are part of the game events we send to Google Analytics (section 3.5).

The link leads to a small page that sends whoever opens it to the App Store or Google Play. Google's Firebase Hosting serves it, so Google's servers receive the visitor's IP address and browser details to deliver the page, as with any website. The page has no analytics, no cookies and no forms, and we get nothing from it.

3.14 Buying us a coffee (in-app purchase)

After you have played for a while, the game shows a card once that asks whether you would like to buy us a coffee; later a coffee cup in a corner of the home screen opens it again. The coffee is an optional in-app purchase that you can make as often as you like. It is a thank-you and unlocks nothing in the game.

Google Play (on Android) or the App Store (on iOS) handles the purchase under their own terms and privacy policies: they show the price, take the payment and keep the record of your purchase. We never see your name, card or payment details. The store tells the game on your device that the purchase went through (with the store's transaction number), and the game confirms it back to the store so that you can buy another one later. The transaction numbers of coffees the game has thanked you for stay on your device (section 3.1); the game sends them nowhere. The stores give us sales reports, which don't tell us who you are. Refunds go through Google Play or the App Store.

Whether the card was shown, what you tapped on it and whether a coffee went through are part of the game events we send to Google Analytics, and Google Analytics also records the purchase itself as an "in-app purchase" event with the product, its price and currency (section 3.5).

3.15 Weekly leagues and your league profile (optional)

You can play the game without joining the weekly leagues. If you tap Join, we create a league profile for you with Firebase Authentication from Google: an anonymous player ID, without a password, an email address or a sign-in. We keep, on Google's Cloud Firestore and Cloud Functions in the USA: that ID; the name the game gave you (a number that each phone shows as an adjective and an animal in its own language, such as "Happy Fox"; you can't type or change it); a short player code; your league and the leagues you reached; the points of the levels and daily puzzles that scored (the level, the time it took, the mistakes) and your places in the weekly groups; and the version of our Terms of service that you accepted. The players of your group see your name, your player code, your league and your points. Google Analytics and Firebase Crashlytics never receive your player ID, player code or name.

To keep the leagues fair, the game sends Google's integrity check with its calls (App Check: Play Integrity on Android, App Attest on iOS), and we may remove a profile that cheats. We keep a profile for 12 months after its last league week, and the weekly groups for 8 weeks (section 7). You can delete your league profile at any time in the game (Settings > Delete league profile), or by writing to us with your player code (section 9); your levels and points on your phone stay.

3.16 What we don't collect

No account with a password or an email address (the optional league profile is anonymous, see 3.15); no name, email address or phone number (unless you email us; the leaderboard uses the player name you have with Apple or Google, see 3.8; the weekly leagues show a name the game makes up, not a name you type, see 3.15); no precise location; no contacts, photos, camera or microphone; no payment details (Google Play and the App Store take the payment for a coffee, see 3.14); no push notification token (the daily reminder needs none, see 3.10); no data from your other apps.

4. Why we use your data and our legal bases

The legal bases below are those of the UK GDPR and the EU GDPR.

PurposeDataLegal basis
Show ads that fund the free game, limit how often you see them, measure them and prevent ad fraud3.2Where storing or reading information on your device requires it (UK, EEA, Switzerland), your consent given in the consent form; otherwise, our legitimate interests (funding a free game) and those of Google (preventing fraud)
Personalised ads3.2Your consent in the consent form (UK, EEA, Switzerland) and, on iOS, your App Tracking Transparency permission; elsewhere, where the law doesn't require consent, our legitimate interests (funding a free game), with the opt-out in your device settings (section 9)
Ask for and remember your privacy choices3.3, 3.4Legal obligation (to obtain and record consent where it is required)
Understand how the game is played and improve it3.5Where storing or reading identifiers on your device requires it (UK, EEA, Switzerland), your consent in the consent form; otherwise our legitimate interests (improving the game and fixing problems)
Measure our own ads for the game and show them to people likely to enjoy it3.5Where the law requires it (UK, EEA, Switzerland), your consent in the consent form; otherwise our legitimate interests (finding players for the game without wasting its ad budget)
Find and fix crashes and errors3.6, 3.9Our legitimate interests (a working game)
Change game settings, such as how often ads appear, without an app update3.7Our legitimate interests (balancing the game and its ads)
Post your scores to the leaderboards3.8Our legitimate interests (offering a leaderboard to players who use Game Center or Google Play Games)
Run the weekly leagues you joined: your league profile, your points, your weekly group and its results3.15Contract (providing the feature you asked for when you joined)
Keep the weekly leagues fair and secure: check that calls come from the genuine game (App Check), and find and remove profiles that cheat3.15Our legitimate interests (fair play for all players and the security of our service)
Answer your emails3.11Our legitimate interests (helping you); contract, where your question is about the game
Ask for a store rating3.12Our legitimate interests (being rated in the stores); the rating itself is handled by Google or Apple
Sell you the optional coffee and thank you for it3.14Contract (your purchase), which Google Play or the App Store handles
Comply with the law and protect our legal rightsas neededLegal obligation; legitimate interests

Where we rely on legitimate interests, we have weighed our interests against your rights and expectations; you can ask us for details and you can object (section 9). Where we rely on consent, you can withdraw it at any time with Privacy options; this doesn't affect what happened before.

5. Who we share data with

  • Google (AdMob; Google Analytics for Firebase, Firebase Crashlytics, Firebase Remote Config and Google BigQuery; Google Ads, for measuring our own ads (section 3.5); and Google Play Games on Android, if you use the leaderboard): as described in sections 2 and 3. Ad requests can also reach the ad partners listed in Google's consent form, according to your choices there.
  • Google as our processor for the weekly leagues (Firebase Authentication, Cloud Firestore, Cloud Functions and App Check), if you join them: your league profile and points, as described in section 3.15.
  • Apple (Game Center on iOS, if you use the leaderboards): your scores, as described in section 3.8.
  • Other players: your player name, avatar and scores on the leaderboards (section 3.8), shown by Apple or Google; and, if you join the weekly leagues, the players of your weekly group see your generated name, your 5-character player code, your league and your points (section 3.15).
  • Apple and Google as app store operators: they give us aggregated statistics and crash reports (section 3.9) and process data under their own policies when you download the game, and when you buy a coffee in it (section 3.14).
  • Authorities, courts or advisers: when the law requires it or to protect our rights.
  • A buyer or successor: if our business or the game is sold or reorganised; this policy would continue to protect your data.

We don't sell personal data for money, and we don't share it with data brokers.

6. International transfers

Blumesoft Ltd is based in the United Kingdom. Google processes data in the United States and in other countries; the data of the weekly leagues (section 3.15) is stored in the United States (Google Cloud's us-central1 region). Where data leaves the UK or the EEA, Google relies on safeguards such as its certification under the EU-U.S. Data Privacy Framework and the UK Extension to it, and on standard contractual clauses in its data protection terms. Apple and Google explain the safeguards for Game Center and Google Play Games in their own privacy policies. You can ask us for more information about these safeguards.

7. How long data is kept

DataHow long
Progress, settings and consent choices on your deviceUntil you uninstall the game or clear its data. Copies in your own Google or iCloud device backups, if you use them, are kept under Google's or Apple's rules
Analytics data (Google Analytics for Firebase)User-level and event-level data: 2 months (our Google Analytics setting). Aggregated reports that don't identify anyone may be kept longer.
Analytics events copied to Google BigQuery2 months (the dataset's table expiration)
Crash reports (Firebase Crashlytics)90 days; then Firebase starts removing them from its live and backup systems
Crash reports copied to Google BigQuery90 days (the dataset's table expiration)
Firebase installation ID (used by Remote Config)Until we ask Firebase to delete it; Firebase then removes it from its live and backup systems within 180 days
Your league profile (weekly leagues)12 months after its last league week or its last change, unless you delete it sooner (section 9)
Weekly groups (the names, player codes, leagues and points of their players)8 weeks after the week ends
Your places in past weekly groups, after you delete your league profileOnly as an anonymous entry with points, so that the other players keep their places, until the group itself is deleted (above)
Anonymous sign-ins that have no league profile (for example, when joining didn't finish)About 30 days: our monthly clean-up deletes them once they are more than 30 days old
Leaderboard scores and your player profile (Game Center, Google Play Games)As set by Apple and Google; you can manage this in your Game Center or Google Play Games settings
Data Google collects for advertisingAs described in Google's retention policy: https://policies.google.com/technologies/retention
Crash reports and statistics from Apple and GoogleAs set by Apple and Google
Records of your in-app purchases (Google Play, App Store)As set by Google and Apple; the transaction numbers on your device until you uninstall the game
Emails you send us2 years after your last message

8. Children

Zontact is not directed at children under 13, and we don't knowingly collect personal information from children under 13. In the app stores, the game is listed as not designed for children. Because the weekly leagues are a ranking among players, the App Store rates the game 13+. Its other age ratings describe its content (an abstract puzzle with no objectionable material); they don't mean that the game is made for children.

If you are a parent or guardian and believe your child under 13 has given us personal information (for example, by email or by joining the weekly leagues), contact us at info@blumesoft.co.uk and we will delete it.

9. Your choices and your rights

Choices you can make at any time:

  • Ads consent: Settings > Privacy options (where shown).
  • Tracking on iOS: Settings > Privacy & Security > Tracking.
  • Advertising ID on Android: you can reset or delete your advertising ID, or turn off ads personalisation, in your device settings (on most devices: Settings > Google > Ads, or Settings > Privacy > Ads).
  • Everything on your device: uninstall the game, or clear its data. A copy in your device's own backup (Google or iCloud), if you use backups, stays there under Google's or Apple's rules; on Android it is restored if you install the game again.
  • Daily reminder: Settings > Daily reminder in the game, or turn off the game's notifications in your phone's settings.
  • League profile: Settings > Delete league profile in the game deletes it at once. You can also write to info@blumesoft.co.uk with your player code (the game's Contact us mail adds it for you). Your levels and points on your phone stay. https://www.blumesoft.co.uk/en/yanki/delete explains both ways.
  • Leaderboard: don't sign in to Game Center or Google Play Games, or sign out in your device settings. You can manage or delete your Google Play Games profile and its game data at https://play.google.com/games/profile or in your Google Account. Apple explains your Game Center choices in its Game Center & Privacy notice (section 3.8).
  • Analytics, crash reports and game settings: these stop when you uninstall the game. Because this data is tied only to random identifiers for each installation, we usually can't find "your" data from an email request alone; if you want us to try, tell us and we will explain what we can do.

Your rights (UK GDPR and EU GDPR). You can ask us to: access your data and get a copy; correct it; delete it; restrict how we use it; object to how we use it (including our use of analytics based on legitimate interests); receive data you gave us in a portable format; and withdraw consent where we rely on it. Write to info@blumesoft.co.uk. We reply within one month. It's free unless a request is clearly unfounded or excessive. Because we don't know who our players are, we may not be able to link a request to data held in analytics or by Google; we will tell you if that is the case. To get a copy of your league profile, or to have it deleted, send us your player code (Settings > Contact us adds it to the mail) and we can find it; https://www.blumesoft.co.uk/en/yanki/delete explains how. For leaderboard data, Apple and Google can also help you directly.

Complaints. You can complain to the UK Information Commissioner's Office (ico.org.uk) or, in the EEA, to the data protection authority where you live. We'd appreciate the chance to help first.

10. Information for players in the United States

Categories of personal information. The categories collected through the game in the last 12 months are: identifiers (advertising ID and other device identifiers, app instance ID, Firebase and Crashlytics installation IDs, IP address); internet or other electronic network activity (how you interact with the game and its ads, diagnostics and crash reports); geolocation data (approximate location derived from your IP address); and, if you email us, your email address and the game details the mail contains (section 3.11). If you join the weekly leagues, we also keep your anonymous league player ID, player code and league points (section 3.15). If you use the leaderboard, Apple or Google also receive your player name, player ID and scores (section 3.8). We don't collect sensitive personal information as defined by California law.

"Selling" and "sharing". We don't sell personal information for money. However, when the game shows personalised ads, Google and its ad partners receive identifiers and activity data, which may count as "selling" or "sharing" personal information for cross-context behavioural advertising under some US state laws (for example, in California). You can opt out:

  • use Privacy options in the game's Settings, if it is shown for your state;
  • on Android, delete your advertising ID or turn off ads personalisation in your device settings;
  • on iOS, don't allow tracking (Settings > Privacy & Security > Tracking).

We don't knowingly sell or share the personal information of consumers under 16.

Your rights. Depending on your state, you have the right to know what personal information we have about you and to get a copy, to correct it, to delete it, to opt out of its sale or sharing and of targeted advertising, and not to be treated differently for using these rights. Email info@blumesoft.co.uk with the subject "US privacy request". You can use an authorised agent; we will ask the agent for proof that you gave them permission. We reply within 45 days. If we turn down your request, you can appeal by replying to our answer with the word "Appeal".

11. Security

The game's only server of our own is the one for the weekly leagues (section 3.15), which runs on Google's Cloud Functions. Only our server functions read and write league data; the game itself can't reach the league database. With its league calls, the game sends Google's App Check proof (Play Integrity on Android, App Attest on iOS), which lets the server tell the genuine game from scripts and modified copies. The Google and Apple software in the game sends data over encrypted connections (TLS). Access to our Firebase, Google Analytics and AdMob accounts is limited to the people who need it. No system is perfectly secure; if a breach affects you, we will tell you and the regulator where the law requires.

12. Changes to this policy

When we change this policy, we update the date at the top. If a change is important, we will tell you in the game or in the app store listing.

13. Contact

Blumesoft Ltd — info@blumesoft.co.uk — Unit Da2 Sutherland House, Sutherland Road, London E17 6BU, United Kingdom.