Controller context
The landing page identifies Verve Technology Ecosystem, Luxembourg, as the operating entity for this pre-launch waitlist experience.
Lawful basis
The required waitlist checkbox is used to capture consent for storing and processing submission data for waitlist administration. Optional updates rely on the separate optional consent selection made by the user.
Data minimization
The current form is limited to launch qualification data: contact details, role, key challenges, launch-fit information, and submission metadata needed to administer the cohort.
Access and deletion rights
Users should be able to request access, correction, export, or deletion of their waitlist entry. During pre-launch, these requests should be handled through direct Verve launch communication until a permanent public support address is published.
Processors and hosting
The landing app currently relies on Firebase Hosting and Cloud Firestore. The active Firestore database used for waitlist submissions is configured in Europe West 3.
International handling
If infrastructure, analytics, or support workflows later involve additional processors or cross-border transfer mechanisms, this notice should be updated before those changes go live.
Security posture
The current launch flow uses application-level validation plus Firestore security rules to restrict write access to the intended waitlist collection. Additional protections such as App Check, monitoring, and operational access controls remain recommended for full public launch.