OverLit Privacy Policy

Version: 3.1.1
Last updated: 2026-08-31

This Privacy Policy covers every version of OverLit. Some features described here may not be present in your version of the app, may not yet be switched on for you, or may describe functionality that has not been released yet; where a feature is not available to you, the sections describing it do not apply to you until it is. Accepting this Privacy Policy does not put anything into effect that the app does not actually do. Where a later version of this Privacy Policy conflicts with an earlier one, the later version governs from its date onward — it does not change how information was handled before then. Previous versions of this document remain publicly available in its revision history.

This Privacy Policy explains what OverLit does with information when you play the OverLit app on iPhone or Android, visit the OverLit pages on alekjaltuszyk.xyz, contact support, or see ads shown in or for OverLit.

OverLit is a short-session arcade game. There is no sign-up, no username and no password, and the app never asks you for a name, an email address or a phone number. There is no text field anywhere in the app, so there is nothing you can type into it. Most of what OverLit knows about your play — your scores, your progress, your unlocks, your settings — stays on your phone.

Three things can send information off your phone: ads, analytics, and online leaderboards. Section 3 lists exactly which of them exist on which platform, because they are not the same on both, and every section after it says which platforms it applies to. Each is described below, including the parts that are less flattering.

1. Who Is Responsible For OverLit

OverLit is provided by Alek Jałtuszyk, legally Aleksander Jałtuszyk, an individual sole trader established in Poland. For data protection law, that person is the controller of the personal data described in this policy.

Contact:

• Email: alekgameshelp2@gmail.com
• Telephone: +48 73 2099027
• Mailing address: Aleksander Jałtuszyk, Skrytka Pocztowa 59, UP Warszawa 93, 02-800, Warszawa, Poland
• Support page: https://alekjaltuszyk.xyz/apps/OverLit/support/
• Privacy Policy: https://alekjaltuszyk.xyz/apps/OverLit/privacy-policy/
• Terms of Use: https://alekjaltuszyk.xyz/apps/OverLit/terms-of-use/
• Legal manifest: https://alekjaltuszyk.xyz/apps/OverLit/legal-manifest.json

No Data Protection Officer has been appointed, and none is required: this is a one-person business with no large-scale monitoring and no processing of special categories of data. No EU representative is required either, because the controller is established inside the EU.

This policy covers the OverLit app on both platforms and the OverLit pages on alekjaltuszyk.xyz.

2. Quick Summary

• There is no OverLit account, no sign-in, no password, and no name, email address or phone number is ever requested by the app.
• Your scores, level progress, theme unlocks, settings, play counters, age answer and purchase state are stored on your device.
• Online leaderboards, where enabled, send a score and a small set of technical fields to a server run by the developer on Google Cloud in Belgium, under an anonymous identifier. Your board nickname is picked at random by the server from a fixed list of words written by the developer. You can ask for a different one at any time, but you cannot type your own, and nobody can put their own text on a board.
• You can turn publication off and keep playing: Settings → Legal → Post my scores to leaderboards. For players who told the app they are 13 to 17 it is off unless they turn it on.
• OverLit shows Google AdMob ads in the free version on both iPhone and Android — a banner above the board while you play, interstitials between runs, and opt-in rewarded ads. Google’s advertising SDK processes ad-request and ad-interaction data, and your IP address, which can be used to estimate a coarse location. Section 6 has the detail; section 3 lists which components each platform carries.
• On iPhone, if you told the app you are 18 or older, OverLit shows Apple’s App Tracking Transparency prompt. If you allow tracking there, Google’s advertising SDK may read your device’s advertising identifier and use it to personalise ads and measure them across other companies’ apps. If you say no, or never answer, the identifier is not available and is not used. Players in the 13 to 17 band are never shown the prompt.
• Because the free game is paid for by advertising, OverLit advertises itself. To know which of those adverts actually work, the app sends the same 16 milestone events to one measurement partner, Tenjin, which reports them back to the ad platforms the developer buys from — currently Meta (Facebook and Instagram), TikTok and Google. It receives no score, no nickname, no age answer and nothing you typed, because there is nothing in OverLit to type. A player treated as 13 to 17 is not measured this way at all: the partner’s software is never started for them. No Meta or TikTok software runs inside OverLit; only the partner’s does.
• Analytics is limited to 16 one-time milestone events — things like “finished onboarding” and “completed level 10” — plus one repeatable event that counts each run you start, labelled only with which of seven game modes it was. They carry no identifier you would recognise, no score, no age answer and no message content. A player who declares 13 to 17 sends none of them. For a player who declares 18 or older, analytics starts only after Google’s privacy message has run, on both platforms. Accepting these documents is not analytics consent.
• The app asks you to pick an age range, 13 to 17 or 18 or older. That answer stays on your device and is never transmitted. It changes how ads and analytics are configured, and whether your scores are published by default.
• In India and South Korea every player is given the 13-to-17 treatment, whichever age they picked, because those countries set the age of a child above OverLit’s minimum of 13. Section 14 explains.
• There is one optional purchase, Full Version. It is handled by Apple or Google Play, it removes ads, and no payment-card details ever reach the developer.
• Nothing is sold to data brokers. Some privacy laws nonetheless treat personalised advertising as “sharing” or “targeted advertising” — section 12 explains how to turn that off.
• There is no chat, no social feed, no friend list, no multiplayer, no cloud save, no camera or photo access, no microphone access and no precise location.

3. What OverLit Is Built From

Everything that can send data off your phone is a third-party component, so the honest way to describe OverLit’s privacy is to list those components. The two platforms are not the same, and this table is the single place that difference is recorded. Every later section says which platforms it applies to; where a section names a component this table marks “no”, that section does not apply to you.

Both apps now carry the same advertising and consent components. Section 6 applies to both. The differences that remain in the table above are Apple’s and Google’s own technologies rather than choices about you: App Tracking Transparency, the Apple advertising identifier and SKAdNetwork exist only on iPhone, and the Google advertising ID only on Android. The two stores also each have their own purchase component.

