Privacy Policy
Said Too Much · Last updated 26 September 2026
This policy explains what Said Too Much collects, what it deliberately does not, and what other players can see. It covers the Android app, the iPhone and iPad app, and this website.
The two apps are the same game and are described together throughout. Where they genuinely differ, the difference is called out on the spot rather than left for you to work out — there are two such places below, in sections 2 and 9.
The app is made by James Loboda, an independent developer, who is the data controller for everything described here.
The short version.
There are no accounts. We never ask for your name, email or phone number. Your answers to prompts are counted anonymously and are never shown to anyone as yours. In Rooms, the only thing about you other people see is the display name you type and how you voted in aggregate — never who you individually picked.
1. No account, no sign-up
You do not create an account. When the app first needs to talk to our database it signs in anonymously with Firebase Authentication, which produces a random identifier for your installation. That identifier is not linked to your name, your email, your phone number or your Google account, and we cannot use it to identify you. It is reset if you reinstall the app.
2. What we store, and where
Our backend is Google Firebase. The Android app uses Realtime Database, Authentication, Cloud Functions, Remote Config, Analytics and Crashlytics.
The iPhone and iPad app uses less. It uses Realtime Database and Authentication — for Rooms — and Crashlytics, for crash and error reports. It does not include Firebase Analytics at all, so nothing in it reports how you use the app: which decks you open, which modes you play, how long you play for. The analytics rows below do not apply to it. The crash-report rows do.
What its crash reports contain: the crash or error itself, the device model and OS version, and a short label for what failed — for example that an advert did not load, or that restoring a past purchase failed. They are not linked to you, and they are used only to find and fix faults. We add no name, no email and no room code to them.
Here is everything the app sends:
| What | Why | Who can see it |
|---|---|---|
| Anonymous ID | So the database can tell one installation from another — for example, to make sure you only vote once on a prompt. | Us. It identifies an installation, not a person. |
| Prompt vote counts ("47% have") |
To show the community result after you answer. | Everyone, as a total only. Stored as two numbers per prompt. Your identity is not attached. |
| Your own answers (playing on your own) | So a prompt you have already answered is not counted twice. | Only you. Stored under your anonymous ID, readable only by that ID, and write-once. Just Us is different — see below. |
| Just Us: your ten answers | To show you both what you each said, once you have both finished. | The one other person in that set. This is the point of the feature: the answers are sealed until you have both finished, and then each of you can read the other’s. Nobody else can, and they are not attached to your other answers anywhere. |
| Just Us: the name you type | So the other person sees who they are playing with. | The one other person in that set. Optional — leave it blank and you appear as “Them”. Screened the same way a room name is. |
| Emoji reactions | To show which reaction a prompt gets most. | Everyone, as a total only. |
| Rooms: your display name | So the other players can tell who is who. | Other players in your room. If you host a room and list it publicly, also anyone browsing for a game. |
| Rooms: your seat, presence and whether you have answered | To run the round — to show who the room is still waiting on. | Other players in your room. It shows that you answered, never what. |
| Rooms: your pick | To count the result. | Nobody. See "the secret ballot" below. |
| Rooms: the result of a round | To show the room its own answer, and the running "most picked" board. | Players in that room. Totals per person, never who voted for whom. |
| Reports | So we can act on a prompt or a player somebody reported. | Only us. No player can read reports, including their own. |
| Analytics and crash reports | To see which features are used and to fix crashes. | Us, through Firebase, in aggregate. |
3. The secret ballot
In Rooms, when you tap a person, that individual pick is written where no other player's phone is permitted to read it — not the host's, not anyone's. When the round closes, the app publishes only the totals and deletes the individual picks in the same operation. The always-open lobbies go further: they are run by our server under an identity no phone can hold, so there is no player who could read a pick even in principle.
This is enforced by our database's security rules, not by the app being polite about it.
4. What stays on your device and is never sent
- Player names you type for pass-the-phone games. Prompts that use a name are personalised on your device; the version sent to us has the name stripped out. The one way a name leaves your phone is a poster card link that you choose to share — see Sharing.
- Decks you create yourself — their names and every prompt in them.
- Your streak, history, settings and which prompts you have seen.
- Players you have blocked. A block is your private preference and is not shared with anyone, including the person blocked.
5. How long things are kept
- Individual picks in a room: deleted the moment the round's result is published.
- A room: expires about four hours after it is created, and is swept automatically. A room a player hosts is removed when they close it.
- Always-open lobbies: results and seats are cleared whenever the lobby empties.
- Anonymous vote totals: kept indefinitely, because they are the community result the game shows. They contain no identity.
- Reports: kept while we need them to act on the problem.
6. Advertising
The app is free and shows ads through Google AdMob — full-screen, rewarded and in-feed ads. We do not show banner ads and there is nothing to buy.
Google may use a device advertising identifier to show and measure ads. The ads SDK also sends the app set ID and your device's IP address with every ad request, and Google may use that IP address to estimate the general area you are in — roughly city level — to choose which ads to show. Alongside these it reports which screens were opened, taps and video views, and technical measurements such as how long the app took to start. None of this is sent by code we wrote: it is what the advertising SDK does on every request, and we are telling you because it is ours to declare. In the European Economic Area, the UK and Switzerland you are asked for consent before any personalised advertising, and you can change that choice at any time from the app's settings. Google's own handling of advertising data is described in the Google privacy policy.
6a. Notifications
If you allow notifications, Firebase Cloud Messaging gives this installation a registration token so a message can reach it. The token identifies the installation, not you, and it changes if you reinstall. Turn notifications off, or uninstall, and it stops being useful. We do not use it to build a profile and we do not share it outside Google.
7. Children
Said Too Much is made for adults and is not directed at children. Because of the content it shows, it is for people aged 17 and over, on any platform. We do not knowingly collect information from anyone younger, and we do not use the app's data to build profiles of, or advertise to, children. Some decks are marked 17+ and sit behind an age confirmation.
If you believe a child has provided us with information, contact us and we will delete it.
8. Sharing
We do not sell your personal information, and we do not share it for cross-context behavioural advertising. We share it only with the service providers that make the app work — principally Google (Firebase and AdMob). We may disclose information if the law requires it, or to investigate a report or protect people from harm.
Data is processed on Google's servers, which may be outside your country.
Poster cards. When you share the recap poster after a game with named players, it
carries a link that lets each player open a card of their own night. The link holds each player's
first name as typed, how many times they said “I have”, how many turns they had, and the
award they won, if any — never a question and never an answer. All of it sits
after the # in the link, which browsers do not send to any server, so we never receive
it. Anyone you send the link to can read it, the same as the poster itself. The card page is hidden
from search engines and collects nothing.
9. Your choices and rights
- Leave a room and your seat and name are removed from it.
- Uninstall the app and everything held only on your device goes with it.
- Reset your advertising ID or opt out of personalised ads. On Android: Settings › Privacy › Ads. On iPhone or iPad: Settings › Privacy & Security › Tracking turns off app tracking requests entirely, and Settings › Privacy & Security › Apple Advertising turns off Apple's own personalised ads. On either, you can change your consent from inside the app's settings.
- On iPhone and iPad, the app must ask before it can track you. Apple requires a separate permission prompt (App Tracking Transparency) on top of the consent screen. Saying no is free: you still get the whole game, and the ads simply become less relevant. If you have already answered, you can change it in Settings › Privacy & Security › Tracking.
- Depending on where you live, you may have rights to access, correct or delete information about you. Because there is no account, the practical way to exercise these is to contact us — and to be able to identify the data, we will usually need the room code and the approximate time. How to request deletion sets out the steps, and exactly what is deleted and what is kept.
10. Security
Traffic is encrypted in transit. Access to our database is governed by security rules that are tested automatically against both our own copy and the live service, and which enforce the guarantees described above — in particular that no player can read another player's pick.
11. Changes
We will update this page when the app changes what it collects, and change the date at the top.
12. Contact
James Loboda — android.personal.support@gmail.com