Privacy Policy
DRAFT — pending legal review. This text is a placeholder so the product can link to it. It is not legal advice and is not yet binding.
Version: 2026-11-draft
Who is responsible
- Account holders (people who sign up for GetWait): GetWait is the
controller of your account data.
- Waitlist visitors (people who join a waitlist): the project that runs
the waitlist is the controller. GetWait is its processor and only acts on the project's instructions.
What we store
| Data | Whose | Purpose |
|---|---|---|
| Account email, username, password hash | Account holder | Sign-in, security |
| Terms acceptance time and version | Account holder | Proof of agreement |
| Session identifier (cookie) | Account holder | Keeping you signed in |
| Signup email, source, hashed IP | Visitor | Running the waitlist, anti-abuse |
IP addresses are stored only as a keyed hash. Details on retention and erasure: see "Data retention and erasure" in the documentation.
Cookies
We set one essential cookie, the sign-in session cookie (getwait.session_token, __Secure-getwait.session_token over HTTPS). It is HttpOnly, SameSite=Lax and host-only. It is strictly necessary, so there is no cookie banner. Your theme choice is kept in your browser's local storage and is never sent to us. We use no analytics or advertising cookies.
Erasure
Visitors can remove their email with the link in every email we send. Project owners can erase signups from the dashboard or API. Erasure deletes the address, source and IP hash; an anonymous row remains for ranking integrity.
Sub-processors
See the sub-processor list.
Your rights
Access, correction, erasure, portability and objection. For waitlist data, contact the project that runs the waitlist; for account data, contact us at the support address in the footer.