There is exactly one attribution partner, and it is not Meta or TikTok. OverLit advertises itself on Meta and TikTok, but no Meta or TikTok software runs inside the app. Both platforms instead carry a single measurement partner, Tenjin, which is what reports back to them. That is a deliberate choice and not merely a tidy one: Apple allows only one component in an app to own the SKAdNetwork conversion value described in section 6, so integrating each ad platform separately would mean one of them measuring properly and the rest not. One partner also means one set of software reading your device, instead of three.

Not present on either platform: Firebase Crashlytics, Performance Monitoring, Remote Config or Cloud Messaging; any third-party crash-reporting or product-analytics tool; any Meta or TikTok SDK or pixel; any conversion API sending events from the developer’s own servers; any mediation partner; or any customer-list, contact-list or email upload to an advertising platform.

4. What Stays Only On Your Device

The following is stored in your phone’s app storage and is not transmitted to the developer, except that an eligible personal-best score and the technical submission fields listed in section 5 can be sent to the leaderboard service:

• your local high-score records, level progress, stars, campaign and arcade state, and local run history
• theme unlocks, menu position, and gameplay preferences such as haptics and accessibility settings
• whether you have chosen to publish scores to leaderboards
• play counters, ad-pressure counters, ad-attempt records and timing values that decide when an ad or an unlock offer may appear
• your Full Version entitlement state, plus the store transaction identifiers needed to recognise a restored purchase
• which version of the legal documents you accepted, and when
• your age-band answer
• a record of which of the 16 one-time analytics milestone events have already been sent, so that none is ever sent twice. The repeatable run-start event described in section 7 is deliberately not recorded here, because it is meant to repeat

Deleting the app removes this local data from the device, subject to the platform’s normal backup and restore behaviour.

OverLit includes a Copy Progress option that copies a plain-text summary of your local progress to the clipboard. Copying it sends it nowhere. It only leaves your device if you choose to paste it somewhere, such as into a support email.

There is no cloud save. OverLit does not use iCloud, Game Center, Google Play Games, or any progress-sync service. A leaderboard entry is a published score, not a backup: if you delete the app, your progress is gone even if your score is still on a board.

5. Online Leaderboards

Applies to both platforms.

Leaderboards are not switched on in every version of the app, and where the feature is switched on, a board becomes available to you only after you complete campaign Level 5. Until both of those are true, no leaderboard data leaves your device and none of what follows happens.

Choosing not to be published

Settings → Legal → Post my scores to leaderboards turns publication off while you keep playing. With it off, nothing about a run leaves your device; you can still open a board and see where everybody else stands.

For a player who chose the 13 to 17 band the switch starts off, and stays off until they turn it on. For a player who chose 18 or older it starts on. That difference is deliberate: several regulators expect a service not to make a child public by default.

Turning it off does not retract what is already published. Section 15 is how you remove that.

The anonymous identity

The first time the app needs to talk to the leaderboard service, it creates an anonymous account with Firebase Authentication. This is not an account in any normal sense: it has no email address, no password, no phone number and no profile, and there is nothing to sign in or out of. It is a random identifier issued by Google.

Because that identifier lets the same installation be recognised again, and lets scores be attached to it, it is treated as personal data under the GDPR. This policy does not claim that leaderboards collect no personal data, because that would not be true.

The identifier is stored in the platform’s own protected storage — the Keychain on iPhone, the equivalent on Android — which is deliberately durable, so it can survive deleting and reinstalling the app.

Your board nickname

The server gives you a nickname made of one to three words drawn at random from fixed lists written by the developer — for example Grumpy Kraken or Cosmic Comet Otter. Two players can end up with the same one.

The nickname is not derived from your identifier, and reveals nothing about it.

Next to your nickname there is a dice button. Pressing it asks the server for a different random name, as often as you like. You are choosing between names the developer wrote; you are not writing one. OverLit contains no text-entry field of any kind, anywhere in the app, and no part of the leaderboard service will accept a nickname sent by an app. There is therefore no way for anyone to put a real name, an insult, a phone number or an advertisement onto a board. That is a deliberate design choice and it removes an entire class of problem.

Your current nickname is stored against your anonymous identifier and is shown next to your score on every board you appear on. In that sense it is a stable pseudonym attached to a persistent identifier, and it is treated as personal data for the same reason the identifier is.

What is sent when a score is submitted

A submission carries exactly these fields, and nothing else:

• a board identifier, which describes what was played: whether it was campaign, arcade, daily or legacy, the level or challenge, the grid size, the ruleset, whether the board ranks by score or by time, and the scoring version
• the week identifier, for weekly boards, in ISO form such as 2026-W30
• the score — a whole number, either points or a duration in hundredths of a second — and whether higher or lower is better on that board
• a de-duplication key built from the run, so that a retry after a dropped connection cannot create a second entry
• the fixed word STANDARD, marking an ordinary run
• the platform (IOS or ANDROID), the app version, and the content version

That list is complete. No name, no age band, no advertising identifier, no device identifier, no location, no email address and no free text is ever sent to the leaderboard service.

Rolling a new nickname is a separate request. It carries no data at all beyond what every call needs — the anonymous identifier and the app-attestation token — because the app has nothing to send: the server picks the words.

Submission happens automatically at the end of a qualifying run, and only when the score actually beats your own previous accepted best. When leaderboards first become available after campaign Level 5, OverLit also checks the eligible personal bests already stored on your device and queues any that are not already pending or recorded as accepted. The same check can run when importing genuine played progress first makes leaderboards available, and it can be started manually from development builds. This backfill sends one best per eligible board using exactly the same fields and ordinary eligibility rules as a live run; it does not upload your progress file or run history. Nothing is submitted while publication is switched off, and tutorial runs, your first onboarding run, abandoned runs, runs played with Developer Mode enabled, skipped levels, records created by developer tools and scores from an obsolete scoring version are never submitted.

What is stored on the server

