Draft before pilot launch
Privacy without the small print.
This document describes the implemented waitlist. Controller and contact details must be completed and legally reviewed before public launch.
Required before launch: the controller's name and address, a working privacy contact and any additional processors. Do not open the waitlist before these are complete.
Data collected
The waitlist asks for your email address, preferred role, preferred city and optional postcode. It also stores the language, submission time and consent.
The form does not store your IP address and the website does not build advertising profiles.
Why it is used
- to assess whether both sides have enough people in the same area;
- to invite you to a suitable test group;
- to contact pilot partners separately;
- to prevent duplicate registrations using the same email address.
The legal basis is consent. You may withdraw it before or during the pilot.
Retention and security
The configured Cloudflare KV storage expires waitlist records no later than 180 days after the latest registration. Choose a shorter period if that is enough for the actual pilot.
Access should be limited to people composing the pilot. Encrypt exports and delete them after use.
Suppliers and transfers
The proposed hosting and waitlist use Cloudflare Pages, Pages Functions and Workers KV. Review contracts, data locations and current privacy terms before launch. Add every other supplier before it receives data.
Your rights
You may request access, correction, deletion, restriction or transfer, object, or withdraw consent. Add a working contact and response period before launch.
Cookies and local storage
The new public page does not place cookies or store interface preferences. If analytics, spam protection or embedded media are added, update this notice and any required consent flow first.