Profile inputs shape the framing
Gender, age range, and occupation help the story feel closer to real life. They do not replace the choices you make.
How PersonaPair works, what is stored, and how to read the result responsibly
This page explains how the assessment scores the story, which profile inputs shape the experience, what stays on your device, and what kind of conclusion the result should and should not carry.
How the assessment works
The result comes from the pattern across all 20 scenes rather than any single answer. Each choice carries a different weight so the system can read energy style, information style, decision style, and pacing without relying on direct self-description alone.
The result is a reflection tool
We want the result to be useful for self-understanding and conversation, not to behave like a rigid final label.
Saved results stay on this device for now
At the moment, saved results live in the browser on the device you used. They do not sync across devices until a real account system exists.
What is stored right now
Most of the assessment runs in the browser. Saved results are stored locally on your device, and product analytics capture basic events such as starting the assessment, completing it, opening key pages, and copying invite links so the experience can be improved over time.
How not to use this result
This result is best used for reflection, communication, and pattern awareness. It should not replace mental health evaluation, clinical judgment, or high-stakes screening decisions.
Common questions
Why only 20 questions?
Each scene is weighted differently and aims at a specific decision pattern, so the goal is depth through design rather than length alone.
Where are saved results stored right now?
At the moment, saved results stay in the browser on that device. Cross-device syncing will need a real account system.
Should this be used for high-stakes decisions?
No. It is better used for reflection and conversation, not as a clinical tool or a serious gatekeeping system.