DISCIPLINE. Privacy Policy
Published by Nomogames · Effective 2026-08-24
This policy explains how DISCIPLINE. handles information when you use the game and its account service.
Information processed
- Account information: your chosen username, a salted password hash, an internal account identifier, and hashed session tokens. DISCIPLINE. does not request an email address, legal name, or payment-card number when creating a game account.
- Abuse-prevention metadata: for account registration and referral claims, the account service receives the network source IP supplied by Cloudflare and immediately converts it, and the relevant account/referral scope, into separate keyed HMAC fingerprints. D1 stores only the scope, pseudonymous fingerprint, fixed-window request count, and window start; it does not store the raw IP or raw referral code in this throttle table. These rows limit automated account creation and protect Google verification quota without globally limiting a public invite code.
- Game and app activity: cloud-save progress, settings stored in the save, inventory, purchases granted to the account, and a client-submitted cumulative tap total used for leaderboards. The account service accepts increases only within a server-side plausibility ceiling of 25 taps per second plus a small synchronization allowance; it does not independently verify each physical tap.
- Community safety: the accepted Terms version and time, private hide relationships, submitted report reasons and explanations, report status, and moderator notes.
- Purchase history: product identifiers, platform transaction identifiers, purchase-token hashes, quantity, verification and consumption/delivery state, granted currency amounts, billing region, exact paid amount and currency when the store provides it, standard/test/promo/rewarded purchase classification, financial/order status, and refund/void evidence. These records verify purchases, reconcile refunds, calculate account spending without treating test, promo, or rewarded transactions as real spending, and prevent duplicate grants. Google Play or Apple processes the payment itself.
- Advertising and diagnostics: Google Mobile Ads may process IP-derived approximate location, app interactions, diagnostic/performance information, advertising data, and device or account identifiers for advertising, analytics, and fraud prevention. The account service records signed rewarded-ad transaction identifiers and reward types to prevent duplicate or spoofed grants.
- Friend referrals: on Android, the app reads the referral code, referral-click time, install time, and installed app version supplied through Google Play Install Referrer. It also requests a Google Play Integrity token cryptographically bound to that exact referral claim. The account service verifies the token with Google before accepting the claim, then uses the evidence solely to prevent self-referrals or duplicate claims, count up to ten rewarded referrals, and grant the referrer one random unowned shop item for each rewarded referral. The social account and reward system is platform-neutral; an iOS claim remains disabled until a separately reviewed, server-verifiable Apple proof adapter is added.
- Friends and multiplayer: the account service stores a random public friend code, friend requests and accepted friendships, PvP invitations, selected mode and duration, server-controlled round timing, client-submitted and server-recorded plausibility-limited tap totals (not verified physical taps), Quick Draw raw server-receipt reaction times, bounded RTT telemetry and submission transport, match results, and eligible five-Mentality winner rewards. At most ten wins per winner and one result per unordered player pair can be rewarded in a rolling 24-hour window, so a completed win may award zero. Platform gaming accounts are not required for this friend graph, so a DISCIPLINE. friendship can work across supported platforms.
How information is used
Information is used to authenticate accounts, rate-limit automated registration and referral-proof abuse, synchronize progress across devices, restore verified purchases, operate leaderboards, validate friend referrals, connect requested friends, run and settle PvP matches, grant eligible winner rewards, review reports, enforce moderation decisions, prevent fraud and duplicate grants, provide rewarded and interstitial ads, diagnose failures, and maintain the game.
Public leaderboard, friends, and community safety
Your chosen username and client-submitted cumulative tap total accepted under the server-side plausibility ceiling are visible to other players on the public leaderboard after you accept the current Terms. This score is not an independently verified count of physical touches. Your username and friend code are also visible to players with whom you exchange a friend request, and your PvP opponent sees the mode, round state, score or reaction result, and outcome of your shared match. Other signed-in players can report a username or score and can hide an account from their own leaderboard. Reports, their selected reason, and any optional explanation are stored for operator review. Hiding is private and is not shown to the hidden player.
Sharing and service providers
Account and gameplay data is processed by the DISCIPLINE. account service and its infrastructure provider. Purchase verification and Android install-referral attribution use Google Play; purchase verification may also use Apple. Rewarded and interstitial advertising uses Google Mobile Ads. Public leaderboard viewers receive public usernames, client-submitted plausibility-limited cumulative tap totals, and ranks. Advertising and platform providers process data under their own terms and available privacy controls.
Security
The production app is intended to use encrypted network connections. Passwords are stored as salted PBKDF2 hashes; session and purchase tokens are stored as hashes where supported. These measures reduce risk, but no system can guarantee absolute security. Production encryption must be verified against the exact release build and deployed endpoints before publication.
Retention
Primary DISCIPLINE. account data remains while the account exists. Account deletion removes the username, Terms/profile state, cloud save, leaderboard score, referral code and personal referral attribution involving the deleted account, friend code, friendships, PvP matches and round submissions involving the account, that account's PvP reward ledger, reports involving the account, private hide relationships, sessions, rewarded-ad ledger, and DISCIPLINE. purchase ledger from the primary account database. A keyed HMAC fingerprint of one-use install evidence remains to prevent the same evidence being claimed by another account; it does not retain the referral code or install timestamps. A referral reward already earned by another player also remains in that player's lifetime reward ledger, without retaining the deleted referred account's identifier. Pseudonymous rate-limit fingerprints and their counts are pruned by an hourly task once their window start is more than 24 hours old, so normal retention is less than 25 hours; they are not a permanent account record.
A successful account deletion removes account-linked records from the live D1 database, and the application does not create a separate archive. Cloudflare D1 Time Travel may retain recoverable database history for 7 days on the Free plan or 30 days on a Paid plan. Workers Logs, if enabled, are retained for 3 days on Free or 7 days on Paid. Cloudflare may also retain limited security or network data under its own privacy policy and legal obligations.
Your choices and deletion
You can revisit advertising privacy choices from Settings. A signed-in player can choose Settings > Delete account. You may also use the web account-deletion page if the app is no longer installed. Account deletion removes that account's referral code and personal referral attribution, friend code, friendships, PvP matches and round submissions, and its own PvP and referral reward ledgers from the primary database. It does not revoke a referral reward already earned by another player: a keyed HMAC fingerprint of the one-use evidence and that other player's reward/count entry remain, with the referral code, install timestamps, and deleted referred account identifier erased. It cannot remotely erase a local save that remains on another installed device; clear the app's local storage or remove the app on that device to remove its local copy. Platform transaction, install-referral, or advertising records controlled by Google or Apple are not deleted by deleting a DISCIPLINE. account.
Age eligibility and target audience
DISCIPLINE. is intended for players age 13 and older and is not directed to children under 13. The game does not ask for a birth date or independently verify age. Players under 13 should not create a DISCIPLINE. account or use its online community features. A parent or guardian who believes a child under 13 created an account may use the account-deletion page or contact the privacy address below.
Contact
For privacy, support, or moderation questions, email co.nosiah@gmail.com.