Short version: we collect sign-in data through Epic Online Services and, on iPhone and iPad, Sign in with Apple. Google AdMob collects device and advertising identifiers (on iOS, the advertising ID only with your consent in Apple’s App Tracking Transparency prompt). We use this data for cross-platform sign-in, multiplayer, leaderboards, and ads, including personalized ads where the law and your choices allow it. We share it with Epic Games, Apple, and Google for those purposes, and we do not sell it. You can delete your account in the game at Settings → Delete Account; your data is deleted straight away (a step that fails is finished by hand within 30 days), and the minimal record of the request is deleted after 90 days. Scores and cosmetics from solo play stay on your phone. Without an account, the game does not connect to Epic at all. On first launch the game asks for your month and year of birth, which stays on the phone: under 16, ads are never personalized and signing in needs a parent’s agreement; under 13, online features are off. Script errors are reported to our service without any player or device identifier; you can turn this off in Settings. Online features (cloud saves, multiplayer, and leaderboards) need an Epic account or, on iPhone and iPad, Sign in with Apple. Signing in stores a nickname, your best scores with the landing times of the runs that set them (to check for cheating), and a cloud progress file. Multiplayer rooms admit only players with a valid lobby pass, a short-lived pass that our service signs for Epic and Apple accounts. Ads in the game are served by Google AdMob. The homepage of this website shows Google AdSense ads, which can store advertising cookies. Where the law requires a choice, Google’s own message asks about those cookies and about ad personalization. Cloudflare hosts this website and processes technical visit data, such as your IP address, for security and statistics. This website does not ask you to create an account.
- Who we are
- How data is captured
- On your device
- Epic and online play
- Advertising
- The clock
- Error reports
- Feedback
- This website
- How data is used
- How data is shared
- Transfers
- Retention and deletion
- Your rights
- Children
- US states
- Store summary
- Contact
Who is responsible
The controller of personal data for Color Track 2 and for this website is Solpaw Paweł Sołtys, established in Poland.
Privacy and deletion requests: kontakt@demono10000.pl
Other questions: kontakt@pawelsoltys.dev
Postal address: Solpaw Paweł Sołtys, ul. Jana i Jędrzeja Śniadeckich 20D/7, 35-006 Rzeszów, Poland.
Phone: +48 17 77 96 007. This number connects to an automated information line. Please send support, business, and data protection (GDPR) inquiries by email to the addresses above.
Tax ID (NIP): 5170447240
No data protection officer has been appointed. Write to the privacy address above.
This policy covers the Color Track 2 app for Android and iOS, and the website at colortrack2.pawelsoltys.dev. It does not cover Apple, Google, or Epic when they act for their own store or account services. Those companies explain that in their own policies.
How data is captured
The game and its service providers capture data in these ways:
- Authentication through Epic Online Services (EOS). When you sign in with Epic, you do so on Epic’s own sign-in page. EOS then gives the game your Product User ID, your Epic Account ID, and your display name. There is no online play without an Epic or Apple account.
- Authentication through Sign in with Apple (iPhone and iPad). Apple’s sign-in sheet gives the game a signed token that identifies your Apple account to this game. The game does not ask Apple for your name or email address. It passes the token to EOS, which opens your game profile.
- Device and advertising identifiers through Google AdMob. The AdMob SDK collects the advertising ID and device details when the game requests ads. On Android this is the AAID. On iOS, AdMob gets the IDFA only if you allow it in Apple’s App Tracking Transparency (ATT) prompt. Where the law requires consent, Google’s consent form comes first.
- Gameplay data. The game records scores, progress, and cosmetics on your phone as you play. Once you sign in, your progress also goes to EOS as a cloud file, and your best scores with your nickname and the run’s landing times go to our leaderboard service.
- Requests to our account and leaderboard service. While you are signed in, the game sends your best scores with their landing times and your nickname to our service on Cloudflare, asks it whether your account still exists, gets a lobby pass before multiplayer, sends the reports you make about leaderboard entries, and downloads leaderboards and the day’s Daily Challenge. Each of these requests carries a token signed by Epic for your account; downloading a leaderboard or the Daily Challenge needs no token. When you delete your account, the game sends the same kind of token, plus a one-time Apple code if you signed in with Apple. Our service uses a hash of your IP address only to limit how many requests one connection can send in a minute, and never stores the address or the hash in its database. Cloudflare’s request logs are described under retention.
- Automatic technical data and emails. Epic’s online-client count, the time check, and website visits are described in their own sections below. We receive an email only if you choose to write to us.
What stays on your device
The game can be played solo without an account. Local configuration and save files on your phone (containing your settings, rewards, economy state, and ghost runs) hold:
- coins, owned cosmetics, favorites, and what you have equipped (pawn, island, landing trail)
- chest progress, including the 10-chest pity counter
- the 7-day daily-reward streak, 10-minute play-time reward timer, and daily quests
- personal bests and the local ghost recording of your best runs
- sound, vibration, and whether the best-run ghost is enabled
- how you sign in, whether you answered the question about saving scores online, and the month and year of birth you entered when you first started the game
- your Apple user identifier if you sign in with Apple, scores waiting to be sent to the leaderboards (with their landing times), the game language, and a random ID for this installation
- nicknames you reported as offensive, so the game no longer shows them on this phone
- counters that limit how often a full-screen ad can appear
- error reports waiting to be sent, if a script error happened (see below)
The game does not upload these files itself. The exception is the phone’s own backup: if backup is on, Android (backup to your Google account) and iPhone (iCloud Backup or a computer backup) can include these files and restore them when you reinstall the game. Google or Apple runs and stores that backup under your account, and we cannot read it. Apart from that, data leaves the phone only in the cases described below.
The app does not ask for your location, contacts, photos, camera, or microphone. It uses the internet, network/Wi-Fi state (so online features and ads can load), and device vibration (for haptic feedback, which you can turn off in Settings).
Leaderboards, multiplayer, friends, and Epic
Solo play needs no account. Online features — cloud saves, multiplayer, and leaderboards — need an Epic Games account or, on iPhone and iPad, Sign in with Apple. You can sign in under Settings, or when the game asks after a run. There is no online play without an account. Leaderboards have no separate switch: while you are signed in, your best scores are sent.
Automatic online-client count. The game starts the Epic Online Services SDK only after you choose to sign in, and on later launches while you stay signed in. If you play without an account, the SDK does not start and the game does not connect to Epic at all. While the SDK runs on an online device, Epic’s SDK automatically counts that client as an online instance (concurrent users) for Epic’s Game Analytics dashboard. Epic states that this count becomes active when the SDK initializes on an online machine. Color Track 2 does not call Epic’s play-session functions, so that dashboard does not receive a named session from us: no display name, controller type, match identifier, server address, or retention record tied to an account. The automatic signal is that a copy of the game is online, together with the connection data needed to reach Epic (including IP address and the game’s product and deployment identifiers). After you sign out, the SDK no longer starts from the next launch, and the count is never sent while the device has no network connection. A nickname, scores, the cloud progress file, and live lobby presence are sent only after you sign in, as described below. When those services are used, Epic can also aggregate that same service traffic in its developer analytics. The game does not add a separate custom-event tracker.
Signing in with Epic: Epic shares with the game your Epic Account ID, Product User ID, and public display name. Your nickname on leaderboards and in rooms is that display name. An encrypted progress file (coins, unlocked cosmetics, favorites, equipped items, daily streak, play-time cycle, daily quests, chest pity counter, and personal bests) is stored in Epic Player Data Storage under your Product User ID, allowing the same Epic account to carry and merge progress across phones. The same Product User ID is shown at the bottom of Settings. The game never sees your Epic password; Epic’s official sign-in portal handles authentication. The file also holds a random ID for each of your phones, used only to merge saves between them.
Signing in with Apple (iPhone and iPad): Apple’s sign-in sheet handles authentication, and the game never sees your Apple password. The game does not ask Apple for your name or email address, so your nickname is generated from your Product User ID: it is the same on every device and contains nothing about you. EOS uses Apple’s signed token to open a Product User ID for your Apple account, and links the phone’s device identifier to it so you stay signed in. Your encrypted cloud progress file is stored under that ID in EOS, and your best scores in our leaderboard service, as with an Epic login. Because later launches reconnect through the phone’s device identifier, our service records once that this Product User ID belongs to an Apple account (see below). The ID is shown at the bottom of Settings.
Leaderboards & Quick Match ghosts: While you are signed in, the game sends your best score for each mode, length, and difficulty to our leaderboard service. Signing in therefore puts your nickname and best scores on the public leaderboards. Other players see the rank, nickname, and score, never your Product User ID. Quick Match can use leaderboard entries to pace rival ghosts when no live room is available. The Daily Challenge gives every player the same track and rules for one UTC day. Its scores go to a separate daily leaderboard that shows only the current day’s challenge and starts empty at midnight UTC.
Our leaderboard service: it runs on Cloudflare Workers and keeps its data in a Cloudflare D1 database in Cloudflare’s Eastern Europe region (EEUR), without copies in other regions. Three tables hold player data: scores (Product User ID, leaderboard, best score, and when it was set), players (Product User ID, the nickname sent with your scores, and when it last changed), and verified_accounts (Apple accounts only: Product User ID, the word “apple”, and when it was confirmed). Three more tables hold each record-setting run, the time filters, and the Daily Challenge: runs (the run’s landing times in milliseconds, with Product User ID, leaderboard, score, and time), period_scores (your best score in the current UTC day, week, and month), and daily_scores (your best Daily Challenge score of each day, with the Product User ID, that day’s challenge, and when it was set). Another table holds the deletion records described under retention, and one more, moderation, holds our decisions after a report or a cheating check: the Product User ID, whether your nickname is shown as “Player” or your scores are left out of public leaderboards, a short note, and when we decided. Another table, reports, holds the reports players send by tapping a leaderboard entry: the Product User IDs of the player who reported and of the player reported, the reason (offensive nickname or cheating), the leaderboard where the entry was seen, the reported nickname, and when the report was sent. We never show anyone who sent a report. Public leaderboard pages show the rank, nickname, and score with an identifier made with a secret key, so it cannot be traced back to your Product User ID. Before a page is published, each nickname is checked against a list of offensive, hateful, and misleading words (such as names posing as us or as Epic), and a name on that list is shown as “Player”; the nickname as sent stays stored. Cloudflare may cache these pages for up to 60 seconds. The service accepts a score only with a token signed by Epic for an Epic account or a confirmed Apple account, only within limits a human player can reach, and only with a recording that matches the score. Recordings are not published; we use them to check suspicious scores.
Live multiplayer rooms (P2P): In a multiplayer lobby (up to 8 players), the game shares your display name, equipped pawn and landing trail, round scores, and live position/rotation along the track with other players in that room. Each device also adds a short room tag, made from a random value that stays on the device and different in every room, so the game can tell two devices on the same account apart: one account can be in multiplayer on only one device at a time. Live positions are transmitted peer-to-peer through Epic Online Services P2P relay (using WebRTC/STUN/TURN servers operated by Epic so connections work across NAT/firewalls without exposing raw player databases). If you signed in with Epic, the game can also read your Epic friends list so you can invite or join a friend. It never reads or uploads the address book from your phone. To host or join a room, the game gets a lobby pass from our service: a note signed by us with your Product User ID, valid for one hour. The game puts it in your lobby entry, where the other players’ games check our signature and that the pass belongs to your Product User ID, so only Epic and Apple accounts can play together. If you host, your pass is also visible to players looking for a room. Our service does not store issued passes.
Epic’s own privacy policy is at epicgames.com/site/privacy-policy.
Advertising
The game shows ads through Google AdMob. There are two kinds:
- Full-screen interstitial ads when you leave the results screen. Full-screen interstitial ads are rate-limited by internal cooldown timers and run counters so they do not interrupt gameplay excessively. If an ad is not ready, the game simply continues without delay.
- Rewarded ads that you actively choose to watch: an extra life during a run, +25 bonus coins (shown when you are within 25 coins of a 50-coin chest or a 200-coin Common skin), a doubled daily reward, a doubled play-time reward, or skipping the 10-minute wait for the play-time reward. Declining a rewarded ad never locks the rest of the game; only the extra bonus is skipped.
There is no banner fixed to the screen.
AdMob may collect and process your device’s Advertising ID (AAID on Android, IDFA on iOS if permitted), IP address (which may be used to estimate coarse location), device and operating-system details, language, app version, and ad-interaction/diagnostic data. Where the law requires consent (such as in the EEA, the UK, and Switzerland), Google’s User Messaging Platform (UMP) consent form runs before ads are initialized. On iOS, AdMob can use the IDFA only if you allow tracking in Apple’s App Tracking Transparency (ATT) prompt. The game shows that prompt on iPhone and iPad after Google’s consent form, before it requests any ad. If you decline, AdMob does not get the IDFA and the game plays the same. You can change your answer in the iPhone’s Settings → Privacy & Security → Tracking. You can reopen your privacy choices at any time in the game under Settings → Change Consent, or reset/limit the advertising identifier in your phone’s system settings.
Players under 16. When you first start the game, it asks for your month and year of birth. The answer stays on your phone; ad requests carry only a flag saying whether you are under 16 (and, separately, under 13), never your birth date. If you are under 16, the game shows neither Google’s consent form nor Apple’s tracking prompt, and every ad request is marked as coming from a user under the age of consent, so Google shows no personalized ads. Under 13, ad requests are also marked as child-directed. For everyone, ads are limited to Google’s G (general audiences) content rating.
Google’s privacy policy is at policies.google.com/privacy, and details on how Google uses information from apps that use its services are at policies.google.com/technologies/partner-sites.
We do not sell personal information for money. If you allow personalized ads, Google and its ad partners may use the advertising identifier across apps. Some US state laws call that “sharing” or “targeted advertising.” Use Settings → Change Consent or your phone’s system ad-privacy settings to opt out.
Time checks for daily rewards
Daily rewards and daily quests follow a real calendar day so changing the phone clock cannot grant them twice. To verify the date, the game makes a lightweight HTTP request to Cloudflare (cloudflare.com/cdn-cgi/trace) and Google (google.com/generate_204) with a user agent of ColorTrack2. The request sends standard HTTP connection metadata (including your IP address) and reads only the server timestamp/date header. It never sends your nickname, Epic ID, or game progress. Cloudflare and Google handle connection logs under their own privacy policies.
Error reports
When a script error happens in the game, the game can send our service an error report so we can find and fix the bug. A report contains the game version, the operating system name (for example Android or iOS), the place in the game’s code where the error happened (file, line, and the functions that led there), the error text, and how many times it happened. Before sending, the game removes anything that could point to you or the phone, such as player IDs, nicknames, email and IP addresses, file paths, long numbers, and free text in quotes; our service removes them again. Reports carry no player ID, advertising ID, or device ID, and the game sends at most 10 different errors per session. Until a report is sent, it waits in a file on your phone.
Our service keeps one entry per distinct error in our Cloudflare D1 database: the counts and one example of the text, not individual reports. It deletes each entry 90 days after that error was last reported. Like every request to our service, a report passes through Cloudflare, whose request logs keep the IP address for up to 7 days (see below). Our service uses a hash of the IP address only to limit how many reports one connection can send, and never stores it with a report. Legal basis: our legitimate interest in keeping the game working (Art. 6(1)(f) GDPR). You can turn error reports off at any time in Settings → Error Reports; turning them off also deletes reports still waiting on the phone. Because reports are not linked to you, we cannot find or delete one player’s reports; they expire after 90 days.
Feedback
If you send feedback or a question to kontakt@pawelsoltys.dev from your email app, we receive only the email you send, including your email address, and use it solely to reply to you and improve the game. The game does not send feedback in the background.
This website
This website is a set of static files. It has no user accounts and no shop, and it does not load fonts or videos from third-party servers. Apart from Cloudflare’s statistics described below, we do not use an audience-analytics tool.
The homepage loads Google AdSense (publisher ca-pub-1913173941460212) so Google can show ads. AdSense may store cookies and similar identifiers in your browser, and it receives your IP address together with device and browser details. Google uses that to deliver ads, cap how often you see the same ad, measure ad performance, prevent invalid traffic, and — if you agree — personalize ads. The privacy policy, terms, cookie notice, chest-odds page, data-deletion page, and error page do not load the AdSense script.
Where the law requires a choice, including in the EEA, the UK, and Switzerland, Google shows its own consent message on the homepage before personalized ads and the related cookies. We do not add a second banner. You can change that choice later in Google’s message, or in Google’s ad settings. How Google uses cookies is described at policies.google.com/technologies/cookies. The names and lifetimes of those cookies are set by Google, not by us. Details of the cookies we know about are on the Cookies page.
If you switch the website language, your choice is saved in your browser’s local storage under the key ct2-lang (for example en, pl, es-419, pt-BR, fr, or de). That value stays on your device, is never sent to us, and can be cleared at any time in your browser settings.
Hosting and content delivery (Cloudflare). This website is hosted on Cloudflare’s infrastructure and delivered through its content delivery network (CDN). Both services are operated by Cloudflare, Inc., USA. Every visit passes through Cloudflare’s servers. For security, analytics, and DDoS protection, Cloudflare automatically collects and processes technical data about each request: your IP address, system configuration (such as browser type and version, operating system, and language settings), and routing information (such as the requested address, the referring page, the time, and the Cloudflare data center that handled the request). Cloudflare uses this data to deliver the pages, detect and block attacks and automated abuse, and give us traffic statistics. The pages also load Cloudflare Web Analytics, a small Cloudflare script that reports the page address, the referring page, and page-load timings. It does not use cookies or local storage. When Cloudflare checks whether traffic is automated, it may show a security check and set a short-lived security cookie (see Cookies).
Cloudflare runs a global network, so this data may be transferred to and processed on servers outside the European Economic Area (EEA), for example in the United States (see International transfers). Cloudflare processes it on our behalf under its data processing terms, and handles some of it, such as information about threats to its network, under its own privacy policy: cloudflare.com/privacypolicy. The legal basis is our legitimate interest in delivering this website securely and reliably and in knowing how much it is used (Art. 6(1)(f) GDPR). We do not combine this data with game profiles.
How data is used, and the legal basis
We use data for these purposes:
- Cross-platform authentication: signing you in and keeping your game profile. An Epic login works on both Android and iOS, and Sign in with Apple works on iPhone and iPad.
- Multiplayer: running rooms, inviting Epic friends, sending live race data between players, and issuing and checking lobby passes so only Epic and Apple accounts join rooms.
- Leaderboards: showing scores and nicknames, checking each score against the recording of its run to stop cheating, keeping offensive or misleading nicknames and manipulated scores off public leaderboards, pacing Quick Match ghosts, and running the Daily Challenge with its daily leaderboard.
- Cloud progress: keeping your coins, cosmetics, and rewards on your account.
- Advertising: showing ads, limiting how often they appear, measuring them, and preventing fraud. Personalized ads use your advertising identifier. Where the law requires consent, ads are personalized only if you agree.
- Account deletion: carrying out your request, revoking Apple tokens, and deleting your scores, run recordings, and nickname from our leaderboards.
Where the EU or UK GDPR applies, we rely on the following legal bases:
- Performance of a contract (Art. 6(1)(b) GDPR): providing the game you chose to play, saving progress locally, and—when you sign in—providing sign-in, public leaderboards, cloud progress synchronization, and live multiplayer rooms.
- Consent (Art. 6(1)(a) GDPR): personalized advertising, and the cookies or device identifiers used for it, where a consent form is required. In the game, withdraw consent via Settings → Change Consent. On this website, use Google’s AdSense consent message or Google’s ad settings. Withdrawal does not affect the lawfulness of processing before withdrawal.
- Legitimate interests (Art. 6(1)(f) GDPR): non-personalized/contextual ad frequency capping, verifying the calendar date so daily rewards are not exploited, preventing leaderboard cheating (including keeping the recordings of record runs, and Daily Challenge results with their recordings for 90 days), keeping players without a valid lobby pass out of multiplayer rooms, preventing abusive nicknames in lobbies and on leaderboards (a word filter, player reports, and our moderation decisions), finding and fixing errors in the game through error reports without any identifier, delivering this website securely through Cloudflare, measuring its traffic, and Epic’s automatic concurrent-user count, which runs only after you have chosen to sign in. You have the right to object to processing based on legitimate interests.
- Legal obligation (Art. 6(1)(c) GDPR): complying with applicable laws and valid requests from competent authorities, including data-protection requests. This includes handling account-deletion requests and keeping the record that shows they were handled, and asking for your month and year of birth so that players under 16 get no personalized ads and need a parent’s agreement to sign in.
Providing personal data is voluntary; you can play Color Track 2 solo offline/locally without signing in. We do not use automated decision-making or profiling that produces legal or similarly significant effects on you.
How data is shared
We share data only with the recipients below, and only for the purposes described above. We do not sell it.
- Epic Games, Inc. (Epic Online Services). Once you have chosen to sign in, Epic receives the SDK’s automatic concurrent-user count whenever the game runs with a network connection. It also receives what online features need: authentication, friends, P2P lobbies, and encrypted player data storage. Leaderboards run on our own service, not on Epic. If you sign in with Apple, Epic also receives Apple’s signed token to open your game profile.
- Google Ireland Limited / Google LLC (and advertising partners shown in Google’s consent message), for AdMob ads in the game, AdSense ads and cookies on this website, consent, and the HTTP time check.
- Cloudflare, Inc., as the host and CDN of this website (technical data of every visit, for security, analytics, and DDoS protection) and for the game’s HTTP time check. Cloudflare also runs our account and leaderboard service, which stores leaderboard scores, run recordings, nicknames, player reports, moderation decisions, Apple-account confirmations, and deletion records in a Cloudflare D1 database in Eastern Europe, and signs lobby passes.
- Apple Inc., for Sign in with Apple and the App Tracking Transparency prompt on iPhone and iPad. When you delete an account that uses Sign in with Apple, our account service asks Apple to revoke the game’s tokens.
- Apple Inc. or Google LLC, as the app store from which you download the game (acting as independent controllers of your store account).
- Other players can see your nickname and scores on leaderboards. In a room, they can also see your display name, equipped items, round scores, and live position.
- Public authorities, only if required by applicable law.
Leaderboard scores, run recordings, nicknames, player reports, moderation decisions, Apple-account confirmations, and deletion records are kept in our own database, described above and under retention. Game progress stays in your cloud file at Epic and on your phone. We never sell lists of players.
International transfers
Epic Games, Apple, Google, and Cloudflare may process data on servers in the United States and other countries outside the European Economic Area (EEA). For Cloudflare, this includes the technical data of every visit to this website. Our own database runs in Cloudflare’s Eastern Europe region, but Cloudflare’s worldwide network carries requests to it and can briefly cache public leaderboard pages anywhere. Where the GDPR requires a transfer safeguard, those providers rely on the EU–US Data Privacy Framework (where certified) and/or the European Commission’s Standard Contractual Clauses (SCCs). Details are available in their respective privacy policies linked above.
How data is retained and deleted
- On your phone: until you uninstall the app or clear its app storage.
- EOS cloud progress: kept for as long as you use online features, or until you delete your account (see below), delete your Epic account, or Epic removes inactive records under its service rules. Logging out or uninstalling the app does not erase copies already stored in EOS.
- Leaderboard scores, run recordings, nicknames, player reports, moderation decisions, and Apple-account confirmations (our D1 database): kept while your account exists, and deleted at once when you delete it. Signing out does not delete them. A report is deleted once we have decided on it, and otherwise 90 days after it was sent; deleting your account deletes the reports you sent and the reports about you. A daily cleanup deletes entries for a day, week, or month within a day after that period ends, and a run’s recording within a day after no leaderboard points to it. Daily Challenge results and their recordings are kept for 90 days after the challenge day, so we can look into cheating reported after the day ends; the daily cleanup then deletes them, and deleting your account deletes them at once. Copies of public leaderboard pages in Cloudflare’s cache expire within 60 seconds. Cloudflare D1 keeps restore points (Time Travel) of the whole database, so deleted rows can remain in them for up to 30 days before they expire. We use restore points only to recover from errors.
- Deletion records: stored securely in our Cloudflare D1 database. Each record holds the Product User ID, a request ID, the request time, the platform, the app version, the result of the Apple revocation, and the processing status. It holds no nickname, email address, IP address, or game progress, and it is never published. It blocks new scores and lobby passes for that ID and shows that the request was handled. We delete it automatically 90 days after the request.
- Error reports: one entry per distinct error in our Cloudflare D1 database, with counts and one scrubbed example and no player, advertising, or device ID; deleted 90 days after the error was last reported. Reports waiting on the phone are sent, or deleted when you turn reports off.
- EOS concurrent-user counts: aggregate figures held by Epic under its own privacy policy. They are not a named player profile we can look up and delete. A deletion request covers the records we can identify, such as the cloud progress file and leaderboard scores.
- Advertising data: retained by Google in accordance with Google’s privacy policy and retention schedules, both for AdMob in the game and for AdSense cookies on this website. Clearing cookies in your browser removes the copies stored on that browser.
- Time-check responses: used in memory to anchor the game clock and discarded immediately; standard connection logs are governed by Cloudflare’s and Google’s policies.
- Website visit data: kept by Cloudflare only as long as it needs for delivery, security, and statistics, under its own retention rules. We see Web Analytics figures only in aggregate.
- Logs of requests to our account and leaderboard service: Cloudflare Workers Logs record each request with your IP address, an approximate location derived from it, the app’s user agent, and the requested address. The sign-in token is masked and not stored. They are kept for up to 7 days (3 days on Cloudflare’s free plan) so we can fix problems.
- Support and privacy emails: kept for the time needed to resolve your inquiry and for up to 3 years afterward if needed to document compliance or defend against legal claims (deletion requests are logged only as a minimal record that the request was fulfilled, without keeping your game data).
Deleting your account. You can delete your account and data directly in the game at Settings → Delete Account. The game deletes your cloud progress file, removes the link between your game profile and your Epic login, Apple ID, or device identifier, and erases the progress saved on your phone. If you signed in with Apple, this also automatically revokes the game’s Apple tokens. Your scores, run recordings, and nickname are deleted from our leaderboards at once; cached copies expire within a minute. If a step cannot finish, for example because the connection drops, we complete it by hand within 30 days. Epic does not let a game delete the Player ID (Product User ID) itself, so that ID may remain in Epic Online Services permanently, empty, with no progress, cloud save, or login linked to it. Other phones that used the same Apple account unlink their device identifiers the next time the game runs on them with an internet connection; a phone where the game never runs again leaves its identifier at Epic. These empty IDs and leftover device identifiers are anonymous technical records and contain no personal information. Apart from them, we keep only the deletion record above, for 90 days, and any email you sent us. Details are on the Delete your data page.
Your rights
If the GDPR applies, you have the right to access your personal data, rectify inaccurate data, erase data (“right to be forgotten”), restrict processing, receive a portable copy of data you provided, and object to processing based on legitimate interests. Where we rely on consent, you can withdraw it at any time.
If you live in Brazil (LGPD) or another country with a similar law, you have the rights that law gives you, including access, correction, deletion, and information about who receives your data. Use the same contact address.
The quickest way to erase your data is Settings → Delete Account in the game.
You can also write to kontakt@demono10000.pl and paste the Player ID from the bottom of Settings (use Copy). That ID is your Epic Product User ID. We use it to find your record, delete the cloud progress and leaderboard entries tied to it, and email you when that is done. A generated nickname or display name is not enough, because more than one player can share a similar name. If you already uninstalled the game and cannot copy the ID, say so in the email and name the Epic display name and the device you used. We will tell you if we cannot match a single record. We respond within one month.
You have the right to lodge a complaint with a data-protection supervisory authority. Because the controller is established in Poland, our lead authority is the President of the Personal Data Protection Office (Prezes Urzędu Ochrony Danych Osobowych — UODO), ul. Stanisława Moniuszki 1A, 00-014 Warszawa, Poland (uodo.gov.pl). You may also contact the supervisory authority in the country where you live or work.
Step-by-step erasure instructions are on our Delete your data page, which also serves as the official data-deletion link for Google Play and the App Store.
Children
Color Track 2 is a general-audience casual game. When the game first starts, it asks every player for their month and year of birth and uses the answer only on the phone. Players under 13 cannot sign in or use online features. They can play solo, and their ad requests are marked as child-directed (see above).
If you are 13 to 15 years old, the game shows no Google consent form and no personalized ads, and asks you to confirm that a parent or guardian agrees each time you sign in with Epic or Apple. If you live in the EEA, the United Kingdom, or Switzerland and you are under the digital-consent age in your country (16 in Poland), do not consent to personalized ads in Google’s message on this website unless your parent or guardian agrees. Without an account, the game does not connect to Epic at all.
If you are a parent or guardian and believe a child has submitted personal data through online features, please email kontakt@demono10000.pl and we will promptly delete the associated cloud progress and leaderboard entries.
California and other US state privacy laws
If you live in California (CCPA/CPRA), Colorado, Connecticut, Virginia, Utah, Texas, Oregon, or another US state with a consumer privacy law, you may request to know/access, correct, or delete your personal information, and to opt out of “sale,” “sharing” for cross-context behavioral advertising, or targeted advertising. We do not sell personal information for money, and we do not knowingly sell or share personal information of individuals under 16.
In the preceding 12 months, depending on which features you use, the categories of personal information processed are: identifiers (device ID, advertising ID, IP address, Epic account ID/Product User ID, Apple user identifier, display name/nickname, AdSense cookie identifiers on this website), internet or electronic network activity (visits to this website processed by Cloudflare, ad requests and interactions in the game and on this website, HTTP time check, requests to our account service, the EOS client-online count when the game runs online after you choose to sign in, multiplayer P2P session traffic), and gameplay records (scores, landing times of record runs, unlocked cosmetics, coins, quest/streak state). We do not collect sensitive personal information, precise geolocation, biometric data, or government IDs.
We do not discriminate against you for exercising your privacy rights. To exercise a right, use Settings → Change Consent in the app, Google’s ad settings for ads on this website, your device’s advertising ID settings, or email kontakt@demono10000.pl stating your state of residence and request. If we decline a request, you may appeal by replying to our response with the word “Appeal.”
Security
Local progress is stored in the operating system’s sandboxed app storage. Online communication with Epic Online Services, Google AdMob, Google AdSense, and time servers uses encrypted HTTPS/TLS connections, and the cloud progress file in Epic Player Data Storage is encrypted using AES-256 client-side encryption configured for the game. Connections to Apple and to our account and leaderboard service also use HTTPS/TLS. Data in Cloudflare D1 is encrypted at rest with AES-256. Only leaderboard rows are published (rank, nickname, score, and a keyed identifier). The service accepts scores, status checks, lobby-pass requests, and deletion requests only with a token signed by Epic for that account, so nobody can post scores for, check, get a lobby pass for, or delete another player’s account by knowing their ID. Lobby passes are signed with a private key that only our service holds; the game checks each pass with the matching public key built into the app, so a pass cannot be forged, altered, or used for another player.
Changes
If this policy changes, the updated text will be published on this page with a new effective date. Where the law requires notice or renewed consent before a material change, we will provide that in the game before the change takes effect.
A map for the store forms
This summary matches how Google Play’s Data Safety section and Apple’s App Privacy labels categorize data:
| Category | How Color Track 2 handles it |
|---|---|
| Location | No GPS or precise location permission is requested. Google AdMob may infer coarse location (country/region) from IP address for ad serving and fraud prevention. |
| Contacts, photos, camera, microphone | Not collected or accessed. Epic friends are queried from Epic Online Services only if you sign in with Epic, never from your phone’s address book. |
| User IDs & Name | Optional. Epic display name and Account ID if you sign in with Epic. An Apple user identifier and a generated nickname if you sign in with Apple (the game does not request your Apple name or email). Your Product User ID and nickname are also stored with your best scores in our leaderboard service. |
| Device or other IDs | Advertising ID used by Google AdMob for advertising and frequency/fraud checks: AAID on Android, and IDFA on iOS only with your App Tracking Transparency consent. Device ID used by Epic Online Services only to keep a Sign in with Apple session active on the phone. |
| Gameplay & app activity | Scores, unlocked cosmetics, coins, streaks, and quests—stored locally on the phone and, after you sign in, synced to Epic Online Services (progress) and our leaderboard service (best scores and the landing times of the runs that set them). After you choose to sign in, the EOS SDK also sends Epic an anonymous concurrent-user count at startup while the device is online, without a player name. Without an account, the game does not connect to Epic. Ad interaction events are processed by Google AdMob. |
| Purchases & Financial info | None. There are no in-app purchases. |
| Not collected inside the app. Processed only if you write to us via your email client (for example, feedback or support questions). | |
| Diagnostics | No third-party crash-reporting SDK is embedded. The game sends its own error reports to our service (see Error reports): game version, operating system, the place in the code, and the scrubbed error text, with no player, advertising, or device ID; you can turn them off in Settings. The Google Mobile Ads SDK may collect basic ad-performance and crash/diagnostic data for its own SDK stability. Epic’s automatic concurrent-user count is usage telemetry, described in the row above, not a crash log. |
Contact
Privacy and deletion: kontakt@demono10000.pl
General contact: kontakt@pawelsoltys.dev
Phone: +48 17 77 96 007 (automated information line; please send all inquiries by email)
Related pages: Terms, Cookies, Delete your data, Chest odds.