Privacy Policy

Last updated: September 2026

1. What we collect

Most of what we hold is created by using the product rather than given to us on a form. The categories below are the whole list.

• A browser identifier — A random value stored in a cookie named dg_guest. It is how we recognise that the person opening a Game is the person who made it. It is not linked to a name, an email address or a phone number.
• A display name, if you type one — Shown on your result and on the Game's board. It is optional: leave it blank and you play anonymously.
• The Games you create — Their name, their questions, the answer options and the answer you marked as yours.
• The Games you play — Which option you picked for each question, when you started, when you finished, and the score that came out.
• Ordinary request data — The IP address and browser user-agent every web server sees, used for rate limiting and abuse investigation.

2. Playing and creating without an account

You do not need an account to create a Game or to play one. When you have no account, the dg_guest cookie is the only thing that connects you to what you made — which is also why clearing it, or opening the site in a different browser, means we can no longer tell that a Game is yours.

A guest identity is personal data from the moment it exists, and it is covered by every right described below.

3. Account data

Accounts are not part of this version of the product. When they arrive, this section will describe exactly what an account row holds and this notice will be replaced rather than quietly deleted.

4. Game data

A published Game is reachable by anyone holding its link. Its name and its questions are visible to every player you send it to, so treat them as public. Do not put anything in a question that you would not want a stranger to read.

Once the first other person starts playing, a Game is locked and its questions and answers can no longer change. That is a fairness rule, and it means a Game cannot be edited after the fact — it can only be taken offline or deleted.

5. Player responses

We record which option a player picked, and nothing about why. A response is stored raw: no verdict, no score and no judgement is written next to it. The score you see is computed from those raw answers when the result is produced.

The creator of a Game can see the display names and scores of the people who played it. They cannot see anything else about them.

6. Analytics

We measure how the product is used — how many Games get created, how many get finished, where people stop — in aggregate. Analytics is not used to build a profile of an individual visitor.

7. Advertising

Advertising is the only way this product is paid for. Ads may be served by third-party networks which set their own cookies and may personalise what they show. The controls for that are in the Cookie Policy.

8. Rewarded advertising

Some limits — how many questions you may re-roll, how many Games you may publish — can be raised by watching a short ad. Watching one records that a reward was granted and claimed. It does not record anything about the ad you watched.

9. Cookies and similar technologies

Two cookies are set without asking: dg_guest, described above, and dg_lang, which remembers the language you picked with the switcher and is written only when you use it. Everything else — analytics, advertising — is described in the Cookie Policy, which is a separate document because it is the one people come looking for.

10. Third-party services

We use third parties for hosting, for analytics and for advertising. Each is a separate controller of whatever it collects, and this section will name them individually before launch.

11. Where data is stored

In one database, in one region, named here before launch. Wherever it is, the protections described in this document travel with the data.

12. How long we keep it

A guest identity that never created a Game and never finished a play is erased automatically after a period of inactivity. That period is a setting an administrator can change, and shortening it takes effect on the next sweep.

Everything else is kept until you ask for it to be erased, or until it stops being needed for the purpose it was collected for.

13. Deleting your data

You can erase everything held against your identity yourself, from this browser, without writing to anybody. The control is on the Delete my data page and it asks you to confirm in words before it runs.

What erasure does, precisely: your Games are taken offline and their management links stop working; the display name on every play you made is removed; the browser identifier is replaced with a value that resolves to nobody. The score of a game somebody else played survives, without your name on it — deleting it would delete their result too, and that is their data, not yours.

14. Your rights

You may ask for a copy of everything held against your identity, and you may have it erased. Both are self-service and neither requires you to prove who you are, because the cookie in your browser is the only identity there is.

15. Security

Every credential this product issues — the browser identifier, a Game's management link, a play token — is stored only as a hash. A copy of the database is therefore not a set of working keys.

16. Contact

Questions about this policy go to [email protected].