Against your anonymous identifier:

• a private player record holding your current nickname, the time it last changed, and per-identity rate counters used to stop automated flooding
• one board entry per board, holding the score, the server time at which that score was first accepted (earliest submission wins a tie), a copy of your nickname, the platform, the STANDARD marker and the identifier itself. Rolling a new nickname updates that copy on every board you are already on
• a de-duplication ledger of recent submissions, so a replayed request returns the original answer instead of creating a duplicate. Each ledger record expires automatically 30 days after it is written. A record also holds a copy of the board rows that were returned to you at the time, which means it can contain other players’ nicknames and scores as they stood then — the same information that was on your screen
• a rating record, holding a percentile-based score derived from your best placements. One is written for every player who submits, whether or not the overall board is showing them

Per board, not per person, the server keeps the board’s registry entry and its size.

What other players see

A board page shows at most ten rows. Each row is a rank, a nickname and a score — your own row is shown as You. If you are outside the top ten, the page shows the top seven plus the rows immediately above and below you, so you can see where you stand. Ranks are calculated on the server; the app never computes them.

The stored platform value is not displayed, and the underlying identifier never leaves the server at all. No timestamps, no progress, no purchase state and nothing else about another player is ever shown to you, or about you to them.

Where it runs, and what protects it

The server code and the database run in Google Cloud’s europe-west1 region in Belgium. The app cannot read or write the database directly: every operation goes through a small set of server functions, and the database rules deny all direct access.

Each request is protected by Firebase App Check, using Apple’s App Attest on iPhone and Google’s Play Integrity on Android, to confirm that the request is coming from a genuine, unmodified copy of OverLit. That check produces a short-lived token. It tells the developer nothing about you.

The whole feature can be switched off remotely, for everyone, without an app update.

The honest caveats

• A leaderboard entry is published. Its nickname and score are visible to any other player who reaches that board.
• Board entries have no automatic expiry. When a board’s scoring rules change the board is archived rather than deleted, and archived boards stay readable indefinitely. An entry stays until you ask for it to be erased. Section 15 explains how.
• Because a leaderboard identity is anonymous, there is no name or email address attached to it. That is good for your privacy and awkward for your rights — see section 15 and section 17.
• The copies of board rows held in other players’ de-duplication ledgers expire on their own within 30 days, but erasing your data does not reach into them. They are never shown on a board or to a new viewer; they are a cached response, and the only way one resurfaces is if that player’s own app repeats the identical submission.

6. Advertising

Applies to both platforms.

The free version of OverLit is paid for by ads, served through Google’s Mobile Ads SDK from Google AdMob. There are three kinds:

• rewarded ads, which you choose to watch in exchange for a cosmetic unlock, a level skip, or a new leaderboard name
• interstitial ads, full-screen, shown only at breaks outside active play — returning to a menu, replaying, advancing a level, or rolling a new leaderboard name
• a banner, a strip shown above the board while you play

The banner is the one ad that is on screen during a run. It sits in the empty space above the grid; it is never placed on the grid itself, it does not move or shrink the board, and it does not take taps meant for a cell. Where a device leaves no room above the board, no banner is shown at all. No full-screen ad ever interrupts a run in progress.

What Google receives

Google and its advertising partners may process, under their own policies:

• your IP address, which can be used to estimate a coarse or general location
• device and app information, and SDK-level signals used to request and render an ad
• advertising data: which ads were requested and shown, impressions, clicks, rewarded-ad completions and similar events
• product interaction data: app launches, taps, ad views and interactions with the privacy messages described in section 12
• crash, diagnostic and performance data from the advertising SDK
• attribution signals, including SKAdNetwork postbacks handled by Apple
• your consent and privacy choices, so that they can be honoured

Google uses this to select and deliver ads, measure them, cap how often you see them, detect fraud and invalid traffic, and to run the ad auction. Google’s own descriptions are in the Google Privacy Policy and in Google’s advertising technologies information.

App Tracking Transparency and the advertising identifier

Apple requires your permission before an app may link what it learns about you with data from other companies’ apps and websites for advertising. That permission is asked through the App Tracking Transparency prompt.

Adults. If you chose the 18 or older band, OverLit shows that prompt once the legal documents have been accepted and the app is on screen. If you choose Allow, Google’s advertising SDK may read your device’s advertising identifier and use it to personalise the ads you see and to measure them across other apps and websites. If you choose Ask App Not to Track, or dismiss the prompt without answering, iOS does not make the identifier available and it is not used. You can change this at any time in iOS Settings → Privacy & Security → Tracking; the change takes effect without reinstalling.

Minors. If you chose the 13 to 17 band — or you are in a country listed in section 14 — OverLit never shows the prompt and never reads the advertising identifier. Cross-app tracking is not asked for and is not performed. This is deliberate: several laws restrict targeted advertising to people a service knows to be minors, and OverLit knows, because it asked.

Refusing costs you nothing but relevance. Ads still appear either way — they are what pays for the free game. What changes is whether they are chosen using an identifier that follows you between apps. The only way to remove ads entirely is the Full Version purchase.

How your age answer changes the ads

For players treated as minors, the advertising SDK is configured with teen treatment, a maximum ad content rating of Teen, publisher ad personalisation disabled, and Google’s publisher first-party identifier disabled. In plain terms, they get non-personalised ads.

Non-personalised is not the same as identifier-free, and it would be misleading to imply otherwise. Google’s own documentation is explicit that non-personalised ads still use cookies or mobile advertising identifiers for frequency capping and aggregated ad reporting, and that consent is still required for that where the law says so. What non-personalised removes is the targeting, not every identifier.

For players treated as adults, ad personalisation and Google’s publisher first-party identifier may be enabled, subject to your consent choices, your device settings, Google’s own settings and applicable law. The publisher first-party identifier is a Google-managed identifier scoped to this publisher; it is not the device advertising identifier and is not shared as one with other publishers.

Install measurement, and the adverts OverLit buys

