1. Who is responsible
The production data controller, its location, and support email are shown in the operating information on this page. If any item is marked as not configured, the site is not ready for production launch.
2. Data we process
- Test data: locale, quiz and scoring versions, option IDs, dimension scores, archetype, level, result evidence, and result feedback.
- Account data: email, verification state, sign-in method, and session data handled by the authentication service; the app keeps the necessary user ID and locale preference.
- Purchases and reports: order state, amount, currency, Stripe identifiers, report status, structured report, and training progress. We do not store full card numbers.
- Challenges and sharing: the public nickname you choose, challenge state, and hashes of unguessable share or management credentials.
- Operations and security: internal IDs, status codes, error categories, provider request IDs, and an IP hash made with a daily rotating salt. Raw IP addresses are not stored as product analytics fields.
- First-party product events: route, locale, device class, duration, and permitted state fields. Events exclude email, nickname, complete answers, report text, and Stripe IDs.
3. Data we do not ask for
The test does not ask for real trauma, precise location, a child's name or school, identity documents, or medical information. Do not place sensitive personal data in a nickname or feedback. The product is intended for people aged 16 and older.
4. Purposes and legal bases
- Provide the test, progress recovery, free result, share card, Secret Partner Match, and purchased reports.
- Handle authentication, payment, refunds, email notices, support, and duplicate-charge prevention.
- Secure accounts and the service, prevent fraud and abuse, and diagnose technical errors.
- Use minimized first-party data to understand completion, recovery, and product experience. The first release does not use advertising pixels or session replay.
- The precise legal basis depends on location and commonly includes contract performance, consent, legitimate interests, and legal obligations. Non-waivable rights remain unaffected.
5. Service providers
We may use Neon for database and authentication, Vercel for hosting, Stripe for payments, OpenAI for paid report generation, Inngest for background work, Resend for email, and Sentry for technical error monitoring. They process necessary data under their respective roles and agreements.
- Report input sent to OpenAI excludes nickname, email, IP address, orders, payment data, and free-text feedback.
- Sentry is configured to remove email, cookies, authorization data, answers, report text, and payment metadata.
- Stripe handles payment details separately and may retain transaction records as legally required.
6. Retention
- Anonymous results and anonymous challenges are normally retained for 30 days unless claimed after sign-in or deleted earlier.
- Signed-in data is retained until account deletion or until it is no longer needed to provide the service.
- Rotated or revoked share tokens stop working immediately; a daily job deletes expired anonymous data.
- Refund, accounting, fraud-prevention, and tax records may retain only the fields required by applicable law.
- Backups and security logs may take a limited additional period to expire under the applicable retention schedule.
7. Security and international transfers
We use access controls, high-entropy tokens, hashed storage, encryption in transit, signed webhooks, rate limits, and minimized logs. No online service can promise absolute security. Providers may process data outside your country; the production operator must add any applicable transfer mechanism and regional disclosure before launch.
8. Your choices and rights
- You can access account results and reports, delete challenges, and revoke or rotate share links.
- You may request access, correction, deletion, restriction, objection, and, where applicable, a portable copy or withdrawal of consent.
- Account deletion revokes sessions and removes application business data, except minimum payment records that must legally be kept.
- Use the support email shown on this page to exercise a right. We may verify identity and will respond within the period required by applicable law.
9. Cookies, changes, and contact
We use first-party cookies or local storage needed for sign-in, locale, progress recovery, security, and payment return. If non-essential analytics or advertising technology is added later, we will update this notice and obtain consent where required. Material policy changes will update the date and include appropriate notice.