Privacy
Document status
This notice describes the data flows actually used by the current public research-candidate version of P-120. A separate legal/privacy gate remains open before commercial production launch for applicable law, exact controller/operator roles, mandatory particulars, the data-subject rights workflow, provider/transfer disclosures and future payment/consumer flows.
Separation of research and contact data
The P-120 research intake and the Contact form are separate data flows. Contact is for general correspondence and professional communication only; it is not linked to a Participant ID, P-120 responses, assessment results or a personal report.
Participant identifier
The current research web form uses a pseudonymous Participant ID. The automatic research intake does not add a name, e-mail address or phone number to the response package.
Research responses and operational data
The research package may include scored-item responses, form version, interface locale, coverage, selected administration modes and session timestamps. The current intake implementation does not include browser telemetry in the transmitted research package.
Local storage
Current-session state and operational records, including responses and the legal clickwrap record, may be stored locally in the browser to support session continuity and record the accepted notice version.
Research storage
After completion of the scored items, the current configuration may transmit a pseudonymous response package to the configured private research store. Browser-side access is constrained to the configured intake path. This notice does not claim that the current pre-commercial architecture is the final commercial privacy architecture.
Contact: data submitted
The Contact form transmits a name if the user chooses to provide one, a required e-mail address, message subject, message text and interface locale. Technical form and privacy-notice versions are transmitted with the request. Anti-bot fields and the form start time are used by the server to validate the request and are not included in the stored message record.
Contact: processing purpose
Contact data is used to receive, process and respond to an enquiry and to maintain the operation and abuse protection of the contact channel. This data flow is not used to calculate P-120 and does not become part of the user’s research profile.
Contact: storage and retention
After server-side validation, name (if provided), e-mail, subject, message text, locale and form/privacy-notice versions are stored in private P-120 contact storage. Each message receives a retention_until value 90 days after receipt; expired messages are removed by an automatic daily retention cleanup and are also cleared during subsequent storage operations.
Contact: rate limiting and technical markers
To protect the channel against automated or excessive submission, the server briefly processes the connection network address and e-mail address to derive HMAC bucket markers. The raw IP address is not included in the stored Contact message record. Rate-limit buckets use short windows: 15 minutes for the short IP limit and up to 24 hours for daily IP/e-mail limits; expired markers are removed. Browser telemetry is not included in the Contact message record.
Contact: content boundary
Do not send P-120 responses or results, Participant IDs, medical information, details about intimate life, passwords, payment information or other confidential material through Contact. A general description of the question is sufficient.
Technical providers
The current site loads some font resources through Bunny Fonts and uses Supabase infrastructure for configured research/contact flows. This notice does not assign final jurisdiction-specific legal roles to those providers or make conclusions about international transfers; exact roles, processing locations, contractual grounds and required disclosures remain part of production legal/privacy review.
Commercial production gate
Before public commercial production release, the final Privacy Policy, processing and retention grounds for all production flows, data-subject rights workflow, provider and transfer disclosures, payment/consumer data flows and other mandatory elements of applicable law must be separately approved. The current public-research-candidate publication does not close that production-level legal gate.