Your tower. Very little data.

The game uses browser or app-private device storage to remember settings and local progress. This can include your best height, career totals, badges, earned Bricks, Daily state, cached Daily data, a curated builder alias (or a legacy local nickname), and named Playground builds: eight free slots, or 32 with Builder's Studio. Playground drafts and builds use a separate local save and are not uploaded as a gallery.

Your installation also creates a random player ID and a secret capability token for optional online features. They are not a conventional account and are not designed to identify you personally. Clearing all data from Settings also clears local Playground builds; clearing the app or site's storage may make the associated online identity unrecoverable.

Online features send only the information needed for the action you choose:

• Anonymous identity: the random player ID and capability token travel over HTTPS. The database stores a one-way SHA-256 hash of the token, not the token itself.
• Verified competition: canonical Classic and Daily submissions contain the game rules version, seed, and compact drop-tick replay. The Worker replays the run and derives its result.
• Friend challenges: creating a link stores a verified replay, its derived result, and a snapshot of the public nickname. Opening a challenge retrieves that public game record.
• Builder name: you may choose a name from our authored catalogue. That alias and a server-assigned public builder number are stored with your anonymous profile and shown publicly. The number distinguishes matching names; it is not a login credential. Free-text names from earlier versions are replaced with curated aliases in every public response; historical originals may remain in private legacy records.

Analytics request bodies never contain the player ID, capability token, nickname, challenge code, seed, replay ticks, or free-form text.

Leaderboard entries show only rank, nickname, verified height, perfect-placement count, and submission time. Public challenge links show the challenge code, nickname snapshot, derived result, and the replay needed to reproduce that challenge.

Public responses do not expose player IDs, capability credentials, private profile data, or another player's submission identifiers. Public names come only from our curated catalogue. The game has no chat, comments, or public uploads. Local Playground build names and exported images are not published to a One More Meter gallery.

The app sends a small allowlisted set of high-level product events, such as an app load, returning-day visit, run start or finish, restart, share, or verification outcome. Playground contributes only aggregate open, piece-drop, reset, and successful share/download counts; build names, shapes, coordinates, screenshots, and gallery contents are not sent. Exact competitive measurements are converted to broad ranges on the device. Events are combined in memory and sent in small, best-effort batches. A returning-day visit is decided locally and sent only as an aggregate counter; no player ID or visit date is included.

The Worker validates the same narrow format again and increments daily aggregate counters. It does not write raw analytics events, per-block taps or coordinates, session records, advertising identifiers, or cross-site profiles. Cloudflare Web Analytics also measures aggregate page visits and load performance on the custom domain. Cloudflare states that this performance beacon does not collect or use visitors' personal data or track individual users across customer sites. If analytics are blocked or unavailable, launch, play, saving, sharing, and restart continue normally.

The web app, API, database, and privacy-first Web Analytics beacon run on Cloudflare. Like any internet service, Cloudflare may process ordinary network and security information needed to deliver requests, measure page performance, prevent abuse, and operate its infrastructure under its own terms.

The app also sends limited technical diagnostics to help us fix errors. New clients classify errors on the device and send only a fixed error category, a fingerprint of that category, an allowlisted context, the platform, and the app version. They do not send exception messages, stack traces, player IDs, nicknames, saved builds, or capability tokens in these reports. The Worker also discards free-form messages and contexts from earlier clients before storing new reports. Diagnostic aggregates stored before this change may include a shortened error message with numbers and hexadecimal identifiers scrubbed. The Worker combines reports into daily error counts and retains these aggregates for 30 days.

On iPhone, Apple processes App Store delivery and any payment details. RevenueCat receives the random app user ID plus purchase and entitlement history to operate and restore the lifetime Architect Pack and Builder's Studio, and to provide purchase reporting in its dashboard. It does not receive gameplay replays or capability tokens. One More Meter does not add advertising trackers, analytics cookies, device fingerprinting, or third-party marketing scripts. Other records are retained while needed to operate the service, preserve verified competition, entitlements, and integrity.

You can play Classic without creating a conventional account. You can avoid public profile features, choose a curated builder alias, decline to share challenge links, block nonessential analytics requests, or clear the game's local storage. The iPhone store and Settings offer Restore Purchases for Architect Pack and Builder's Studio; restoration recovers those paid entitlements, not locally earned career history or saved builds.

Clearing storage does not automatically remove already-public verified leaderboard or challenge records, and without the original local capability there may be no way to prove control of an anonymous identity. Because there is no account-recovery channel, use online competitive features with that limitation in mind.

Your rights. You may ask support about deletion of your anonymous player record (player ID, nickname, and run receipts) by emailing support@playonemoremeter.com with your player ID. Support will explain the available verification and which service records can be removed. Never email your capability token. Public copies already distributed outside the service, such as screenshots or redistributed challenge pages, may remain beyond our control.