No Accounts, No Sign-Up: Designing Privacy for a Play Page
There is a category of privacy policy that says nothing useful because it cannot say anything useful. The site embeds somebody else's game, the game sets its own cookies, and the page itself is a thin wrapper. A lot of p
There is a category of privacy policy that says nothing useful because it cannot say anything useful. The site embeds somebody else's game, the game sets its own cookies, and the page itself is a thin wrapper. A lot of policies in that position either hide behind the embedded service or read like a legal template.
What the site collects itself
The alternative is to name every thing that happens, including the part you do not control, and to say plainly where the line sits. On this one the split is straightforward and it is worth copying. The full list, the embedded-frame disclosure and the reader's actual choices are on the daily orbs privacy page.
- Aggregate visit statistics — page views and unique visitors, counted to see which pages get used, not to build a profile of any individual.
- Comments, when you post one: your chosen display name, the message, which page it was on, and the time, so that other visitors can read the thread.
- Messages you send, kept so that a reply can be written.
- No email address is requested in order to play, and no data is sold.
- Comments are loaded separately from the page and are not part of the content that search engines index.
The part you do not control, named honestly
Comments are the interesting case. They are stored so the thread can be read, but they are loaded separately from the page and are not part of the page content that search engines index. That single design decision is the difference between a comment box and a spam surface, and it costs nothing to implement: the render path and the index path are different.
Opening the homepage automatically connects the browser to the developer's domain to load the game, before a puzzle is even chosen. The publisher and the advertising and analytics services it uses may set cookies or other identifiers, and the publisher may record the moves you make. The policy says so, and points at the publisher's own policy for the detail instead of paraphrasing it badly.
Two practical consequences are spelled out as well. Clearing site data can remove locally saved game progress, and blocking browser storage may affect game features — so a reader who is privacy-conscious should know that blocking storage is a trade, not a free win. The same page also notes that the site is general-audience and not directed at children under thirteen.
Originally published by Dev.to WebDev. Aggregated on AIWithGhost for educational purposes — full credit and traffic to the original publisher.