Privacy
Last updated October 30, 2026. ZipKnow is a product of Open Arts, LLC. See also our Terms of Service.
Event guests
At check-in we record only the postal code you give and the time it was entered. Giving it is optional: if you’d rather not, the organizer may note only that a guest didn’t share one, with the time. We don’t ask for or store your name, email, phone number or address, and we don’t use cookies or trackers on the check-in page. The organization running the event sees totals by ZIP code, city, county and state to understand where its audience comes from, and may share those totals with the funders that support its events. If the organization takes part in Audience Constellation (below), other participating organizations see only a similarity score and a few town names worked out from many guests together, never anything about you. Some organizations also ask visiting groups whether they’re staying overnight because of the event (nights, rooms and type of lodging, optionally the property). That question is optional too, nothing identifies you, and answers are reported only as totals.
Organizations
Organizers sign in with their email address or a passkey. Each organization’s events and check-ins are private to that organization’s owners and admins, except for the summaries described under Audience Constellation, which an organization’s owner can choose to share. If you choose to scan your website for branding, we read only its public pages. We don’t sell data or share it with advertisers.
Audience Constellation (optional, Pro)
Audience Constellation helps organizations find others whose audiences live in the same neighborhoods. It is off unless a workspace’s owner turns it on, and only organizations that turned it on take part. An organization on the free trial can’t take part; it needs a paid plan. It works both ways: a participating organization sees others only while they can see it.
Participating organizations see each other’s name, website, a one-line description and an optional contact email the owner chose to share; a percent saying how much their audiences overlap; how many ZIP codes both draw from; and up to three towns where one draws well and the other doesn’t. To work these out, ZipKnow compares the ZIP-code totals of the two organizations’ U.S. check-ins from the last 24 months. Overlap only counts a ZIP code where each organization has at least 3 check-ins, a town is shown only where the other organization has at least 10 check-ins in one ZIP code, and an organization needs at least 50 check-ins to take part. No counts, events, dates, individual check-ins or anything about a guest are shared. Practice events, removed check-ins, “No ZIP” taps and overnight answers are never used.
An organization stops appearing as soon as its owner turns Audience Constellation off, its Pro plan ends, or it asks to delete its workspace. Questions about another organization’s use of what it saw should go to that organization.
Cookies and storage on your device
We set cookies only to keep organizers signed in; they hold your session and nothing else, and they end when you sign out. There are no advertising, analytics or third-party cookies anywhere on ZipKnow, so there is nothing to consent to and no banner. The check-in, volunteer and kiosk screens keep entries in the browser’s own storage until they reach our server (so a lost signal loses nothing) and remember small conveniences such as the chosen look; that storage stays on the device and is never sent anywhere else.
Volunteers
Volunteers who check guests in use a link and never sign in. When an organizer makes a link for a named volunteer, the name (and an email address, if the organizer adds one) is saved in that organization’s workspace so it can be suggested for future events. Only the organization’s owners and admins see it, ZipKnow never emails volunteers, and an organizer can remove a saved volunteer anytime in Settings.
Payments
If your organization upgrades to Pro, payment is handled by Stripe. We never see or store card numbers; we keep only what we need to know your plan is paid. Stripe’s own privacy policy covers the payment details you give it.
What we keep about organizers
For each person who signs in: an email address, the sign-in method (email link, passkey or Google), the workspaces they belong to and their role in each, and the time of their last sign-in. For each workspace: its name, website and branding, its events, venues, grants, check-ins and reports, and its plan. If a workspace pays for Pro, we keep Stripe’s customer and subscription identifiers, not card details. Our servers keep ordinary request logs (address, browser, page, time) for a short period to keep the service running and secure.
How long we keep it
Workspace data stays as long as the workspace exists, because organizations compare seasons across years. A deleted event’s check-ins are erased at once; a deleted workspace is erased 7 days after its owner asks (see below). Server logs are kept for no more than 30 days. Payment records stay with Stripe for as long as tax and accounting rules require.
Services we rely on
ZipKnow runs on Vercel (hosting) and Supabase (database and sign-in), both in the United States. Stripe handles payments, Resend sends our emails, and map tiles come from OpenStreetMap when a report is viewed. Each sees only what it needs for its part. We don’t sell data, share it with advertisers, or use it to train anything.
Children
ZipKnow is for organizations and the adults who run their events. We don’t knowingly collect anything from children under 13, and a postal code at check-in is never tied to a person of any age.
Your rights
Wherever you live, you can ask us what we hold about you, ask us to correct or delete it, or object to how we use it. Organizers can see and change most of it in Settings and can delete their workspace themselves; for anything else, write to us at the address on the contact page and we’ll answer within 30 days. People in California, the European Economic Area and the United Kingdom have these rights by law, including the right to complain to their local data protection authority; we don’t sell or “share” personal information as those laws define it. If we ever change how we use data in a way that matters, we’ll say so here and tell organizers in the app or by email first.
Deleting a workspace or account
A workspace’s owner can delete the whole workspace from Settings → Organization. After 7 days, its events, check-ins, reports, grants, volunteers and settings are erased permanently, and the owner can choose to delete their ZipKnow login too. Payment records stay with Stripe.
Questions or removal
For questions about an event, contact the organization that ran it, for example through its website. For anything else, including a request about your data, email markrappmusic@gmail.com or see the contact page. Organizations can remove individual check-ins at any time from their workspace, or delete an event along with everything recorded at it. A deleted event’s check-ins are erased permanently, not just hidden.