What stays on your phone
SliceIT works without an account. Your unfinished game, history and preferences are saved in private app storage, alongside a local copy of your optional profile photo.
Your chosen profile photo is published in leaderboards. We use the system photo picker without access to your entire photo library.
Your optional account
Google Firebase Authentication processes your email, sign-in credentials and account identifier for authentication, email verification and password reset. Our game server never receives or stores your password. If you choose Google sign-in, Firebase also processes the Google account identifier and profile information supplied by Google. This information is not automatically published in the leaderboard.
The Firebase SDK also processes IP addresses for security and abuse prevention, platform and SDK versions, and the Firebase app identifier to operate the service. Read the Google Firebase privacy information.
Play Games achievements
Google Play Games uses a separate gamer profile for platform authentication and achievements. We send earned achievements to Google and keep milestone and delivery-confirmation flags on your device. Your Play Games profile does not change your Firebase game account or heart balance.
The Play Games SDK also processes gamer identity, game usage, analytics and diagnostics to operate and improve its services. Manage profile visibility and delete game data or your entire gamer profile through Play Games. Deleting your SliceIT account clears its local achievement queue; already unlocked achievements held by Google require separate deletion. Read Google's Play Games data information.
Public leaderboard
Normal-round results are automatically published for accounts and guests. The leaderboard contains average score, best streak, round count, a public player alias, the chosen nickname, country, profile flag and avatar or profile photo of accounts and guests. Internal player UUIDs, email, password and game geometry are not public. Results are not yet verified by the server. Country is your manual choice; the app does not access GPS or infer your location from IP addresses.
Selecting a photo in your profile gives consent to publish it; after processing it uploads automatically to the leaderboard. You can replace it with a built-in avatar and save the profile; after the change uploads successfully, the server stops serving it. Others may copy public data; their own copies are outside our control and previously cached copies may remain until they expire.
Offline results stay in a local queue and upload later. Account deletion also removes that account’s public results. Device-data deletion removes local data only.
Heart purchases
If you buy hearts, Google Play handles payment. Our server receives no card number or payment details. To verify purchases, restore balances, consume purchases and process refunds, we process the account identifier, product, quantity, order identifier and purchase token. Tokens needed for processing are encrypted; completed purchases are identified by their token hash.
We retain your balance, purchase history and spending records while your account exists. Account deletion removes the Firebase identity link, balance and rescued-round identifiers. Minimal pseudonymous replay-prevention and refund records remain for 90 days after deletion, then are removed during successful periodic cleanup. Google retains its payment records under its own rules.
What gets backed up
A verified account backs up your nickname, built-in avatar number and preferences over HTTPS: language, colours, sound, haptics, reduced motion, mode, difficulty, tutorial progress, chosen country and profile flag. We also back up personal round summaries, best streak and challenge progress.
Photos, unfinished game geometry and shared images are not backed up. We use the backup to restore your progress; personal results are not a public competitive leaderboard.
Purposes and legal bases
We process accounts, requested backups, profile settings and purchases to provide these features and perform the contract under GDPR Article 6(1)(b). Sign-in data is needed for accounts; purchase data is needed for verification and heart delivery. Without it, the related feature cannot work, but local play requires neither an account nor a purchase.
Automatic public leaderboards rely on our legitimate interest in enabling comparison of game results and displaying player profiles; operation logs and minimal purchase records support security, reliability and fraud prevention under Article 6(1)(f). You may object to this processing. Publishing an optional profile photo relies on your consent under Article 6(1)(a), which you can withdraw by replacing the photo with an avatar or contacting support; withdrawal does not affect prior lawful processing. Handling rights requests and specific legal obligations relies on Article 6(1)(c).
Leaderboard positions are calculated automatically from scores and streaks. We do not make decisions with legal or similarly significant effects or carry out advertising profiling.
Recipients and data transfers
We use Google Firebase Authentication, Google Play and Play Games services, server hosting and database infrastructure providers, Cloudflare for proxy and security, and Google for the support email mailbox. These providers process data needed for the stated services: sign-in and game data, purchases, backup contents, network data or support messages according to their role. Public profile information and results are available to leaderboard visitors. We may disclose data to competent authorities when required by law or to the extent necessary to protect legal rights.
Google and Cloudflare may process data outside the EEA, including the USA. Their published policies describe use of the EU–US Data Privacy Framework and, depending on the service, standard contractual clauses. Details and safeguards are described in Firebase information, Google's transfer policies and Cloudflare's policy; use the contact below to request information about our providers and applicable safeguards. Google Play and gamer profiles also follow Google's own processing rules.
Support and requests
When you contact us, we process your email address, message and information necessary to verify and resolve the issue. We provide support for requested services; other enquiries rely on our legitimate interest in answering users and protecting their data. Rights requests are handled to meet legal obligations. Do not send passwords, private tokens or card details.
We retain correspondence for the time needed to resolve the request and document its outcome; longer only to the extent needed for a legal obligation or a specific legal claim. We review the need for retention and remove data that is no longer needed.
Public guest data
We retain a guest's public profile, results and optional photo while they remain published, until removed following a verified request or linked to an account that you subsequently delete. There is currently no automatic cleanup of inactive guests. Uninstalling or clearing phone data does not remove their server copy.
Request access, correction or removal using the contact below. Include the public leaderboard ID and nickname. To prevent deletion of someone else's profile, we verify your control, for example through an agreed nickname change. A public ID alone is not proof of ownership. Do not send passwords or private tokens. Verification can be harder after losing the local profile; contact us in that case too.
Your control over your data
We keep your active cloud backup until account deletion, which removes your cloud profile, results and Firebase identity. A deletion identifier is retained until deletion completes and for approximately one additional hour, until the next successful periodic cleanup, to prevent in-flight writes.
Signing out keeps on-device data. Remove local data in the game’s settings or Android app-storage settings on each device. Copies on other devices must be cleared there too; the local guest profile is separate from your account.
How long data is retained
Operational database copies are retained for at most 30 days and hosting logs for at most 7 days.
Deleted data is not returned to active use. Deletion requests are reapplied after a database restore. Contact the operator below to access, correct or delete your personal data.
Google's retention periods
The periods above for our database copies and hosting logs do not apply to Google's separate systems. According to Google's information, Firebase Authentication retains logged IP addresses for a few weeks; after account deletion is initiated, other authentication data is removed from live and backup systems within 180 days. Google Play payment records and the Play Games profile follow Google's own rules. Separately delete game data or your gamer profile through your Play Games profile.
Your rights
Subject to GDPR conditions, you have rights to access and obtain a copy, correction, erasure, restriction, and portability of data processed automatically on the basis of contract or consent. You may object to processing based on legitimate interests on grounds relating to your particular situation. You may withdraw consent at any time without affecting the lawfulness of previous processing.
Contact the controller below. We normally handle requests free of charge, without undue delay and within one month. Complex or numerous requests may require up to two additional months; we explain any extension and its reasons within the first month. If we have reasonable doubts, we request only information needed to verify your identity or control of the profile. You can complain to the Czech Office for Personal Data Protection or the competent supervisory authority where you live, work or believe an infringement occurred.
Controller and scope
Ondřej Zahumenský is the data controller for the operation of SliceIT and these public pages. Privacy and support contact: support.sliceit@gmail.com. This policy covers local play, accounts, backups, public leaderboards, Play Games services and optional heart purchases.
Security and local storage
Data is transmitted over HTTPS. Private cloud data is protected by account verification and owner-specific access; public leaderboards are intentionally accessible without sign-in. On-device data is in private app storage and Android cloud backup is disabled. Purchase tokens needed for server processing are encrypted.
The game stores a local profile, preferences and a sign-in session; it uses no advertising cookies or advertising SDK. These legal pages themselves add no analytics or marketing cookies. Providers' network and security processing and Play Games analytics are described above.
Policy changes
The current policy is available on this page and from the game's Settings. We update the policy and its date when features or processing change. We inform users about material changes before starting new processing through an appropriate in-app notice or email where available. If a new purpose requires consent, we request it separately; using the game alone is not consent to every processing purpose.