Applies to both platforms.

The free game is paid for by advertising, so OverLit advertises itself — on Meta (Facebook and Instagram), on TikTok, and through Google. Buying adverts is only worth doing if it is possible to tell which of them brought players who actually play, and that is what this part is for.

One partner, named. OverLit carries a single attribution component, the Tenjin SDK (Tenjin Inc., United States). No Meta or TikTok software runs inside the app. Tenjin measures which advert an install came from and reports the milestones in section 7 onward to whichever ad platforms the developer is buying from.

What Tenjin receives, when it runs at all:

• the event names listed in section 7 — nothing else about a run, and none of the parameters those events carry to Google Analytics;
• your device advertising identifier, but only where it is available: on iPhone that means only if you allowed tracking through Apple’s prompt, and on Android it is the resettable Google advertising ID;
• your IP address, which can be used to estimate a coarse location, and ordinary device, app-version and session information;
• on Android, the Google Play Install Referrer — the string Google Play hands an app to say which listing or advert it was installed from;
• on iPhone, a copy of the SKAdNetwork postback described below.

It does not receive your score, your rank, your board nickname, your leaderboard identity, your age answer, your purchase card details, or anything you typed — there is nothing in OverLit to type.

Nothing runs for a player treated as a minor. For the 13-to-17 band, and for everyone in the countries in section 14, the Tenjin SDK is not started at all. This is deliberately stronger than switching it off: an attribution SDK exists to measure across apps, so for a player who should not be measured across apps the honest state is that it never runs.

Consent still governs it for everyone else. Where Google’s privacy message applies, the SDK is not started until that message reports that advertising may proceed, in exactly the way section 7 describes for analytics.

If you decline Apple’s tracking prompt, measurement continues without the identifier. No advertising identifier is available, so events are sent without one and are flagged to the ad platforms as opted out of personalisation. What remains is aggregate: Apple’s SKAdNetwork, described next, plus counts. This is worth stating plainly rather than implying that declining stops all measurement, because it does not — what it stops is measurement that can follow you between apps.

SKAdNetwork, and the one number OverLit sets. The iPhone app declares the standard Google-mediation set of SKAdNetwork identifiers. SKAdNetwork is Apple’s own attribution system: it reports installs to ad networks in aggregate, with delays and thresholds designed to prevent any individual being identified, and it carries no identifier for you at all. Within it, an advertised app may set a single small number — a conversion value — summarising how far a player got. OverLit sets that number from the same milestones in section 7: 0 means the app was installed and nothing was reached, and it rises through the list to 16 for the Full Version purchase. Apple sends that number to the ad network that won attribution, and, because the app names Tenjin’s reporting endpoint, a copy to Tenjin. The developer receives campaign-level counts, not user-level data.

On Android there is no SKAdNetwork, because it is an Apple system. Attribution there works through the Google Play Install Referrer instead, which is why that row appears in the section 3 table for Android only.

What the ad platforms get back. Meta, TikTok and Google receive, from Tenjin, that an install from one of their adverts reached a given milestone. They use it to judge which adverts work and to find similar people to show them to, under their own privacy policies and as independent controllers. No list of players, no email addresses and no contact list is ever uploaded to any of them — OverLit holds none of those to upload.

The app-ads.txt file

To identify authorised sellers of OverLit’s ad inventory, this site publishes an app-ads.txt file.

House ads

Applies to both platforms.

When no network ad is available, OverLit may show a house ad instead: a panel promoting one of the developer’s own apps. These are bundled into the app. Showing one sends nothing to any ad network, and no data about you is used to choose it beyond whether you are being treated as an adult.

Which apps are promoted differs by platform, for the same reason the rest of section 3 does. On iPhone they are PlanKept and AudioChoices, plus Voice of Self, which is shown only to players treated as adults. On Android there is a single house ad, for AudioChoices, shown to everyone — the other two have no Android listing to send anyone to.

Tapping one opens the app store or a page on this website, and from that point the destination’s own policies apply. Rewarded ads are never replaced by a house ad, and Full Version suppresses house-ad fallback along with everything else.

Full Version removes ads

While the Full Version entitlement is active, OverLit makes no banner, interstitial or rewarded ad request and shows no house-ad fallback. If you have the “Help the Dev” setting on, you get a thank-you panel where an ad would have been.

7. Analytics And Measurement

Applies to both platforms, identically.

OverLit uses Google Analytics for Firebase, in a deliberately narrow way.

It starts switched off, and it stays off for minors. Analytics collection is disabled in the app’s configuration before any code runs. A player treated as a minor — the 13-to-17 band, or a country in section 14 — sends no OverLit Firebase milestone, purchase, conversion or gameplay events. Events that occur before the privacy process is complete, or while analytics is disabled, are not queued and are not replayed later.

For everyone else it is Google’s privacy message that turns it on, not a checkbox in these documents. For a player treated as an adult, the app first runs Google User Messaging Platform. Where Google’s message applies, UMP maps that player’s current privacy choice into Google Consent Mode, including the analytics_storage signal. The app then allows Firebase Analytics to operate under those Google-managed signals; it does not turn analytics on because the player accepted these documents, and on iPhone it does not use Apple’s App Tracking Transparency answer as analytics consent either. UMP and Firebase determine the resulting behaviour for the player’s region and choice, including any limited measurement Google provides when storage consent is denied. If the privacy message does not complete successfully, analytics stays off. This is the same mechanism on both platforms.

A correction to an earlier version of this document. Until Android gained an ad SDK, that build removed the advertising-identifier permission and switched off the identifier Google Analytics for Firebase would otherwise collect, because nothing in it had any use for one. That is no longer true and this sentence replaces it: the Android app now carries the Google Mobile Ads SDK, the permission is present, and identifier collection is enabled for a permitted collection. Whether a collection is permitted at all is unchanged and is still decided by the legal gate, the audience rule and Google’s privacy message.

There are two kinds of event, and only two. The full list is short enough to print, so it is printed.

