Privacy Policy
What we collect
Your account (signed in): one antics account is used both to play and to make games. When you sign in with Google we receive your email address, whether Google has verified it, and the name on your Google profile (the full name, and your first and last name when Google sends them); if you sign in with an emailed link we receive the address you type. The name is for our records only — it is never shown to other players and never sent to a game. Your display name is generated, you can change it, and that is the only name other players see. We do not keep your Google picture. We store the projects, API keys, and deployments you create. Accounts made before September 2026 signed in with GitHub; for those we hold the GitHub id, login, display name and (if GitHub provided one) verified email we received then.
Players: players need no account. A game assigns a per-room player id and a display name (which you choose, default "Guest N"); these are tied to the room, not to a personal profile. Scores you submit are stored for the game's leaderboard.
Visit and play history: your browser holds a random guest identifier in local storage (no cookie), which we use to count visits, returns, games played and how long a game's page stays open in a room — kept for at most 90 days and then deleted. We also record the first page you landed on and the site that referred you (the site's domain only, never the full address). If you create an account, this history and first-visit record attach to it so we can understand how people find antics; deleting your account deletes them. None of this runs inside hosted games.
Operational data: we process IP addresses transiently for rate limiting and abuse prevention, and to derive an approximate country (used only as an aggregate count to plan server locations — the IP itself is not stored against it). We keep aggregate, non-identifying counters (page views, traffic source, country, rooms, concurrent players) for capacity, billing, and understanding usage. Our own counters are daily aggregate totals.
We use Google Analytics (client-side, via the standard gtag.js snippet) to
understand page traffic and which games are played: it sets first-party _ga cookies to recognize returning
browsers. We configure it analytics-only — ad storage, ad user data, and ad personalization
are all explicitly denied, and Google Signals is off. Our server additionally mirrors
selected product events (deploys, room lifecycle, sign-ins, plays and time played) to PostHog and
Google Analytics; these server events carry no browser identity, no IP, and no user agent —
pseudonymous, HMAC-derived identifiers only. PostHog is configured to build no per-person
profiles. There is no session recording anywhere.
Cookies
The only cookies on this origin are Google Analytics' _ga measurement cookies
(see above). Authentication never uses cookies — it uses a bearer token held in your
dashboard's local storage — and games you host or play cannot read analytics cookies from
their sandboxed frames. Hosted games remain served without any tracking injected into the
game itself.
Why we process it (legal basis)
To provide the service you asked for (performance of a contract), and for our legitimate interest in keeping it secure and abuse-free. We do not sell your data. Advertising in our mobile apps is described below; the website itself shows no ads. We give Google no account data of ours for mobile ads.
Who we share it with (sub-processors)
We use service providers strictly to run antics: Google (sign-in), Resend (sign-in emails), GitHub (only to confirm ownership of an account made with GitHub, when you ask us to recover it), MongoDB Atlas (database hosting), Amazon Web Services (server & file hosting), PostHog, and Google Analytics (privacy-preserving product analytics). They process data on our behalf under their own terms.
Our mobile apps (SIDE OUT on the App Store and Google Play, and the Antics app for Android, where Pro is bought) additionally use RevenueCat to process in-app purchases. RevenueCat receives a purchase record and an app-generated anonymous user id so it can tell the app what you have bought; it never receives your name or payment details. Your card is handled by Apple or Google under their own privacy policies — we never see it.
The mobile apps also use Google Firebase for two things, and it is worth being exact about which is which.
- Firebase Analytics — how the game is played, so we can fix what is broken and build more of what is played. Screens opened, matches started and finished, how long a round lasted, whether a room was joined or the join failed, frame rate and network latency, whether a purchase was started and whether it completed. It is tied to an app-instance identifier Firebase generates on your device, never to your name, your email or an advertising id. We do not send anything you type — not your display name, not a room code, not an invite link. Career totals and latency are sent as ranges (“10–49”, “under 100ms”), never as exact numbers, because an exact running total is itself a way to recognise a device.
- Firebase Crashlytics — what the app was doing when it crashed: the device model, OS and screen size, and the state of the match (phase, number of players, whether you were hosting). No behavioural profile, and again nothing you typed.
Your control over it. Options → Share usage data in the app turns analytics off, and turning it off also tells Firebase to delete the app-instance identifier everything collected so far is filed under. If you are in the EEA, the UK or Switzerland the switch starts OFF and nothing is collected unless you turn it on. Elsewhere it starts on and you can turn it off at any time. Crash reporting is not covered by that switch: a crash report says what broke, not how you play, and an app whose crashes cannot be diagnosed is its own problem for the people using it. Our legal basis for it is our legitimate interest in shipping a game that works.
Google processes this data on our behalf under the Firebase terms and its own privacy policy. We have not linked Firebase to Google Ads, Firebase collects no advertising identifier, and none of it is used to track you across other companies’ apps or websites.
Crews, chat and notifications in the Antics app
Crews. A crew is the people you played with, kept so you can find each other again. We store which crews your account is in, the name the crew knows you by and your colour, and each crew’s games and results. While the app is open we store whether you are online and which game you are playing, and we show that only to your crew-mates. You can turn it off on the You tab (“Show my crews when I’m playing”).
Chat. Crew and party chat messages are stored with the account that sent them, for up to 30 days and at most the newest 200 lines per crew, and are visible to the members of that crew or party (and, in a party, briefly on its television). Messages pass through a word filter. Any message can be reported, and any person blocked, from the message itself. We review reports and remove messages and mute or remove people who break the chat rules.
Notifications. If you allow notifications, the app gives us a push token for your phone, which we use only to send the notifications you can turn on and off in the app: a new game, a crew invite, and a crew-mate who is playing. We also store your phone’s time zone so the automatic one stays quiet at night. Notifications are optional.
All of this is deleted with your account.
Ads in SIDE OUT for iOS and Android
Starting with version 1.1, SIDE OUT for iOS and Android may show a Google AdMob banner at the bottom of the screen between rounds (the results board and the room lobby) and on the leaderboard. There is no ad on the home menu or while a round is being played. A one-time Remove Ads purchase removes the banner permanently; Restore Purchase restores it on the same Apple or Google account. The game waits for its purchase status and any required Google consent choice before requesting an ad.
For ad delivery and measurement, Google may receive your IP address (and approximate location inferred from it), device identifiers, ad views and interactions, crash information and performance data. We configure AdMob for non-personalized ads and disable its publisher first-party ID. Where required, Google presents a consent form before the first ad and offers an Ad privacy control in Options to change your choice. We do not give Google your SIDE OUT display name or room code. See Google's privacy policy for its processing details.
Ads in the Antics app
This applies from the version of the Antics app for Android that offers “Watch an ad for more matches”, and not to any earlier version, which shows no ads and contains no ads software. Nothing on the web (antics.gg) shows ads.
In that version, the app shows a rewarded ad from Google AdMob only when you choose “Watch an ad for more matches” after running out of free matches. The ads software starts only then, never before. When it runs, Google collects your device’s advertising ID, an approximate location from your IP address, how you interact with the ad, and diagnostics, and uses them to show and measure ads and to prevent fraud, under Google’s own privacy policy. If you are in the EEA, the UK or Switzerland, Google’s consent form appears before the first ad, and you can change your choice at any time from the app’s You tab (Ad privacy). We give Google no account id, name or email of ours: the reward is confirmed to us by Google directly, and we then add the match to your account.
Where & how long
Data is hosted in the United States, so if you are in the EEA your data is transferred outside it. For those transfers we rely on appropriate safeguards — our hosting providers (Amazon Web Services and MongoDB Atlas) offer Standard Contractual Clauses through their data-processing agreements.
Keyless rooms and their data expire (currently after 24 hours). Account data (projects, keys, leaderboards) is kept until you delete it or close your account.
Your rights
If you are in the EU/EEA (or a similar regime), you have the right to access, correct, delete, export, or object to the processing of your personal data. You can delete your account yourself from your account page (if you made games, delete them from your dashboard first), or email privacy@antics.gg: how deletion works. You may also complain to your local data-protection authority.
Requesting deletion of your data
This applies to antics (antics.gg) and to our apps, including SIDE OUT for Android and iOS, all published by AGE OTORI PTE. LTD.
How to ask. Email privacy@antics.gg with the subject "Data deletion request". Tell us the display name you played under and roughly when you last played, so we can find your rows — the apps have no accounts, so that is the only way we can identify what is yours. If you have an antics account, say which email it uses (or, for an account made before September 2026, which GitHub login) and we will use that instead. An account you can delete yourself in seconds, with no email to us at all: how deletion works. We will confirm within 30 days.
What we delete. Your leaderboard entries (display name, score, and the per-room player id attached to them), any projects, API keys and deployments on a signed-in account, your crew memberships, chat messages, push tokens and free matches, and our correspondence with you about the request. Deleting your account does not cancel a Pro subscription: cancel it in Google Play first.
What you can delete yourself, without asking us. Turning off Options → Share usage data in the app deletes the app-instance identifier that all of its analytics data is filed under, which unlinks that data from your device immediately and stops any more of it being collected. You do not need to email us for that one, and we cannot do it for you — the identifier only exists on your device.
What we keep, and why. Records of purchases made in our apps are kept for as long as tax and accounting law requires us to keep them; these sit with Apple, Google and RevenueCat as the processors of the transaction, and we cannot delete a store's own receipt. Aggregate counters (how many rooms opened, how many players were concurrent) are not personal data and are not linked to you; they stay. Room data expires on its own — keyless rooms and everything in them after 24 hours — and IP addresses are processed transiently for rate limiting and abuse prevention and are not stored against you.
Children
antics is not directed at children under 13, and we do not knowingly collect their personal data. Our apps are rated for players aged 13 and over.
Changes
We may update this policy; we'll change the "last updated" date above and, for material changes, give notice where appropriate.