Synthetic data
STUDIO / FANSPINE / LIVE BACKEND
Export by purpose
Every export answers three questions before a single hash leaves: is this recipient allowed, did each supporter agree to this purpose, and is the group big enough to be anonymous? Only consenting supporters go out, as SHA-256 email hashes in the format Google and Meta accept. Synthetic data, labelled as such.
Run an export
session …Club email marketing needs marketing_email. Destinations: CSV.
Delivery to a partner is a signed webhook (HMAC-SHA256) to one configured endpoint. It is switched off in this demo.
Run log
Every run is recorded, whether it was ready or refused.
| Time | Club | Purpose | Recipient | Destination | Status | Exported | Refusal |
|---|---|---|---|---|---|---|---|
| No runs yet. | |||||||
What is enforced, in order
- The rights matrix for any third party
- Latest consent for each required purpose
- A usable hashed identifier
- At least 50 people for any third-party export
- Every run logged, refused or not
What this is not
- No raw emails are stored or sent.
- No live upload to Google or Meta from this page.
- Delivery goes only to one configured, signed webhook.