What we keep, and why
Plain words, because the whole point of this product is keeping your phone number backstage.
What speakers give us
Your public profile: name, link, headline, bios, headshot, talks, links and the stats you choose to show. Anyone with your link can see these.
Your backstage details: legal name, phone, emergency contact, vehicle, dietary and stage notes. They are encrypted before they are stored and appear only on a backstage pass you issue.
If you connect Google Calendar: your calendar's free and busy times, never event titles, descriptions or guests. We also add accepted talks to a calendar you own. You can disconnect at any time, which revokes our access.
What organizers give us
The booking slip: your name, email, role, your university or organization, your city and country, an optional link, and the event details. The speaker you contact sees all of it.
Your request's private link and backstage pass are random tokens. We store only their hashes, plus an encrypted copy so we can include the link in later emails.
Where it lives
The database and sign-in run on Supabase. Headshots are stored in Amazon S3. Email is sent through Amazon SES. The app runs on Vercel.
Network addresses are stored only as a keyed hash, to limit spam.
How long we keep it
Backstage passes stop working the day after the event, and the speaker can revoke them earlier.
Speakers can delete their page from the profile screen. That removes the profile, requests, passes, backstage details, uploads and the Google connection.
Organizers can ask the speaker, or us through the feedback page, to remove a request.
Cookies
A sign-in cookie for speakers, a short-lived cookie during sign-up and Google connection, and an anonymous cookie that stops double votes on the feedback board. No advertising or tracking cookies.