Privacy Policy — One Left
Last updated: 13 November 2026 · Deutsche Fassung
One Left is a puzzle game for Android. One tap sets off a chain reaction, exactly one dot is left. The game uses your internet connection (Wi-Fi or mobile data) for ads; without a connection you can keep playing, and then no ads are shown. Exactly four things go online, and all four are described separately below: the consent request (Google's check whether your region requires consent) and the ads themselves (ads between levels after completed levels or when you leave a level for the map, a permanent ad banner at the bottom edge of the screen, and three optional reward videos); the ads include the measurement that Google's ad SDK itself carries out once the ads have started (5.3) — not already when you open the app; and the purchases through Google Play — "Remove Ads" and, since version 1.2, tools and tool uses — together with the query for the products and for earlier purchases at Google Play on every start and the logs that Google's library for purchases sends to Google along the way (section 4); and the statistics with Google Analytics for Firebase, only under the same conditions as the ads and without the advertising ID (section 6). For the purchases a program library from Unity is built in; it runs on your device and sends no data to Unity in this app (4.5). Special offers with a personalised price are built into the game but switched off in version 1.2: the app shows none, and even when switched on nothing would go online for choosing them (4.6). I receive usage data only from the statistics, as aggregated numbers and without knowing who you are. This policy tells you what the app stores on your device, what is processed on these paths, who receives it, on what legal basis, and what rights you have.
App: One Left (package name com.northloopgames.oneleft), distributed through Google Play.
1. Controller
The controller within the meaning of Art. 4(7) GDPR is:
- Raphael Esslinger
- Frauenalber Strasse 39
- 76199 Karlsruhe
- Germany
- Email: support.northloopsgame@gmail.com
No data protection officer has been appointed, because the conditions for one are not met: Art. 37 GDPR does not apply (no public authority, no large-scale regular monitoring, no large-scale processing of special categories), and § 38 of the German Federal Data Protection Act does not apply (fewer than 20 people are constantly engaged in automated processing — it is one individual).
2. What the app stores on your device
Everything below stays on your device and, if Android's backup is switched on, in the backup of your Google account (see "Retention" below). Nothing is kept by me: there is no account and no server of mine.
The complete list, as the app keeps it in the saved game (field names in brackets):
- per level (field
levels): stars (stars), best result (best), number of attempts (attempts), failed attempts in a row (failStreak), whether and how often a help was used (helped,hint), the taps needed for the replay of the best result and of the Second spark (bT,bX,bY,b2T,b2X,b2Y: time and position of the tap in the playing field, not a position in the world), the state of the bulb (tipp): whether the hint for that level is already unlocked and whether the bulb has already offered itself there once, and since version 1.2 the tool of the best attempt (bestW), so that the replay shows it correctly - daily board history (field
daily): per daily board the day number (day), the best result (best), the attempts (tries) and the tap of the best result (t,x,y) - the Second spark (field
spark): state, level, tap and attempt identifier (state,level,t,x,y,endTick,attemptId), plus the attempt countersattemptSeqandsparkUsedAttempt - saved-game housekeeping: schema version (
v), a checksum against corruption (sum), the time the saved game was first created (createdMs) and a time anchor (anchorMs) that rises with every save so that an older backup cannot overwrite a newer state - settings: sound (
sound), vibration (vibration) and the fieldstatistik, a leftover without function — it controls nothing; whether anything is measured depends only on consent (section 6) - game markers: which introduction cards have been shown (
hintsSeen,artenGesehen), which island moments have been shown (inselFertigWelt), whether the arrival in a new world has been shown (weltAnkunft, from version 1.1 with the second world), whether the notice screen about ads has been shown (consentShown) and whether the one-time notice about "Remove Ads" has been shown (werbefreiHinweisGezeigt) - the purchase flag (
werbefrei): "yes" once Google Play has confirmed a purchase of "Remove Ads", otherwise "no" (section 4). For "Remove Ads" only this yes or no is stored, no receipt and no purchase token. - the tools (field
wz, since version 1.2): which tools you have bought (gekauft, a yes or no per tool), which tools have already been introduced to you (gesehen), which practice ponds you have completed (probe), how many uses you have per tool (einsatz) and the purchase tokens of the credited purchases of uses (kaufToken, at most the last 64). A purchase token is the identifier Google Play gives a purchase; it contains no payment data. The app keeps it only so that every purchase of uses is credited exactly once (4.2). Whether a tool was given to you or earned by playing is not stored but derived from your stars. - the special offers (field
ang, since version 1.2, 4.6; in version 1.2 the offers are switched off, and the app then keeps only the counting day, the current run of failed attempts and the random number here, the other fields stay empty): the day on which counting was last done (tag), how many offers came today and per level (heute,jeLevelL,jeLevelN) and which packs were shown today (paketeHeute), how often you said "No thanks" in a row (ablehnFolge), the current run of failed attempts in a level (fehlLevel,fehlFolge,fehlAngebote), which offers you have already seen in the current round (verbraucht,offen,saison,saisonAb), a random number drawn once when first needed that shuffles the order of the offers (saat; it does not come from a device identifier), and, for an offer purchase that has been started, which pack it is to bring (offenProdukt,offenCode,offenTag; plus the older fieldskaufOffenProdukt,kaufOffenCode,kaufOffenTag, which only read in old saved games and stay empty afterwards). This information stays on the device and is sent nowhere. - the ad counters:
levelSeitInterstitial,interstitialsHeute,interstitialDatum(the date on your device on which counting is done),interstitialsGesamt,letzterWerbungZeitanker(when an ad between levels was last shown, so that the minimum gap is kept) - the game counters (field
m, thirteen counters):nearMiss(near misses),retryNochmal,retrySpark,retryHint(retries after "Again", Second spark and bulb),attemptsMap,attemptsDaily(attempts on the map and in the daily board),daysPlayed,lastDay(days played),hintNotConfirmed(bulb not confirmed),videoSpark,videoHint,videoTotal(reward videos watched),interstitialFehl(ads between levels that did not appear). These counters stay on the device and are sent nowhere. - the consent answer stored by the UMP SDK (not in the saved game but in the private settings of the Google SDK)
- what Google Analytics for Firebase stores once measuring is allowed (section 6): a random ID of this app installation (app instance ID), whether collection is on, and events until they are sent (not in the saved game but in the private data of the Google SDK)
Locations: the files oneleft-save.json and oneleft-save.bak.json in the app's private folder, plus the private settings of the Google SDKs.
System log: For troubleshooting, the app writes short lines about the course of ads, consent, purchases and (since version 1.2) tool credits and special offers to your device's system log ("logcat"), for example whether an ad between levels was shown, whether Google Play delivered a product with its price, or how many uses of which tool were credited. These lines contain no account, no name, no purchase receipt, no purchase token and no transaction number. The app does not send this log anywhere.
Legal basis: § 25(2) no. 2 TDDDG for the saved game including the purchase flag, the bought tools, the uses and the purchase tokens (storing them is strictly necessary for the game to do what it is for, for a purchased state to be kept and for every paid purchase to be credited exactly once); § 25(1) TDDDG together with Art. 6(1)(a) GDPR for everything the ad SDK and Google Analytics for Firebase store, where consent is required (sections 5.4 and 6.3). For the block of special offers (ang) see 4.6.
§ 25(2) no. 2 TDDDG covers the purchase tokens: you request the purchase yourself, and without the stored purchase token the app cannot credit a paid purchase of uses reliably exactly once (4.2).
Retention: as long as the app is installed. Android's Auto Backup copies the two saved-game files into the user's Google account and restores them on a reinstall; that is a function of the operating system, which the app explicitly switches on for this. With the saved game, the uses, the purchase tokens and the state of the special offers are therefore also in this backup. Uninstalling deletes the data on the device, not this backup (section 10).
3. Google as recipient
The recipients of the data described below are (for purchases from version 1.1, Google Play, section 4):
- Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland (EEA)
- Google LLC, 1600 Amphitheatre Parkway, Mountain View, CA 94043, USA
For the ads, Google is not my processor. For the collection of the data through the SDK built into the app and its transmission to Google, Google and I are joint controllers under the case law of the Court of Justice of the EU (judgment of 29 July 2019, C-40/17, "Fashion ID"); Google covers this in its controller terms (business.safety.google/controllerterms). What Google does with the data afterwards — selecting, delivering and measuring ads — is Google's responsibility as an independent controller. The statistics (section 6) are different: there Google is my processor (6.4). According to Google, Google may pass an ad request in its auction to advertising partners it has approved; where consent is requested, the form lists these providers one by one, and without your agreement nothing goes to them there. What Google does there is set out in Google's own documents:
4. In-app purchases
The purchase path is included from version 1.1 of the app, the first version to appear on Google Play. This section describes it; since version 1.2 there are tools and tool uses besides "Remove Ads".
The products:
- "Remove Ads", €2.99 (price in Germany; in other countries Google Play converts it), non-consumable, bought once and no subscription (section 5.9).
- since version 1.2 tools to keep: single tools and the toolbox with every tool, each non-consumable, bought once and no subscription.
- since version 1.2 packs of uses in the shop (Settings → Tools): a fixed number of uses for a particular tool, consumable. One use is one attempt with the tool; uses do not expire over time.
- special offers (4.6; switched off in version 1.2, the app does not offer them): also packs of uses, consumable, at a price below the shop price. On Google Play these products are called "Sonderangebot: Werkzeug-Einsätze" ("special offer: tool uses"); which tool and how many uses such a purchase brings is fixed by the app before the purchase and shown on the offer.
Google Play shows the prices before every purchase. All purchases are handled by Google Play with the Google Play Billing Library; in the app it is built in through the program library Unity In-App Purchasing (section 4.5). Every purchase is optional; levels and daily boards are available without it (section 9).
4.1 What Google Play processes
When you buy, the app opens Google Play's payment window. There Google processes your Google account, your payment method, the payment, the order with its receipt and any refund. Google acts as an independent controller (addresses and documents in section 3). I have no access to this. Please direct questions about payment, invoice and refund to Google Play.
4.2 What the app receives and what it stores
The app sees no payment data — no card number, no billing address, no name. From Google Play it receives only: the product details (identifier, name, price), the order or purchase token with Google's purchase receipt, the purchase status and the time. The app checks the receipt on your device and reports back to Google Play that the purchase has arrived (the confirmation of the purchase; for consumable products this is also the consuming).
- "Remove Ads" and tools to keep: they are only switched on once Google Play has accepted the confirmation. Some payment methods take longer; the app then shows that the purchase is still being checked. If the confirmation does not come through, the app says so, and Google refunds an unconfirmed payment under its own rules. Only a yes or no per product is stored (section 2), no receipt and no purchase token.
- Uses (shop and special offers): here the order is reversed. The app first credits the uses and saves them permanently on the device, and only then confirms the purchase at Google Play; otherwise a paid purchase would be lost if the app crashed in between. For this it stores the purchase token of the purchase in the saved game (section 2, at most the last 64): if Google Play delivers the same purchase again, the app recognises it by the token and does not credit it a second time. If crediting fails (for example because saving fails or because the pack would raise your uses above the limit of 999 per tool), or if a special offer no longer fits your progress, the app does not confirm the purchase; Google then refunds an unconfirmed payment under its own rules, and the app tells you so.
Google's purchase receipt is not stored. Receipt and purchase token are not sent to me, and the game's code passes them on to no one (on the program library for purchases built into the app, see 4.5). Because the purchase tokens are in the saved game, they go with it into Android's backup of your Google account if that backup is switched on (section 2, "Retention"). The app itself stores about purchases only the purchase flag, the bought tools, the uses, the purchase tokens of the purchases of uses and, for an offer purchase that has been started, the intended pack (4.6), all on your device. The purchase process itself — querying the product, the purchase, its confirmation and the check of earlier purchases — is handled in the app by Google's Google Play Billing Library; it logs its calls together with their success or failure and sends these logs to Google (4.3). Whether they also contain details of individual purchases, I cannot see. In the "Data safety" form on Google Play I therefore declare, as a precaution, that purchase history data is collected and transmitted to Google.
4.3 Check on start and restoring
The non-consumable products ("Remove Ads", the tools to keep and the toolbox) can be restored: an earlier purchase comes back through "Restore purchases" in the settings or by itself. For this the app asks Google Play on every start for all its products with their prices (it needs the prices for the shop; the special offers, 4.6, are switched off in version 1.2) and for the purchases of the Google account on this device, even if you buy nothing and decline the ads; the purchase package may repeat this query when you return to the app. This is also how the app catches up on a purchase whose confirmation did not work the first time, including a purchase of uses that had not been credited yet. The query goes to Google Play, not to me.
Uses are consumable and cannot be restored through Google Play: Google Play does not deliver a confirmed purchase of uses again. After a reinstall your uses only come back if Android's backup restores the saved game (section 2); if two saved games meet there, the higher number per tool counts, never the sum. Without that backup, uses are lost when you uninstall.
The Google Play Billing Library, through which the app talks to Google Play, also sends its own logs to Google on every start: success or failure of its calls and connection problems, together with device details such as manufacturer, model, system version, language, country and mobile network, and the version of the app. According to Google, it uses them to improve the library and to provide better support for errors. This happens even without a purchase and without consent to ads; these logs do not reach me either. Uninstalling deletes the purchase flag and the bought tools only on the device; the non-consumable purchases themselves are kept by Google.
4.4 Legal basis
Art. 6(1)(b) GDPR (performance of the contract of purchase) for the purchase, its confirmation, crediting and restoring it, including storing the purchase tokens, without which a purchase of uses cannot safely be credited exactly once (4.2). For the check on start, which the app runs even without a purchase (4.3), my legitimate interest in providing a paid purchase without any action on your part, also after a reinstall (Art. 6(1)(f) GDPR). § 25(2) no. 2 TDDDG for storing the purchase flag, the bought tools, the uses and the purchase tokens and for accessing Google Play on your device (on the purchase tokens see section 2). This access is strictly necessary even if you have bought nothing: whether a purchase of "Remove Ads" already exists for your Google account, for example from an earlier installation or from another device, the app can only learn through this query, and without it a buyer would first get ads again after a reinstall. The processing at Google Play is Google's responsibility (section 3). For the logs of the Google Play Billing Library (4.3) I rely, in my assessment, on my legitimate interest in offering purchases reliably through the library Google provides for this (Art. 6(1)(f) GDPR), and for the access to your device on § 25(2) no. 2 TDDDG, because purchase and check are only possible through this library and its logs cannot be switched off in the app. What Google does with the logs afterwards is Google's responsibility.
4.5 The program library for purchases
The app builds in the Google Play Billing Library through the program library Unity In-App Purchasing (com.unity.purchasing, version 5.3.1, with the package com.unity.services.core, version 1.14.0) from Unity. The library runs on your device and mediates there between the app and Google Play. For this the app creates no Unity account, does not sign in to Unity and uses no Unity analytics. Unity receives no data from this app. I checked this in two ways. First, the source code of both packages: as this app is built, it contains no path on which data goes to Unity, including Google's purchase receipt, the purchase token or a device identifier. Second, the network traffic: I let the package of version 1.1 built for Google Play run for more than twelve minutes each time, playing it and recording where the app opens connections, once without and once with consent to ads, each time with a second start and with the settings including the purchase row. There was no connection to a Unity server. No Google account was signed in during this measurement, so the connection to Google Play was not established; for everything the library does with an established connection — the query on start and the purchase — the statement rests solely on the review of the source code. Unity's general answers for Google's "Data safety" form for versions before 5.4 name diagnostic data and other performance data of the app; after these two checks, no such data goes from this app to Unity. Should this change with a later version, I will add it to this policy beforehand. Version 1.2 uses the same versions of both packages as version 1.1; the tool purchases run along the same path.
4.6 Special offers with a personalised price
Switched off in version 1.2. In this version the app shows no special offer and offers none for purchase; the rule in the code allows no offer as long as no start day for the offers is entered, and none is entered in version 1.2. On your device the app nevertheless keeps a small count in the field ang: the counting day, the current run of failed attempts in the current level and a random number drawn once (section 2). It does not leave the device and is not used for anything while the offers are off.
If a later update switches the offers on, the following applies; I will change this policy beforehand if any of it changes.
What you will then see: After a level you did not complete, the game may first show a special offer instead of the result card: a pack of uses for a tool that is not yet permanently yours, at a price below the shop price of the same pack. Without any further tap the card says: "Personalised price – chosen automatically from how you play." You can say "No thanks" or buy through Google Play; the shop price continues to apply in the shop at any time. There are no offers in the daily board and none before level 12, at most 2 per level and day and at most 4 per day; after three "No thanks" in a row no further offer comes that day. Offers appear at the earliest 30 days after the packs of uses have been on sale in the shop at the shop price.
How it is chosen: on your device alone, by fixed rules in the app's code. For this the app uses:
- the level you are in and how many failed attempts in a row you had there; also how long you have been in the level since entering it (in seconds, for this visit only; an offer may also come if you stay in a level for a long time);
- the date of your device (to count offers per day);
- which tools have already been introduced to you and which are permanently yours (given, earned or bought; those are no longer offered) — both follow from your stars and purchases —, and how many uses you have (so that no pack goes above the limit);
- whether the purchase path to Google Play is currently open (otherwise there is no offer);
- how much each tool helps on exactly this level: a fixed table built into the app, the same for all players;
- the prices Google Play reports for the products (the offer has to be between 25 and 60 percent below the shop price, otherwise there is none);
- what section 2 lists under "the special offers": which offers you have already seen, how many came today, your "No thanks" in a row and the random number drawn once that shuffles the order.
Not used are: the advertising ID or any other device identifier, an account, your location, data from other apps, your past spending or your purchase history at Google Play, and whether you have bought "Remove Ads". Nothing goes online for the choice: neither to me nor to Google; the statistics (section 6) do not learn whether or which offer you saw or declined.
If you buy: before the purchase the app stores in the saved game which pack the purchase is to bring (section 2). As with every purchase, Google Play sees the product, that is the price tier "Sonderangebot: Werkzeug-Einsätze" with its price, but not which tool and how many uses it contains. If this entry is missing when the purchase arrives, the app credits, by a fixed rule, the pack with this offer price that has the highest shop price; if none fits any more, it does not confirm the purchase, and Google refunds it (4.2). An open entry expires after 14 days.
Automated decision: the app chooses tool, amount and price automatically from how you play. An offer commits you to nothing, and every pack is available at any time at the shop price in the shop.
Legal basis when the offers are switched on: my legitimate interest in offering you a cheaper pack at a suitable moment (Art. 6(1)(f) GDPR). The choice runs only on your device, none of it reaches me or Google, and an offer commits you to nothing: it has no legal effect and does not similarly significantly affect you, so it is not a decision within the meaning of Art. 22 GDPR. You can object to this processing at any time by email (sections 11 and 15). The app has no switch for this, and because I do not know your device, I can only change the offers for everyone with an update. For storing the count in the saved game on your device I rely, as for the rest of the saved game, on § 25(2) no. 2 TDDDG.
5. Ads
5.1 The five ad placements, one by one
- Ads between levels (interstitial, a full-screen ad): from level 6, only for levels on the island map, never in the daily board. They appear on two occasions only: after a completed level, and when you leave a level for the map after having failed at least 3 attempts in it. At least 5 minutes lie between two such ads. As a pure safeguard against errors there is an upper limit of 60 ads between levels per day, which normal play does not reach. Each comes with 3 seconds of advance warning. Never in the middle of a level, never on "Again", and never between two attempts.
- Ad banner in its own strip at the bottom edge of the screen: from level 6 (on the map, once level 6 is completed) permanently, while you play a level on the island map or look at the map — this includes while you tap the field. It sits in its strip below the playing field, never over the playing field and never over a tap area. Never in the daily board, and not during the advance warning, an ad between levels or a video, in the settings, or at the consent request.
- Reward video "Second spark": optional, only if you tap it.
- Reward video "Aim help": optional, only if you tap it.
- Reward video "Bulb" (hint with a video): optional, from level 4. The video only starts if you tap the bulb at the top right and confirm "Watch video" in the window. After 8 failed attempts in a row in a level, the game points to the bulb once per level with a short notice; that never starts a video by itself.
5.2 The SDK
Ads are delivered by the Google Mobile Ads SDK (AdMob), built in as com.google.ads.mobile 11.5.0 (containing the Android SDK play-services-ads 25.4.0). The consent request is presented by the Google User Messaging Platform (UMP, version 4.0.0), which is part of the same package.
5.3 What Google processes when delivering an ad
- your device's advertising ID (Werbe-ID)
- the app set ID: an identifier that Google Play services assign on your device to the apps of one developer; Google names it next to the advertising ID in its disclosure for the ad SDK. It cannot be reset in the Android settings, and deleting the advertising ID does not affect it.
- your IP address (truncated or not, according to Google's own statements)
- device and app details (model, operating system version, language, app version)
- an approximate location that Google estimates from the IP address — this is not a location permission; the game never reads your location
- your interaction with the ad (seen, tapped, dismissed)
- the ad SDK's own measurement, once the ads have started: app launches, taps and video views, plus diagnostic data on the performance of the app and the SDK (such as launch time, hang rate, energy use). With it, Google measures how the ads perform and, according to Google, uses the data for advertising, analytics and fraud prevention.
When this measurement begins: not when you open the app. The app sets the entry com.google.android.gms.ads.DELAY_APP_MEASUREMENT_INIT to true in its manifest; the ad SDK then only starts to measure when the app starts the ads (MobileAds.Initialize, 5.4). Where consent is required and you do not give it, the ads never start, and neither does this measurement.
5.4 Consent first, where it is required
Until then the app calls neither ads nor the consent request. After you complete level 3 the app shows, once per saved game and in every region, a notice screen about ads with a "Continue" button; it is not a consent. With this screen the app asks Google's consent request (UMP) whether your region requires consent. Google decides that by your location; according to Google it concerns the European Economic Area, the United Kingdom and Switzerland. After that the app checks again on every start whether this has changed (from version 1.1 no longer after the purchase "Remove Ads", 5.9).
The consent request itself transmits, in every region and also where no form follows, your IP address and device and app details (such as language and app identifier) to Google, and the UMP SDK stores its answer on your device (section 2). Legal basis: where consent is required, I must obtain it and be able to demonstrate it (Art. 6(1)(c) in conjunction with Art. 7(1) GDPR); otherwise my legitimate interest in starting ads without consent only where that is permitted (Art. 6(1)(f) GDPR). The access to your device that this request needs is covered by § 25(2) no. 2 TDDDG.
Where consent is required, Google shows a form. The app starts ads only if you have agreed there to the purpose "Store and/or access information on a device" (purpose 1 of the European TCF standard). Without your consent MobileAds.Initialize is never called, no request goes out to the ads, the ad SDK's measurement (5.3) does not start, and the game stays playable: saying no locks no level and no daily board. The three helps with a reward video are then not offered (section 9). If the app cannot read your answer, it prefers to show no ads.
In all other regions the app shows no consent request and no form: ads start there as soon as Google's check has found that ads may be requested. That is expressly not a consent given by you. Where the GDPR applies there too, I base the ads on my legitimate interest in financing the game without charge through advertising (Art. 6(1)(f) GDPR); you can object to this at any time (box "Right to object" in section 11). You can reset or delete the advertising ID in the Android settings (section 10). On age see section 13.
5.5 Withdrawal
Where a consent is requested, you can withdraw at any time through Settings → Privacy → "Change consent" (Art. 7(3) sentence 4 GDPR: withdrawing must be as easy as giving). Ads already loaded are then discarded, a banner that is in place is removed, and nothing new is requested.
5.6 Profiling
Where consent is required, whether Google delivers personalised ads depends solely on it. If you decline there, no ad is requested at all. Where consent is not required, delivery follows Google's rules for that region; I have no influence on that.
Automated decision-making: I make no automated decision within the meaning of Art. 22 GDPR, and no profiling with legal effect on you. Google selects the ads automatically; to my knowledge this has no legal effect on you and does not similarly significantly affect you.
5.7 Maximum ad content rating
The maximum ad content rating is set to G — suitable for all ages.
5.8 Transfer to the USA
Google LLC is based in the USA. The transfer rests on the EU-US Data Privacy Framework, for which the European Commission issued an adequacy decision on 10 July 2023; Google LLC is certified under it.
5.9 What the purchase changes
The purchase "Remove Ads" (from version 1.1, section 4) ends the ads between levels and the ad banner for good; afterwards no ad is requested for either. The three helps with a reward video (Second spark, Aim help, Bulb) are then available without a video. From the next start after the purchase the app calls neither the consent request (5.4) nor the ad SDK: the consent request no longer goes to Google, the ads no longer start, and so the ad SDK's measurement (5.3) no longer takes place either. The statistics (section 6) stop measuring too: the app switches their collection off on every start and only switches it on again with an answer from the consent request, and after the purchase there is none. For anyone who has not bought "Remove Ads", section 5 applies unchanged.
6. Statistics (usage analysis)
The app contains Google Analytics for Firebase (Firebase Unity SDK 13.17.0, only the App and Analytics modules; no Crashlytics, no remote configuration, no notifications). It tells me how the game is played and whether it pays for itself — not who plays it. What you do in the game — every level, every attempt, every star — still stays on your device (section 2); only the five events below go out. This is separate from the ad SDK's measurement (5.3), which is part of the ads and goes to Google, not to me.
6.1 What is measured
- sessions: when the app comes to the foreground and when it leaves it again, with the duration in seconds. An ad or the Google Play purchase window does not end a session.
- milestones: completing levels 5, 10, 25, 50, 100 and 250 for the first time — once per level, with the level number.
- the purchase "Remove Ads": whether it succeeds ("purchase" or "restored") or a purchase attempt that was started fails, with a reason from a fixed list (cancelled, already owned, store not reachable, payment declined, pending, not acknowledged, saving, unknown, other) — never Google's error message; no payment details, no receipt, no purchase token.
- the revenue of an ad shown, as AdMob reports it: value, currency, precision of the figure and the format (video, ad between levels, banner).
- what the SDK collects itself: the app instance ID (a random ID of this installation, not a device ID), your IP address, from which Google derives country and region, device and app details (model, operating system version, language, app version) and the SDK's automatic events (first open, session start, engagement time, app update). According to Google the SDK also records purchases through Google Play itself (in-app purchase with product and price); since version 1.2 this also applies to tools and uses, for a special offer with the price tier as the product. The app sends an event of its own only for "Remove Ads", not for tool purchases and not for special offers.
Not collected are the advertising ID and the Android ID: the app switches both off in its manifest (google_analytics_adid_collection_enabled and google_analytics_ssaid_collection_enabled set to false), and in the SDK's consent mode ad storage, ad user data and personalisation are always set to "denied". The statistics are not used for advertising, not linked to the ad SDK and not combined with other data about you.
6.2 When measuring happens
Exactly when the ads may start too, and not earlier. Collection is switched off in the app's manifest (firebase_analytics_collection_enabled = false) — also for the automatic events on first open that the SDK would otherwise write before any of the app's code runs. The app switches it off again on every start and only on once the consent request (5.4) is complete and, where consent is required, you have agreed to purposes 1, 8 and 10 of the TCF standard (store and/or access information on a device; measure content performance; develop and improve services). If you decline there, you are not measured. In all other regions measuring starts like the ads without a consent request (5.4). After the purchase "Remove Ads" it ends (5.9). Measurement runs of the developer tools send nothing.
6.3 Legal basis, withdrawal, objection
Where consent is required: your consent (Art. 6(1)(a) GDPR; for access to your device § 25(1) TDDDG). You can withdraw it at any time via Settings → Privacy → "Change consent"; the app then switches collection off at once and deletes the analytics data on the device, including the app instance ID. In all other regions: my legitimate interest in improving the game and understanding whether the ads pay for it (Art. 6(1)(f) GDPR); your right to object is in section 11.
6.4 Recipient, retention, transfer
Google (section 3) processes the statistics as my processor under the data processing terms for Firebase and Google Analytics (Art. 28 GDPR); the settings that would let Google use analytics data for its own purposes are switched off. Google Analytics keeps the events for 2 months and then deletes them. I only see aggregated numbers in the Firebase console, no names and no advertising ID. For the transfer to the USA, 5.8 applies.
7. Permissions of the app
The shipped package declares the following permissions. Four belong to the game itself, six are brought in by the ad SDK, and one (com.android.vending.BILLING) belongs to the purchase path (section 4).
| Permission | What for |
|---|---|
android.permission.INTERNET | fetching the ads and the consent request |
android.permission.ACCESS_NETWORK_STATE | the ad SDK checks whether a connection exists |
com.google.android.gms.permission.AD_ID | the device's advertising ID for AdMob |
android.permission.VIBRATE | a short vibration on hits; no data is processed for it |
android.permission.ACCESS_ADSERVICES_AD_ID | one of Android's Privacy Sandbox interfaces that the Google Mobile Ads SDK brings in |
android.permission.ACCESS_ADSERVICES_ATTRIBUTION | one of Android's Privacy Sandbox interfaces that the Google Mobile Ads SDK brings in |
android.permission.ACCESS_ADSERVICES_TOPICS | one of Android's Privacy Sandbox interfaces that the Google Mobile Ads SDK brings in |
android.permission.FOREGROUND_SERVICE | brought in by the helper library androidx.work, which the ad SDK uses. My own code starts no foreground service. |
android.permission.WAKE_LOCK | brought in by play-services-measurement-sdk-api, which the ad SDK uses. My own code uses no wake lock. The screen staying on while you play is done by the app's window, not by this permission. |
com.northloopgames.oneleft.DYNAMIC_RECEIVER_NOT_EXPORTED_PERMISSION | a purely app-internal protection marker at signature level, brought in by the helper library androidx.core. It grants no access to your device and is unreachable for other apps. |
com.android.vending.BILLING | handling the purchases through Google Play: "Remove Ads", tools and uses (section 4) |
The app does not access contacts, location, camera, microphone, calendar, or files outside its own storage. There are no notifications.
8. What the app does not do
- no account, no sign-in, no registration
- no server of mine
- no leaderboard, no chat, no content sharing
- no location access, no contacts, no camera, no microphone
- no notifications
- no further usage statistics: no Crashlytics, no Unity Analytics, no Adjust, no AppsFlyer; Google Analytics for Firebase only as section 6 describes it, without the advertising ID; the ad SDK's measurement (5.3) goes to Google, not to me
- no payment data: Google Play handles every purchase, and the app sees no payment data (section 4)
- no analysis of how you play outside the device for offers: the app chooses special offers on the device alone (4.6)
- no sharing with third parties other than Google and, through Google's auction, the advertising partners approved by Google, to the extent described in section 3; on the program library for purchases from version 1.1, see 4.5
9. Do you have to provide data?
No — neither by law nor by contract. All levels and every daily board are reachable without money, even if you give no consent to ads. Outside the EEA, the United Kingdom and Switzerland the ads are, however, part of the app: they start there without a request, and if you do not want them you can object (section 11) or not use the app. "Again" is always instant and free. The one exception are the three helps (Second spark, Aim help, Bulb): they come through an optional reward video or, from version 1.1, with the purchase "Remove Ads". Where consent is required (5.4) and you do not give it, no ad is requested; the three helps are then only available with "Remove Ads", otherwise you play without them. The purchase "Remove Ads" is optional and unlocks no levels. The same applies since version 1.2 to tools and uses: every level can be solved without a tool, and you also get every tool without money, as a gift or for good from a certain level on.
10. Deletion
- Uninstalling deletes all of the app's data on the device. Android's backup remains and restores the saved game on a reinstall until you remove it (next point).
- The advertising ID can be reset or deleted in the Android settings under "Privacy → Ads". The app set ID (5.3) cannot be deleted there.
- A purchase (from version 1.1) is kept by Google Play and survives uninstalling; "Remove Ads" and bought tools can be restored (4.3). Uses cannot: they live only in the saved game and after uninstalling only come back through Android's backup. Access and deletion for purchase data are provided by Google (section 11).
- Google Analytics deletes the statistics (section 6) after 2 months. The app instance ID on the device disappears when you uninstall and, where you were asked, when you withdraw consent (6.3).
- Android's Auto Backup can be removed under "Google → Backup".
- There is no account that could be deleted — none exists.
11. Your rights
You have the right of access (Art. 15 GDPR), rectification (Art. 16), erasure (Art. 17), restriction of processing (Art. 18), data portability (Art. 20), objection (Art. 21), and withdrawal of consent (Art. 7(3)).
Right to object (Art. 21 GDPR)
Where I base the ads on my legitimate interest (Art. 6(1)(f) GDPR, that is outside the EEA, the United Kingdom and Switzerland, 5.4), you can object at any time on grounds relating to your particular situation; to ads as direct marketing also without giving grounds. The same applies to the consent request insofar as it rests on point (f), from version 1.1 to the check of purchases on start (4.4), and to the statistics where they run without a consent request (6.3).
How: an informal email to support.northloopsgame@gmail.com. There is no switch for this in the app. Two ways take effect immediately and by yourself: delete the advertising ID in the Android settings ("Privacy → Ads"; it is then no longer sent, but the app set ID from 5.3 still is) or uninstall the app (then nothing more goes to Google).
What happens then: because the app knows no account and no identifier of yours, I cannot switch off the ads on your device remotely. I will reply to you and point to the two ways above; there is no other way that costs nothing. The purchase "Remove Ads" (from version 1.1, 5.9) also ends the ads, but it is a paid purchase and not a way to exercise your right to object: nobody has to buy anything in order to object.
The check of purchases on start (from version 1.1, 4.3 and 4.4) runs between the app and Google Play, together with the logs of the Google Play Billing Library to Google (4.3); nothing reaches me, and there is no switch in the app that turns this off. Following your objection I will examine whether grounds for the check and these logs override your interests, and reply to you. The only way that takes effect immediately by yourself is uninstalling the app.
For the data that arises at Google, including purchases through Google Play, Google is the body that has to answer: I have no access to it and can neither hand it over nor delete it. Please use the pages named in section 3 for that.
12. Right to lodge a complaint
You may lodge a complaint with a data protection supervisory authority. The competent one is:
- Der Landesbeauftragte für den Datenschutz und die Informationsfreiheit Baden-Württemberg
- Lautenschlagerstrasse 20
- 70173 Stuttgart, Germany
13. Children
The app is directed at people aged 16 and over; the target audience in Google Play is set to 16+. It is not directed at children and teenagers under 16. Ad content is capped at G (see 5.7).
Why 16: Where ads need your consent (5.4), consent is the only legal basis for the advertising ID and the ads. Under Art. 8(1) GDPR a consent is valid in Germany without more only from the age of 16; for younger people it needs the consent of the holders of parental responsibility (other EU states set the limit lower, down to 13). The game has no age check and cannot verify age, and it passes no age information to Google. If you are not yet 16, please decline the consent unless your parents or guardians have agreed; levels and daily boards then remain playable (section 9). Parents or guardians who believe that a child under 16 has transmitted data can write to me at the address in section 15.
14. Changes
This version is dated 13 November 2026 and applies to version 1.2 of the app (with tools and uses, section 4; the special offers are switched off, 4.6); the purchase path exists from version 1.1, the first version on Google Play. Changes are published on this page; the version in force is the one available here.
15. Contact
Questions about privacy: support.northloopsgame@gmail.com