Sixteen conversion milestones, each sent at most once, ever. The app keeps a local record of which have been delivered so that none repeats:

overlit_onboarding_complete, overlit_first_run_started, overlit_first_run_complete, overlit_level_1_complete, overlit_level_3_complete, overlit_level_5_complete, overlit_level_7_complete, overlit_level_10_complete, overlit_level_20_complete, overlit_level_30_complete, overlit_level_40_complete, overlit_level_50_complete, overlit_level_60_complete, overlit_level_70_complete, overlit_campaign_complete, and overlit_full_version_purchase.

The only parameters they carry are the milestone level number, the campaign’s level count, and the Full Version product identifier.

One repeatable event, overlit_mode_play, sent each time a run starts. This is the one event that is not deduplicated, because the question it exists to answer — how often each way of playing is actually played — is unanswerable if the second play is discarded. It is behavioural data about how the app is used, and it is described plainly here rather than folded into the milestone list, because it repeats and the others do not.

It carries two parameters, each drawn from a fixed short list rather than from anything about you or about the run:

• mode — exactly one of campaign, daily, random, pattern, snake, classic, other
• ruleset — exactly one of survival, time-attack, none

It carries no level number, no score, no result, no duration and no timing. It records which of seven surfaces a run was started on, and nothing else. Tutorial runs and developer-forced runs are excluded, because they are not a player’s choice of what to play.

The sixteen milestones have a second recipient; the repeatable event does not. The same sixteen names, and only the names, are also sent to the measurement partner described in section 6, so that advertising OverLit can be measured. The parameters above are not sent there, and overlit_mode_play is not sent there at all — it is behavioural data about how the game is played, which no ad platform needs and which would be a far larger disclosure than the milestones. A player treated as a minor sends neither, to either recipient.

Across both kinds: no score, no leaderboard identity, no age answer and no store transaction identifier is ever attached. The app sets no user identifier and no user properties.

Alongside those events, while Firebase Analytics is enabled, Google and Firebase process the standard app-instance identifier, session and app-launch information, app version, device and platform information, an approximate region derived from the network, and diagnostic metadata that Firebase Analytics needs in order to function at all.

8. The Full Version Purchase

Applies to both platforms. The store differs; nothing else does.

OverLit offers one optional purchase: Full Version, a one-time non-consumable in-app purchase. It removes ads and unlocks ad-gated themes, and it lets an existing level-skip offer complete without watching an ad. It does not unlock content that is meant to be earned by playing.

The store takes the payment — Apple through the App Store on iPhone, Google Play Billing on Android. No payment-card details, billing address or store account details ever reach the developer. The app checks your entitlement with the store on the device, stores the result locally along with the transaction identifiers needed to recognise a restored purchase, and supports the store’s own restore flow. There is no server-side receipt check, because there is no purchase server: entitlement is verified on your device.

If the store reports that a purchase was refunded or revoked, the app updates the local state to match.

The one-time overlit_full_version_purchase analytics event described in section 7 carries the product identifier only.

9. Why This Data Is Processed, And The Legal Basis

Under the GDPR, every purpose needs a lawful basis. These are the ones relied on:

Where consent is the basis, you can withdraw it at any time — section 12 explains how — and withdrawing it does not affect processing that already happened.

There is no automated decision-making that produces legal effects or similarly significant effects for you. Ad networks use automated systems to select, cap, measure and fraud-check ads, subject to your choices; that is not a decision about you in the legal sense.

You are not required to give the developer any personal data in order to play OverLit. There is no registration and nothing to fill in. Refusing advertising consent does not lock you out of the game, buying Full Version removes advertising altogether, and the leaderboard switch in section 5 means even score publication is optional.

10. Who Receives Data

Nothing is sold to a data broker. No customer list, contact list or support inbox is uploaded to any advertising platform — the developer holds none of those to upload. There is one attribution partner, named above, and no analytics vendor other than the Google products named above.

Information may additionally be disclosed where genuinely necessary to comply with law, to respond to a valid legal request, or to establish, exercise or defend legal claims. If the app or the developer’s business were ever transferred to someone else, relevant records could transfer with it, and this policy would be updated first.

11. International Transfers

Leaderboard records stay in the EU. The server functions and the database that hold the records described in section 5 run in Google Cloud’s europe-west1 region in Belgium. If you are in the EEA, the UK or Switzerland, those records do not leave the EU on an ongoing basis.

Other processing does reach the United States, and it is worth being clear about that rather than overstating how contained things are:

• Google LLC, which operates the EU-hosted infrastructure above, is itself a United States company. Some administrative access and some of Google’s own operational logging can still involve the United States.
• Google’s advertising and analytics services — AdMob, the Mobile Ads SDK, the User Messaging Platform and Google Analytics for Firebase — are global services, and the data described in sections 6 and 7 is processed outside the EU, including in the United States.
• Firebase Authentication and App Check are global Google services rather than regional ones.
• Tenjin Inc., the attribution partner in section 6, is a United States company, and the data it receives is processed there.
• Meta and TikTok receive attribution reporting about their own adverts and operate internationally under their own terms.
• Apple and Google Play process purchases, platform services and attribution under their own terms, internationally.

The safeguards relied on. Where personal data is transferred to the United States, that is made under Article 46 GDPR safeguards and, where applicable, the European Commission’s adequacy decision for the EU–US Data Privacy Framework. Google LLC and Apple are certified under the EU–US Data Privacy Framework and its UK Extension and Swiss–US counterpart, and Google’s data processing terms additionally incorporate the EU Standard Contractual Clauses. The attribution partner’s transfers rely on its own data processing agreement and the EU Standard Contractual Clauses. UK transfers additionally rely on the UK International Data Transfer Addendum or the UK Extension, and Swiss transfers on the Swiss–US Data Privacy Framework or the Swiss annex to the Standard Contractual Clauses.

