A quiz about personal experiences creates a simple product question. How much of the answer data needs to reach a server?
For a single-session quiz, the useful answer can be none of it.
The current version of RicePurityTest.party stores progress in sessionStorage
. A refresh in the same tab can restore the current question and previous yes or no choices. Closing the tab clears that session. There is no account to create and no answer payload to sync.
The score calculation also stays in the browser. Each checked item subtracts one point from 100. That rule is visible in the site's methodology, so the result does not depend on a hidden model or personality inference.
The share flow needs its own privacy boundary. A result card can be useful without becoming a transcript. The card is drawn locally and contains the score, the number of checked items, a result label, an illustration, and the site name. It leaves out the individual questions.
This design has honest tradeoffs. There is no cross-device resume, no account history, and no way for the site operator to recover a lost session. Those limits are acceptable when the data is sensitive and the product promise is temporary, private use.
The reusable checklist is short.
The full privacy explanation states these boundaries in user-facing language. That page matters as much as the implementation. Privacy claims should describe the system people actually use.