Privacy and erasure
How personal data is handled and erased.
What a signup stores
| Column | PII | Purpose |
|---|---|---|
email_original | yes | Address as typed, for sending mail |
email_normalized | yes | Dedup key (unique per waitlist) |
source | yes (may hold a referrer URL / UTM tags) | Attribution |
ip_hash | yes (pseudonymous) | Anti-abuse |
id, waitlist_id, status, referral_code, referred_by_signup_id, verified_at, created_at, deleted_at | no | Ordering, referrals, audit |
Signups are kept until the project owner erases them.
Operational rows are pruned daily by /api/internal/cron/prune-data
(server/domain/retention.ts). Pending work is never deleted.
| Data | Kept |
|---|---|
| Expired sessions and verification tokens | deleted once expired |
| Sent or failed outbox mail (payload holds the address) | 30 days |
| Delivered or failed webhook payloads (hold the signup email) | 30 days |
| Used or expired confirm/remove tokens | 30 days |
| Abuse events, ops events | 90 days |
| Processed Stripe events, daily email counters | 90 days |
| Rate-limit buckets | until expiry (hourly job) |
Erasure
DELETE /api/v1/waitlists/:id/signups/:signupId (secret key) erases a
signup in place:
email_original,email_normalized,sourceandip_hashare set toNULL(hard delete of the values, not a flag).statusbecomesremoved;deleted_atis set on the first call and kept on retries.- The row itself stays as an anonymized tombstone: its id, referral
code, and referral links remain, so:
- other signups' positions follow the documented rule (rank among live signups) — signups after the erased one move up by one, nobody else changes;
- if the erased signup was referred, its referrer's count is unchanged.
- The erased signup no longer appears in listings or by-code lookups
(
404). The secret-key detail route still returns the tombstone so the owner can confirm the erasure. - The address is freed: the same email can join again later and gets a new signup at the back of the list.
Erasure is irreversible; there is no undo.
Removal without erasure
A creator can also take a signup off the list without deleting anything
(PATCH /api/v1/waitlists/:id/signups/:signupId with status: "removed", or
the dashboard's Remove). The row keeps its address and source, deleted_at
stays NULL, and it leaves the live ranking exactly as erasure does, so
positions and referral credit behave the same. Because the address is still
stored, it is not a data-subject erasure; use Erase for that. A removed
signup can be restored (status: "pending"); it must confirm its address
again. An erased signup can never be restored.
Recipient-initiated removal
Every email carries a removal link (and List-Unsubscribe one-click headers).
Using it performs the same erasure as above. The link's token is stored only
as a SHA-256 hash, never expires, and is not usable for anything else.
Not yet covered
- Pending outbox emails for an erased signup are never sent (the drain checks the signup first and marks them failed without alerting). Webhook deliveries are handled when they land (2.3).
- Abuse events store only hashed or normalized values (1.4).
- Database backups retain erased values until they expire (4.3 documents the backup window).