A copy of the safeguards relied on can be requested at alekgameshelp2@gmail.com. Data Privacy Framework adequacy has been challenged before; if it were invalidated, transfers would continue under the Standard Contractual Clauses, and this policy would be reviewed.

12. Your Privacy Choices

The Google privacy message. Where required — in the EEA, the UK, Switzerland, and in US states with an applicable opt-out right — OverLit shows Google’s User Messaging Platform message before advertising or analytics starts. Your answer there governs whether personalised advertising, analytics storage and the associated storage on your device are permitted. On iPhone the Mobile Ads SDK is not started at all until that message reports that ads may be requested; on both platforms analytics stays off until it completes.

Changing your mind. When Google reports that a privacy-options form is required for your region, OverLit’s Settings screen shows a Privacy and cookie settings row that reopens it. That is the route to withdraw or change advertising and analytics consent. In some regions Google does not require that form, and the row is then not available; in that case your device-level advertising controls are the remaining lever.

US opt-outs. For applicable US state laws, Google’s message includes the “Do Not Sell or Share My Personal Information” style choice, and OverLit relies on Google’s implementation to carry that signal to the advertising stack. OverLit does not itself detect the Global Privacy Control or any other browser-level opt-out signal, because it is an app rather than a website.

Refusing. If you refuse consent or opt out, ads may still appear — contextual, non-personalised or otherwise limited by Google according to your choice and the law where you are. What changes is how the ad is chosen and what identifiers may be used, not whether ads exist at all, because ads pay for the free game.

Removing ads entirely. The Full Version purchase stops OverLit requesting ads at all.

Leaderboards. Settings → Legal → Post my scores to leaderboards stops your scores being published while you keep playing. Section 5 describes the switch and section 15 how to erase what was published before you used it.

Install measurement. The same Google privacy message governs whether the attribution partner in section 6 starts at all, so refusing there stops it too. On iPhone, declining Apple’s tracking prompt additionally means no advertising identifier is available to it, and what remains is aggregate measurement that cannot follow you between apps — that is a real reduction, but it is not zero, and section 6 says so plainly rather than implying otherwise. Buying the Full Version does not switch install measurement off: it is about which advert brought you here, not about serving you ads. Players treated as minors are excluded from it entirely.

Analytics. A player treated as a minor sends no OverLit Firebase analytics events of either kind. For everyone else the Google privacy message described above carries the analytics_storage choice where it applies. There is no second OverLit checkbox because it would not replace or override that Google consent mechanism. Accepting these documents is not analytics consent.

13. Store Privacy Labels

Apple’s App Privacy labels and Google Play’s Data safety section use each store’s own categories, which are broader and blunter than plain language. They are meant to describe the same practices as this policy, and because each store asks its own questions about its own platform’s identifiers (section 3), the two stores’ answers are not word for word the same.

On the App Store, the labels cover advertising data and product interaction from the AdMob SDK, the app’s own product-interaction events described in section 7, coarse location derived from IP address, device and SDK identifiers used for ad delivery, attribution and fraud prevention, the Full Version purchase event, and the diagnostic and performance data Google’s SDK reports. The attribution partner in section 6 is part of why device identifiers and product interaction are marked as used for third-party advertising.

Apple gives tracking a specific meaning: linking data from this app with data from other companies’ apps, websites or offline sources for advertising or advertising measurement, or sharing it with a data broker. Doing that requires permission through the App Tracking Transparency framework. The iPhone app does use that framework, for players treated as adults, so the App Store label does show Data Used to Track You. The label describes what may happen if you allow tracking; it does not mean tracking happens without your permission, and it never happens for a player treated as a minor.

On Google Play, the Data safety answers cover the same ground: the advertising data and device or other identifiers the AdMob SDK and the attribution partner handle, including the Google advertising ID; the coarse location derived from IP address; the app-activity and device information Firebase Analytics, the attribution partner and the leaderboard service handle; and the purchase state Play Billing handles. Play’s form also asks whether data is shared with third parties, and OverLit answers yes for the advertising categories, because AdMob is an independent controller rather than a processor acting only on the developer’s instructions.

What differs between the two forms is not the advertising, which is now the same on both, and not the attribution partner, which is also on both. It is Apple’s tracking question and the identifiers each platform provides: Apple’s advertising identifier and SKAdNetwork exist only on iPhone, and the Google advertising ID and Play Install Referrer only on Android.

If you ever find that a store label and this policy disagree, please tell the developer at alekgameshelp2@gmail.com. The labels are summaries; this policy is the detailed statement, and all of them should say the same thing.

Apple and App Store services are governed by Apple’s Privacy Policy and the Apple standard terms for apps. Google Play services are governed by the Google Privacy Policy.

14. Age, Children And Teens

OverLit is intended for players aged 13 and over. It is not directed to children under 13, and the developer does not knowingly collect personal information from children under 13. It is not enrolled in Apple’s Made for Kids programme or Google Play’s Designed for Families programme.

During onboarding the app asks you to choose an age range: 13 to 17 or 18 or older. There is no under-13 option and no path into the game without answering. The app does not ask for a date of birth and does not attempt any age verification, so the answer is self-declared.

That answer is stored on your device and never transmitted. It is not attached to any leaderboard record, is not sent as an analytics parameter, and no copy of it exists on any server. What it does is change three things: how the advertising SDK is configured, whether Firebase Analytics runs at all, and whether your scores are published to leaderboards by default.

A player treated as a minor gets non-personalised, Teen-rated ads, is never shown Apple’s tracking prompt, is kept away from the adult-only house ad, sends no OverLit Firebase analytics events of either kind, and is not published to a leaderboard unless they switch it on themselves.

Countries where everyone is treated as a minor

The age at which a person counts as a child varies by country, and in several places it is higher than 13. Where that is so, a self-declared “18 or older” is not always something OverLit can responsibly rely on. The two countries below are handled differently, because what their law actually asks for differs — so this table names what each one narrows rather than treating them as one rule.

