Security
How ZipKnow protects what organizations collect, and how to tell us if something is wrong. See also Privacy and Status.
Less to protect
Check-in records only a postal code and a time. No names, emails, phone numbers or addresses are collected from guests, so there is no guest identity to lose.
Each organization’s data stays its own
Every table is protected by row-level security in the database, so a signed-in person can read and change only the workspaces they belong to, and plan limits are enforced in the database as well as the app. Volunteer and kiosk links use a single-purpose token that can only add check-ins to one event, and can be turned off at any time.
Signing in
No passwords. Organizers sign in with a one-time email code or link, a passkey, or Google, and can require a second step. Sessions are kept in secure, HTTP-only cookies.
In transit and at rest
Everything is served over HTTPS with strict transport security, a content security policy, and headers that stop the site being framed or sniffed. The database (Supabase, on AWS in the United States) encrypts data at rest and keeps regular backups. Payments go straight to Stripe; we never see card numbers.
Changes and reviews
Every change is reviewed and tested before release, and the database’s access rules have their own tests.
Reporting a problem
Found a vulnerability? Email markrappmusic@gmail.com with “Security” in the subject. We’ll acknowledge within two business days, keep you informed, and credit you if you’d like. Please give us a reasonable time to fix it before publishing, and don’t access or change data that isn’t yours. The same details are at /.well-known/security.txt.