A sensitive questionnaire does not need a server-side answer store. For a recent browser project, I treated data minimization as a product requirement rather than a policy-page promise.
The result is Test Rice Purity, an independent adults-only implementation of the familiar 100-question checklist.
Core design choices
- Local state: checked items remain in the browser.
- Transparent scoring: the score is 100 minus the number of checked items.
- No account gate: users can complete the flow without creating a profile.
- Clear-data control: progress can be removed on shared devices.
- Safe result framing: the score is for entertainment and self-reflection, not a clinical or moral judgment.
Sharing without leaking answers
A share action should be explicit and should contain only the information the user chose to publish. The individual checklist answers are not needed for a result card or a friend challenge, so they should never be placed in an analytics event or a readable query string.
What this improves
Keeping the calculation local reduces the data surface, makes the privacy promise testable, and lets the interface be useful even without sign-in. It also forces clearer UX: users can see how their score works and can remove local progress at any time.
You can review the live implementation at Test Rice Purity. It is not affiliated with Rice University.
Top comments (0)