Privacy policy
Last updated: 14 August 2026
One Table is a game. This policy describes what it keeps, where, and for how long. It is written from the app's actual storage and the server's actual database schema, not from a template.
The short version
- You do not make an account with an email address, a phone number or a password. Playing online creates a guest account identified by a random code.
- There is no advertising, no analytics and no tracking. The app makes no network request to anyone except the One Table service.
- Playing offline against the bots sends nothing anywhere. Everything stays on your device.
- You can delete your account and everything attached to it from inside the app.
What stays on your device
Whether or not you ever play online, One Table keeps a small file in the app's own private storage:
- Coins and gems, which cosmetics you own and which you have equipped
- Your display name and chosen avatar
- Each game's table setup, any match in progress, and your last fifty results
- Your settings
Uninstalling the app deletes it. It is never uploaded.
Your online access tokens are kept separately, in the Android Keystore or the iOS Keychain, not in that file.
What the service keeps, if you play online
Creating a guest account stores:
| What | Why |
|---|---|
| A random account id and a shareable player code | So a friend can add you |
| Your display name, avatar and nameplate choice | So friends can recognise you at a table |
| When the account was created and last seen | To show friends whether you are online |
| Session tokens, stored only as SHA-256 hashes | To keep you signed in without storing anything reusable if the database leaked |
| Your friends, friend requests and blocks | To show your friends list |
| Rooms you join and matches you play | To run the match and let you reconnect to it |
| Match results and ladder ratings | To score the season |
| Reports you file about another player | To act on abuse |
That is the whole list.
What the service does not keep
- No email address, phone number, real name or date of birth
- No password
- No contacts, photos, camera, microphone or location — the app never asks for these permissions
- No advertising identifier, and no device fingerprint
- No payment details. In-app cash purchases are not enabled in this version and the app cannot charge you
- No IP address is written to the database. Addresses are used only in memory, briefly, to rate-limit abuse
Who it is shared with
Nobody. There is no third-party analytics, advertising, crash-reporting or attribution SDK in this app, and no data broker.
Other players can see only what you would expect them to: your display name, your avatar, your player code if you give it to them, whether you are online, and how you played in a match you were both in.
The service runs on Google Cloud Platform, which stores the data on our behalf as our infrastructure provider.
Children
One Table has no age gate and collects no age. Because a display name is visible to other players, it can carry personal information if a child types it in — the app filters names, but no filter is perfect. There is no chat, no voice and no free-text messaging anywhere in the app, which removes the usual route for that. Reactions at the table are a fixed set of stickers.
If you believe a child has entered personal information as their display name, contact us and we will remove it.
Your choices
- Change your name or avatar at any time from the profile screen.
- Delete your account from More → Safety & privacy. This erases the account, its display name, friendships, requests, blocks, sessions, rooms and ratings. Reports you filed about other players are kept without you attached to them, because deleting your own account should not erase someone else's abuse record.
- Start over locally from the same screen, which resets the on-device profile.
- Block a player to stop them contacting you or being matched with you.
- Uninstalling removes everything on the device.
How long it is kept
Your account and its data are kept until you delete it. Sessions expire on their own: access tokens after 15 minutes, refresh tokens after 30 days. Finished matches are kept so that ratings can be audited for a season.
Security
Traffic is HTTPS/WSS only; the app refuses to send anything over an unencrypted connection in a release build. Session tokens are stored hashed on the server and in the platform keystore on your device. Authorization headers, refresh tokens and match state are never written to logs.
Changes
If this policy changes materially, the date at the top changes and the new version is published here before the change takes effect.