Short version: we collect what you type into our forms, use it for the purpose you gave it, and don't sell it. Ever.
The only personal information this site collects is what you submit through its forms: newsletter signup, contact, event proposals, and the partner, volunteer, and consulting inquiries. Each form states what it needs; email is required, phone is optional. Forms also record which page you submitted from and, when you arrive via a campaign link, standard UTM tags, so we know which outreach works.
This site uses Google Analytics 4 to count visits and see which pages and events people actually reach. It tells us that a page was viewed, roughly where in the world from, and which link brought you. We use it to decide what to publish and where to put it.
We do not run advertising trackers, we do not sell or share what it collects, and it is never joined to anything you submit through a form. Analytics data sits with Google under their terms, separate from the submissions described above. Browser and OS controls that block analytics work normally here; nothing on this site asks you to turn them off, and the rest of the site works with them on.
Submissions are validated and stored server-side, and a notification email is sent to the operations inbox. Personal details are excluded from application logs. Email delivery uses a transactional provider (Resend) when configured; the provider is not used as a database, and messages containing your details are not forwarded beyond the operations inbox.
The newsletter is consent-based: you check a box to join, every issue includes unsubscribe, and unsubscribing works without explanation. We never sell or share your contact information, and no outside organization receives attendee or subscriber lists.
You can ask what we hold about you, ask us to correct it, or ask us to delete it: use the contact form or the email address in the site footer. Deletion requests are honored except where a record is needed for an active event you are hosting or a legal obligation.
This policy is written to be read. If anything is unclear, that’s a bug; tell us and we’ll fix the wording.