Privacy / launch gate
Privacy notice placeholder
This page describes the intended shape of the readiness-check data flow while the final controller, lawful basis, retention, and contact details are still awaiting approval.
What the check asks for
The assessment captures answers about product scope, market context, product and supplier data, evidence, ownership, exchange, trigger, desired outcome, and next step. The detailed report gate asks for name, work email, company, role, optional phone, a required privacy acknowledgement, and optional marketing consent.
Why it is collected
The intended purposes are to calculate and deliver the requested directional report, understand readiness patterns across market tests, and, only when separately consented, send occasional company updates. The final lawful basis and retention periods are not yet approved.
External processing
When configured, the static site sends the assessment payload to an external automation endpoint for report processing. That endpoint, its providers, storage region, access roles, deletion process, and incident contact must be documented and reviewed before launch.
Your choices
The detailed report acknowledgement and optional marketing consent are separate. The final notice must explain access, correction, deletion, withdrawal, suppression, and how to contact the responsible entity.
No legal entity, controller, processor, email address, or retention period is invented here. Add approved details before launch.