Fourfold Android Privacy Policy
Last updated: October 28, 2026
Fourfold is developed and published by nicki.
This Privacy Policy explains local play, optional online leaderboards, banner advertising and the Remove Ads purchase in Fourfold 1.2.0 for Android. Earlier offline-only versions do not gain online features merely because this policy is updated.
Information Fourfold Collects
Leaderboard participation is optional and requires your explicit consent in Fourfold. You can play without joining, and browse public rankings without creating a guest profile.
If you join, your chosen nickname, eligible Normal Mode scores, platform, rings, level and qualification date can appear publicly. The qualification date is when the server first received the run. Use a nickname that does not reveal your real name or contact details.
Fourfold uses a randomly generated guest identity for each installation or browser storage context, not a conventional account with an email address and password. A secret credential is stored locally and sent over HTTPS to authenticate guest requests; the server stores a hash of that credential. Credentials are not shown in public rankings.
With consent, eligible new runs, or a completed run you explicitly choose to share, can be queued and uploaded automatically. Submissions include a run identifier, score, rings, level, piece-lock count, active duration, platform, build and ruleset identifiers, completion time and eligibility flags. The service also stores guest/profile information, consent version, receipt times and validation status to operate rankings and handle retries and abuse. It does not receive a full replay of your inputs.
The leaderboard feature does not request access to location, camera, microphone, contacts or external storage. It does not require an email address, a purchase or an advertising identifier.
Information Stored on Your Device
Fourfold stores game settings and preferences, high scores and records, lifetime gameplay statistics, tutorial completion and other game configuration locally. These saves are not automatically cloud-synchronized. Joining leaderboards does not upload historical local high scores.
Android leaderboard credentials use app-private, Android Keystore-backed encrypted storage. Browser guests use browser-local storage. Each installation/browser context is separate.
Data Sharing
The leaderboard API and databases run on Cloudflare Workers and D1. Cloudflare processes requests, stored leaderboard data and technical information such as IP addresses to deliver and protect the service. IP-based rate limiting helps prevent abuse. Our application logs contain request identifiers, routes, status and timing, not guest secrets or full score payloads.
Public ranking fields can be read by anyone. Cloudflare and Google may process information outside Quebec or Canada. See Cloudflare’s Privacy Policy.
Banner advertising and consent. Fourfold uses Google AdMob to show banners during eligible gameplay when Remove Ads is not owned. Google Mobile Ads can collect and share network information, including an IP address used to infer approximate location; Android advertising IDs, app set IDs and other applicable device identifiers; ad and app interactions; and diagnostic information about the app and SDK. Google uses this information for advertising, analytics and fraud prevention. Banner requests are configured as non-personalized, which does not mean that no information is collected.
Fourfold refreshes consent information at app launch using Google’s User Messaging Platform (UMP). Where required, UMP presents privacy messages and records your choices. Banner requests wait until UMP permits them. You can reopen Ad Privacy Options in Settings when this entry is required and available. Consent choices, including any regional restrictions on data use, are separate from joining leaderboards. See Google’s Privacy Policy.
Google Play purchases. Remove Ads is an optional, permanent one-time purchase associated with the Google Play account used to buy it. Fourfold checks ownership through Google Play, verifies purchase receipts and acknowledges completed purchases. Unresolved payments do not grant ownership. Verified ownership suppresses banner requests and removes an existing banner. Google Play handles payment details; Fourfold does not receive your payment-card number. Restoring purchases and recognizing refunds or revoked ownership depend on successful Google Play checks. Removing ads does not stop the purchase reporting described below or erase information already processed by service providers.
Unity IAP purchase-event reporting. Fourfold 1.2.0 integrates Unity IAP 5.4.4 with Google Play Billing. In addition to the Google Play payment flow, Unity IAP sends purchase-attempt and outcome events to Unity. Reporting can include purchase history, product and transaction information, price and currency, purchase receipt information, installation and session identifiers where available, app and SDK versions, and device or diagnostic metadata such as device model, operating system and language. Unity uses this information to provide purchasing functionality and analytics. This reporting is separate from optional leaderboard participation and Google’s UMP consent choices. See Unity’s Privacy Policy.
Fourfold’s custom guest leaderboard identity is separate from the Google Play account used for payments. A purchase does not create, recover or link a leaderboard guest. Fourfold does not use Google Play Games authentication or leaderboards. Google, Unity and Cloudflare may process information outside Quebec or Canada.
Data Retention and Deletion
Local game data remains until you reset it or remove app data. Reset All Data, uninstalling or clearing app/site data is not a request to delete an online guest.
In Participation & Privacy, Stop Participation stops future uploads and clears pending scores. It does not remove scores already received by the service. Delete Online Guest requests removal of that guest profile and its scores; keep the local app/browser data until deletion is confirmed so the request can be retried if offline or interrupted. These online actions do not reset your local game records.
If you saved a confirmed deletion-only backup before uninstalling or losing the original installation, you can request deletion of that online guest on our website: Delete online guest.
The backup contains the guest ID, service and deletion code. It authorizes deletion only, not login, guest transfer or account recovery. Anyone possessing it can authorize deletion of that guest. Never send your gameplay authentication secret. The service stores a hash of the deletion code, not the code itself.
The backup must show Registration: confirmed. Registration: pending is not confirmation: keep the proposed backup and retry registration with the same code in the original installation before uninstalling or clearing its data. The website cannot confirm issuance or register a replacement after that installation is lost.
If a deletion request is interrupted, times out or returns a temporary error, its outcome is uncertain. Keep your saved backup and explicitly retry with the same credentials. Only confirmation from the service confirms completion. A completed deletion can be confirmed again within the existing 90-day receipt window, measured from the original deletion; retries do not restart it. An invalid-credential response or expired replay authorization does not prove whether an earlier request completed.
The deletion page holds the pasted backup temporarily in the page and sends it directly to the leaderboard service over HTTPS. It does not save it in browser storage or include it in URLs, analytics or application logs. Confirmed deletion, explicit cancellation, leaving the page or changing language clears the entry; keep your own saved copy for retries. This cannot protect against malicious extensions, clipboard history or a compromised device.
Creating a deletion-only backup requires a game build that offers this feature. Fourfold Web 1.1.0 lets confirmed online guests create, reveal, copy and export a deletion-only backup. Export and securely retain a backup marked Registration: confirmed outside your browser; it can be used with the self-service deletion page linked above. Older versions and the isolated test build may not offer these features. Use in-game deletion while the original local credentials remain available. Clearing site data, private browsing or storage eviction can remove local credentials, backups and saves; this page cannot recover them. Website deletion does not erase local records or other independently created guests.
Losing local credentials, including by uninstalling or clearing app/site data, can leave an online guest and its scores in place while removing your ability to manage or delete them through the game. There is no automatic credential recovery, guest transfer or cross-platform linking. A previously saved confirmed deletion-only backup can still authorize website deletion of that guest. Without the local gameplay credentials or that backup, contact us about privacy concerns; we cannot promise recovery or deletion without authorization. An email address, public nickname or score screenshot alone is not proof of ownership.
Online guest profiles and submitted runs, including held or rejected submissions, have no automatic inactivity expiry and remain while the guest exists. Moderation can hide a result without deleting its stored submission. Pending local score uploads expire after 30 days; pending deletion requests do not expire automatically. Public ranking updates may take up to 60 seconds to appear.
Limited deletion records retain guest identifiers, credential hashes and deletion/protection dates to authenticate retries and prevent deleted guests from returning after database recovery. Retry receipts expire after 90 days. Independent protection records remain at least 31 days after confirmed completion and may remain longer while deletion or recovery is unfinished; scheduled cleanup removes them when eligible. They do not contain nicknames or score payloads.
Deleting a guest does not instantly erase Cloudflare recovery history or provider security records. Recovery history is subject to Cloudflare retention; deletion protection is used before recovered data is returned to service.
Deleting an online guest or resetting local game data does not delete your Google Play account, purchase history or information held independently by Google or Unity, and does not request a refund. Google and Unity apply their own retention and privacy-request processes to information they handle, including records needed for purchasing, security and legal obligations. Contact the relevant provider about those records using its privacy policy. We do not promise a fixed retention period or immediate deletion of provider-held information.
Security
Leaderboard requests use HTTPS. Keep local credentials private and keep app/browser data until any pending deletion is confirmed. No method of storage or transmission can be guaranteed completely secure.
Children's Privacy
Nicknames and results shared with leaderboards are public. Avoid including a child’s real name or contact information. Parents or guardians with questions or concerns about a child’s information can contact us below.
Changes to This Privacy Policy
We may update this policy as Fourfold develops or its services change. The date above identifies the latest update.
Contact
For questions about this Privacy Policy or Fourfold’s privacy practices, including requests concerning online guest data, contact:
Developer: nicki
App: Fourfold
Email: [email protected]