# Local scoring without collecting a response sheet *A project note from Rice Purity HQ* A web questionnaire does not always need a database of responses. Sometimes its entire job is to let one person make a set of choices, calculate a result, and decide whether to keep it. In that situation, collecting an identifiable answer sheet can add a privacy cost without helping the participant finish the task. ## Start with the task, not the form There are at least two different products that can look like a questionnaire. A survey gathers responses so that an organizer can analyze them. A private checklist gives a result back to the participant. If the organizer needs aggregate research data, local calculation alone will not satisfy that goal. If the participant only needs a personal total, uploading every answer may be unnecessary. Before choosing a form service, write down who needs to see the answers, whether they need to persist, and whether the result depends on a server. These questions are more useful than assuming that every checkbox must eventually become a database row. ## Separate the answer sheet from the result For a simple count, a browser can do the arithmetic directly. A 100-item checklist that subtracts one for each checked item needs only a count to produce a complete score. Twenty-four checked items produce 76. That total does not reveal which twenty-four boxes were checked: many different sheets produce the same number. Unknown answers deserve their own state. With twenty-four checked and ten unknown items, the possible score is 66–76. The interval describes uncertainty; it is not a prediction that the final score will be 71. Quietly converting a skip into “no” changes what the result claims to know. ## Local does not mean invisible everywhere Keeping answers in the browser reduces the need to send them to a scoring service. It does not make everything about a visit secret. A hosting provider can still receive normal page requests. A shared device can retain browser state. A copied result image can be forwarded. A link containing a summary can expose that summary to anyone who receives it. A useful privacy explanation distinguishes those paths. It should say where calculation happens, which storage is used, what a shared link contains, and which copies can remain after local answers are cleared. “No account required” answers only one of those questions. ## A concrete adult checklist example [Rice Purity HQ](https://ricepurityhq.com/) is an independent 100-question experience checklist for adults. Its interface distinguishes skipped or untouched items, calculates locally, and lets the participant choose whether to share a summary. The [privacy explanation](https://ricepurityhq.com/privacy/) describes the project's data flow, while the [scoring guide](https://ricepurityhq.com/rice-purity-score-meaning/) explains complete scores and incomplete ranges. The lesson is about designing the smallest data flow that completes a task. It is not a claim that a checklist is a scientific assessment, that any score measures character, or that a participant should disclose personal experiences. A good result screen can leave the person informed and in control, including the choice to close the page without sharing anything.