Reviewed 2026-07-18
Methodology & Privacy
How this site calculates a score, what stays in your browser, what the result cannot tell you, and which sources support its history pages.
Scoring formula
The test contains 100 equally weighted questions. The score is arithmetic, not a psychological model:
Score = 100 - number of checked experiences
A score of 77 therefore means 23 boxes were checked. The total does not reveal which 23 were checked, and two people can receive the same score from entirely different answers.
Question-set review
The site's 100-question implementation was reviewed on 2026-07-18. That date records this site's editorial review; it is not a claim that the wording is the one official or original version.
Questions include adult sexual, substance, and legal topics. The test is intended for adults aged 18 and over. A person may leave any item unchecked or exit the test, but an unchecked item is scored the same whether the experience did not occur or the person preferred not to answer.
What the quiz stores locally
The interactive quiz stores a small record in your browser's local storage under rice-purity-test-answers. The record contains a format version, checked numeric question IDs, the current section, completion state, and an update time so the browser can restore progress after a reload.
The quiz code does not submit those IDs or answer values to this site's server. The delete control removes the saved record. Choosing “Delete and start again” removes the previous record and creates a blank one for the new session. You can also remove all saved state by clearing site data for this domain in your browser.
Normal web infrastructure can still receive routine request metadata such as the requested URL, time, IP address, and browser user agent. Those requests do not need the checked-question list to serve the quiz, and the quiz does not add that list to request URLs or payloads.
Sharing and downloads
The result image is drawn locally in the browser. It contains the final score, checked and unchecked counts, a neutral descriptive band, the question-set review date, and the site URL—not the selected questions. Downloading creates a local image file; native sharing or copying a link happens only after you choose that action.
A score is still personal information in context. Share it only when you want to, and do not pressure another person to reveal a score or individual answers.
Privacy-safe funnel events
The quiz emits named browser events for funnel measurement. If Cloudflare Zaraz is configured on production, the same name is passed to zaraz.track. The call contains no custom properties—never question IDs, answers, categories, checked counts, or a score.
Allowed event names cover start, first selection, 25%, 50%, and 75% progress, completion, reset, resume, result review, copy, share, and download. The quiz still works when no analytics provider is present. Standard web infrastructure may process normal request metadata as described above.
Interpretation limits
The result is a count of checked items from one checklist. It does not diagnose personality, maturity, health, risk, morality, relationship compatibility, or a person's history beyond the answers they chose to mark.
This site does not maintain a documented population dataset of scores. It therefore does not publish a universal average, demographic comparison, or percentile. Descriptive score bands are navigation aids, not estimates of where a person ranks against other test takers.
For more detail, read why online average claims need evidence and the scoring guide.
Historical sources and independence
This is an independent implementation. It is not operated by, endorsed by, or affiliated with Rice University.
- Rice University archives: “Purity Test, 1990s” An archival catalogue record establishing a Rice-associated purity-test item in the 1990s.
- Rice Thresher: “Purity Test evolves, spreads beyond Rice” Rice-affiliated reporting used for the account of the test's evolution and spread.
Corrections policy
Factual corrections should identify the affected page, the claim in question, and a source that supports the proposed change. Submit a request through the project's issue tracker.
Material corrections are checked against the strongest available source, applied to every affected page and structured-data field, and recorded with a new review date.