The app determines this from the device’s own region settings — on Android, the SIM’s country where there is one, otherwise the device’s language and region; on iPhone, the device’s language and region. Nothing is sent anywhere to work it out. That is a hint rather than a verified location, and it is deliberately only ever used to restrict: a wrong guess can give someone the minor treatment who did not need it, never the reverse.

Elsewhere, the position is: in the EEA the age at which someone can consent on their own to services like advertising is set nationally, between 13 and 16. In the UK, the Information Commissioner’s children’s code treats everyone under 18 as a child and expects marketing profiling to be off by default for them, which is what the 13-to-17 configuration is. OverLit does not operate a parental-consent system and cannot verify anyone’s age.

If you are 13 or older but under the age of majority where you live, use OverLit with a parent’s or guardian’s permission where that is required. Where a player is below the relevant age in their country, the right steps are a parent’s or guardian’s involvement, the device’s own parental controls, or the Full Version purchase, which removes advertising entirely.

If you believe a child under 13 has provided personal information, write to alekgameshelp2@gmail.com and it will be dealt with.

15. Retention, And How To Delete Your Data

How long things are kept

On-device data stays on your device until you change it, use an in-app reset where one exists, or delete the app.

Leaderboard board entries have no automatic expiry. One entry per player per board is kept for as long as the board exists, and boards are archived rather than deleted when scoring rules change — an archived board stays readable indefinitely. An entry is removed when the board’s underlying record is erased on request.

The leaderboard de-duplication ledger expires automatically after 30 days. Each record carries an expiry timestamp and is deleted by the database’s own time-to-live process.

The private player record, the rate counters and the rating record are kept for as long as the anonymous identity exists — that is, until erasure.

Operational and access logs at Google are kept for the periods Google applies to its own logging by default. Those periods are set by Google rather than configured by the developer.

Advertising and analytics data held by Google is retained under Google’s own policies and the retention settings of the Firebase and AdMob products.

Support emails are kept for as long as reasonably needed to answer the request and keep a record of it.

Erasing your leaderboard data

The steps are on their own page: Delete your OverLit data. That page is a plain-language summary; where the two differ, this document governs.

The leaderboard service has a single function whose only job is deletion. It hard-deletes everything held against your anonymous identity: every board entry on every board, the private player record and its rate counters, the rating record, the de-duplication ledger, and the anonymous Firebase Authentication user itself. Your entries come off the live boards, not merely out of an internal table — a published score is public, so erasing it has to mean erasing what other people can see. The function is deliberately never blocked by the feature’s kill switch, because deletion has to keep working even when everything else is switched off.

The one thing it cannot reach is the cached copy of board rows held in other players’ de-duplication ledgers, described in section 5. Those are never shown on a board or to anybody else; the only way one can resurface is as the replayed result of that player’s own earlier submission, and they expire on their own within 30 days.

The route in the app is one tap, on both platforms. Open Settings → Legal → Delete my leaderboard data. It acts on your own identity directly, so nothing has to be matched and nothing has to be described. It is available whenever leaderboards are available to you, it asks you to confirm, and it cannot be undone. Your local progress, levels and unlocks are not touched — only what the leaderboard service holds.

By email, write to alekgameshelp2@gmail.com with the subject “Delete my leaderboard data”, carrying your leaderboard ID. Your identity is anonymous — no name, no email address, no account — so that ID is the only thing that says which data is yours; Settings → Legal → Copy my leaderboard ID puts it on the clipboard. Your nickname is not a substitute: it is drawn from a fixed vocabulary and is not unique. Without the ID the request cannot be actioned, and under Article 11 GDPR a controller that genuinely cannot identify a data subject is not obliged to acquire extra data in order to do so — inventing an identity-linking system to service deletion requests would be worse for everyone’s privacy than the problem it solves.

Deleting the app does not remove a published leaderboard entry.

Everything else

Local game data: delete the app, or use the in-app reset controls where they exist.

Advertising and analytics data held by Google: use the choices in section 12, and Google’s own privacy tools and account controls.

Purchase records: these belong to Apple or Google, and their support channels handle them. The developer holds no purchase server and no purchase database.

Support emails: ask, from the same address where possible, and they will be deleted.

Requests are answered within one month, as the GDPR requires. If a request is complex that can be extended by up to two further months, and you will be told why.

16. Security

Every connection the app makes is encrypted in transit with HTTPS.

For leaderboards specifically: the database denies all direct access from the app, so every read and write goes through server code that validates it. Each request must carry both a Firebase authentication token and a Firebase App Check token — backed by Apple’s App Attest on iPhone and Google’s Play Integrity on Android — which makes it substantially harder to submit scores from anything that is not a genuine copy of OverLit. Scores are checked against plausibility ceilings before they are accepted, submissions are rate-limited per identity, and retried submissions are de-duplicated rather than double-counted. The whole feature can be disabled remotely if it is abused.

Backend administrative access is limited to the developer and protected by the account security of the underlying platform providers.

No app, network, device or provider can be guaranteed to be perfectly secure. If you believe you have found a privacy or security problem, please write to alekgameshelp2@gmail.com before disclosing it publicly.

17. Your Rights

If you are in the EEA, the UK or Switzerland you have the rights below. They are honoured for everyone, everywhere, regardless of where you live.

• Access — ask what is held, and get a copy.
• Rectification — have inaccurate data corrected.
• Erasure — ask for data to be deleted. Section 15 explains the routes and the one real limitation.
• Restriction — ask that processing be limited while a dispute about accuracy or lawfulness is resolved.
• Portability — receive data you provided in a structured, machine-readable format.
• Objection — object to processing based on legitimate interests. That includes the anti-cheating measures in section 9 and, importantly, the publication of your score on a leaderboard. You do not have to write to anybody to exercise that one: Settings → Legal → Post my scores to leaderboards stops it, immediately and for good, while you keep playing. If you also want what was already published removed, section 15 is the route.
• Withdraw consent — for advertising and analytics, at any time, through the routes in section 12.

