This site is meant to feel private and low-pressure. We aim to collect as little personal information as possible and be clear about what is stored and why.
The experience does not require account creation before someone can begin the test. That means the site avoids asking for names, contact details, or other personally identifying information unless a future feature genuinely requires it.
If a future feature does require user-submitted data, the purpose will be clearly explained before collection begins.
The site may use basic analytics to understand whether pages load, whether people begin the flow, whether they finish it, and which pages are being used. The purpose is product improvement, not identity profiling.
Operational data is limited to what is needed for performance, stability, and understanding aggregate behavior.
Where possible, progress and result transitions stay lightweight. If state is stored client-side, it is treated as part of the user experience rather than as a long-term personal record.
If server-side storage is introduced later, this policy will be updated to explain what is retained, for how long, and for what purpose.
The site may rely on infrastructure or analytics providers to host pages, deliver assets, or understand traffic. Those providers may process technical request data as part of normal website delivery.
If additional third-party tools are added later, this page will be updated so the list stays current.
No. Entry is designed to stay private and low-friction.
It may use basic analytics to understand traffic and product behavior at an aggregate level.
No. It will be updated whenever storage, analytics, or data handling practices materially change.
Keep the same calm tone while moving into the next step that matches your pace.
If you want the practical limitations and expectations in one place, the terms page is the next stop.