Two practical notes. First, most of what OverLit knows about you is on your phone and never reaches the developer, so for that data the fastest “access request” is to open the app. Second, for leaderboard data the anonymity cuts both ways: without something that identifies your entry, a request cannot be matched to it. Section 15 explains what to include.

Requests go to alekgameshelp2@gmail.com. There is no charge for the first request and no requirement to give a reason. You will never be treated differently for exercising a privacy right.

If you are unhappy with how a request was handled, you can complain to a data protection supervisory authority. The developer’s is Poland’s:

• Urząd Ochrony Danych Osobowych (UODO), ul. Stanisława Moniuszki 1A, 00-014 Warszawa, Poland — https://uodo.gov.pl/en

If you live elsewhere in the EEA you can also complain to your own national authority. In the UK that is the Information Commissioner’s Office, https://ico.org.uk. In Switzerland it is the Federal Data Protection and Information Commissioner.

18. Support Emails And Website Pages

If you email support, the developer receives your email address, your message, and anything you choose to include — for example your device model, OS version, app version, or a pasted Copy Progress summary. Please do not send sensitive personal information in a support message unless your request genuinely needs it.

Support email: alekgameshelp2@gmail.com. Support page: https://alekjaltuszyk.xyz/apps/OverLit/support/.

Support emails are not used for marketing, are not uploaded to any advertising platform, and are not used to build audiences.

The OverLit pages on alekjaltuszyk.xyz are static informational pages: the app page, support, these documents, the deletion page, the legal manifest and the public app-ads.txt file. They set no analytics cookies, no advertising cookies and no tracking storage of the developer’s own, which is why there is no cookie banner on them. Ordinary hosting and security infrastructure processes technical information such as IP address, browser type, requested URL, referring URL and timestamps, in order to serve and protect the site.

19. Changes To This Policy

This policy will be updated when OverLit changes in a way that affects it. The version number and effective date at the top of this page show when it was last updated, and the same values are published in the legal manifest linked in section 1.

Changes will not be made silently or retroactively. When there is a material change — for example a platform gaining an advertising SDK it did not have, switching leaderboards on for the first time, changing what is stored, changing retention, or changing the analytics setup — the app shows the updated documents again before you continue playing and asks you to accept the new version. The app records which version you accepted, and when, on your device.

If a future change would involve a genuinely new kind of data processing, this policy will be updated before that processing begins, not after.

20. Regional Information

The practices described above are applied globally, and the rights in section 17 are honoured for everyone everywhere rather than by jurisdiction. This section covers only the specifics that a particular law asks to be stated.

European Economic Area, United Kingdom, Switzerland. Sections 9, 11 and 17 are the operative ones: legal bases, international transfers, and your rights. Advertising and analytics rely on your consent, collected through Google’s privacy message, which also covers the ePrivacy consent needed to store and read information on your device. Leaderboard records are stored in the EU. The controller is Aleksander Jałtuszyk, Poland; the lead supervisory authority is UODO. UK users may also contact the ICO, and UK transfers rely on the safeguards named in section 11.

In the UK, the Information Commissioner’s children’s code applies to services likely to be accessed by under-18s and expects marketing profiling to be off by default for them, and expects a child’s profile not to be public by default. Players who choose the 13-to-17 band get non-personalised ads with a Teen content cap and are not published to leaderboards unless they choose to be. Players who choose 18 or older are treated as adults, and the app cannot verify that choice.

United States. Personal information is not sold for money. However: several US state privacy laws define “sale”, “sharing” and “targeted advertising” broadly enough that serving personalised advertising through an ad network can fall within them, whether or not any money changes hands. Where that applies, the opt-out is Google’s privacy message, described in section 12. Buying the Full Version stops advertising being served to you entirely, but — stated precisely rather than generously — it does not by itself stop the install measurement in section 6, which is about which advert brought you here rather than about showing you more. Refusing in Google’s privacy message is what stops that, and it stops the advertising too. No sensitive personal information is collected. The rights in section 17 are honoured for US residents on the same terms as for everyone else, and there is no discrimination for exercising them.

OverLit is an app rather than a website, so there is no browser-level opt-out preference signal such as Global Privacy Control for it to receive. The in-app privacy message and your device’s advertising settings are the equivalent controls.

Teenagers in the United States. A growing number of states restrict targeted advertising to consumers a business knows to be a minor — Connecticut for 13-to-17-year-olds, Colorado and others for everyone under 18. Because OverLit asks for an age band, it knows when a player has said they are 13 to 17, and configures advertising for that player with personalisation disabled and a Teen content cap. That is the point of asking.

Children in the United States. OverLit is not directed to children under 13 for the purposes of COPPA. It offers no under-13 path, asks for no contact information from anyone at any age, and keeps the declared age band on the device. Nothing is knowingly collected from a child under 13, and no parental-consent mechanism is operated because none is needed for a service that does not accept under-13 users.

Canada, including Quebec. Quebec’s Law 25 requires that the person responsible for the protection of personal information be identified: that is Aleksander Jałtuszyk, reachable at alekgameshelp2@gmail.com. Technology capable of identifying, locating or profiling a user is disclosed in sections 5, 6 and 7, and the means of deactivating it are in section 12. There is no automated decision made about you.

India and South Korea. See section 14: every player in these countries is given the minor treatment, whichever age band they chose.

Brazil. Under the LGPD the controller is a small-scale processing agent with no Data Protection Officer appointed; the communication channel for data subjects is the contact in section 21.

Elsewhere. The same protections and the same rights apply, and requests go to the same address. Where local law requires a specific contact or a specific right that is not listed here, write to that address and it will be handled.

21. Contact

Privacy questions, data-subject requests and deletion requests:

• Email: alekgameshelp2@gmail.com
• Support page: https://alekjaltuszyk.xyz/apps/OverLit/support/
• Telephone: +48 73 2099027
• Mailing address: Aleksander Jałtuszyk, Skrytka Pocztowa 59, UP Warszawa 93, 02-800, Warszawa, Poland
• Country: Poland