Skip to main content

Privacy Policy

Last updated: November 2026

Who we are

Danzeira is an event discovery and ticketing platform for the dance community, operated from Australia. If you have questions about this policy, contact us at [email protected].

Information we collect

We collect information you provide and data generated when you use Danzeira:

  • Account data: name, email address, and a hashed password if you set one. Sign-in codes are stored hashed and expire after 10 minutes. If you sign in with Google or Apple, we store that account's ID and email address. If you use passkeys, we store WebAuthn credential identifiers and related metadata (not your biometric data). If you choose to update it, we store your time zone. Your browser's time zone is only read in the page and sent when you accept.
  • Orders and tickets: buyer and attendee names, email addresses (including per-ticket holder emails when provided), ticket types, dance roles, promo codes applied, order history, and your answers to any question the organizer asks at checkout (for example, your dance experience).
  • People profiles: handle, bio, dance styles and levels, profile location, and badges. Your public name is your first name and last initial. Everyone but accepted connections sees only that name and your photo.
  • Event instructors: names, bios, and photos that organizers add to show who teaches an event. These appear publicly on the event page. Organizers can search approved instructors by name to link their page, and a linked instructor's profile photo shows when the organizer adds none. Events that link you are listed on your profile. We email you when you are linked and when a session you teach moves or is removed, and you can remove the link yourself; ask the organizer to remove your name.
  • Connections: requests you send or accept, the organizers and people you are connected to, and the people you block.
  • Discovery preferences: home area, event radius, and dance-style filters used to personalize event discovery and optional email digests.
  • Waitlists: your place on a waitlist when a ticket type is sold out, if you join one.
  • Feedback: messages you send through the Feedback form, including optional page URL, browser information, and screenshot attachments.
  • Organizer profiles: display name, bio, and related event information you publish.
  • Favorites: events you bookmark.
  • Session picks: the sessions you add to your schedule. Only you see them.
  • Calendar feeds: a private subscription token and your feed preferences (which events to include).
  • Push subscriptions: browser push notification endpoints if you opt in to event reminders, including as a guest after purchase.
  • Notification preferences: which topics you receive by email and push, the events whose session reminders you muted, and the in-app notifications we sent your account in the last 90 days.
  • Two-step sign-in: if you turn on an authenticator app, we store an encrypted setup secret and encrypted backup codes.
  • Private lessons: for instructors, availability, prices, locations, and any trips they add (city and dates, shown publicly); for students, lesson requests (with any message you add) and payment status. Instructors see your name and message when you request a lesson. An instructor can share an image of their open and taken times. It never shows who booked. A photo an instructor adds to the image stays on their device and is not uploaded.
  • Reviews: a rating and optional comment you write about an event or private lesson. It is public, shown with your name and photo and linked to that event or lesson, and counts toward the organizer or instructor. Their reply, and any report about it, are kept with it. You can edit or delete your review at any time.
  • Messages: the direct messages you send and receive, visible to you and the other person. Our team reads a conversation only when one of you reports it. A new message may be sent to the other person as a notification or email that includes its text. If you delete your account, the other person keeps the conversation, shown as from a deleted account with no name, photo or profile link.
  • Connected calendars: if an instructor connects an external calendar, we store its link and the start and end times of busy events, not their titles or details, and we fetch the link regularly. Calendar feeds can include booked private lessons.
  • Google Calendar: if an instructor connects Google Calendar, we access the list of their calendars (names only) and the free and busy times of the calendars they switch on, never event titles or details. We store those calendar names, the busy times and an encrypted access token, and use them only to block lesson times that are already taken. We do not share or sell this data. An instructor can disconnect at any time, and we then revoke our access in Google. Danzeira's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
  • Access tokens and connected apps: API tokens you create (stored hashed, with what each one may do and its last-used time) and apps you authorize to act on your account. A token or app sees and changes only what you could yourself on the website.
  • Uploaded content: profile avatars and event cover images. An organizer can make an event poster in their browser. A photo added to it stays on their device unless they save the poster as the event's cover image, which uploads it like any cover image.

Payment information

Card payments are processed by Stripe. Danzeira does not store full card numbers. Stripe may collect billing details and payment method information according to its own privacy policy.

Location data

When organizers add event venues, we geocode addresses to show events on a map. Address autocomplete (for event venues, your dancer profile location, and your home area in Account Settings) sends your typed search queries to Mapbox so you can select a place. We store the location you provide and the resulting coordinates — not your device's GPS location. Profile and home locations are stored and shown as city and region where applicable, not full street addresses.

Communications

We send transactional emails (sign-in codes, order confirmations, password resets, ticket transfers, event cancellations, event updates, event reminders, waitlist promotions, and organizer notifications) via our email provider. If you opt in, we send a weekly what's on digest of events near your home area. If you connect with an organizer, we may also email you when they publish a new event. After an event or private lesson you attended ends, we may email you once to ask for a review, and we email organizers and instructors when someone reviews them. You can turn these emails off under Notifications in your settings or with the unsubscribe link in the email. If you enable push notifications, we also send event reminders, event updates, lesson requests and reminders, and new-event alerts from organizers you are connected to through your browser's push service. If you have push on, we send the review request there instead of by email. We also email lesson requests and updates, connection requests, and organizer announcements. Organizer announcements are also shown on the event page to ticket holders and event organizers. You can turn each topic on or off in Notification settings, or use the unsubscribe link in any optional email. If you are not signed in, we store your email address with your unsubscribe choice so we honor it.

Website analytics

We use Cloudflare Web Analytics to understand how visitors use Danzeira — for example, which pages are viewed, where traffic comes from, and general device and browser information. This helps us improve the site. Cloudflare Web Analytics does not use cookies, does not track you across other websites, and reports aggregated usage data rather than identifying individual visitors.

Danzeira also records key steps people take on the site, such as viewing an event, reserving tickets, paying, or creating an account, so we can see where people get stuck. This uses no cookies. Signed-out visitors are counted with an anonymous code that changes every day, so visits cannot be linked across days; we do not store IP addresses for this. If you are signed in, steps are linked to your account. We delete these records after 13 months, and they are never shared or sold.

Cookies and sessions

Danzeira uses a session cookie to keep you signed in. Sessions are stored in our database. We do not use third-party advertising or tracking cookies.

How we share information

  • Payment processing: Stripe receives order and payment data needed to complete transactions, card holds for private lessons, and organizer and instructor payouts.
  • Email delivery: Our email provider processes recipient addresses and message content for delivery.
  • Address search: Mapbox receives location search queries during address autocomplete.
  • Error monitoring: In production, we use Sentry to collect technical error reports (such as stack traces and request metadata). We do not intentionally send personal information to Sentry.
  • Website analytics: Cloudflare receives anonymized, aggregated usage data (such as pages visited and referring site) to provide analytics.
  • Google and Apple sign-in: If you choose to continue with Google or Apple, that provider confirms your identity and shares your name and email address with us. Apple may give us a private relay address instead of your real email.
  • Google Wallet: If you add a ticket to Google Wallet, Google receives ticket and event details needed to create the pass.
  • Calendar subscriptions: Anyone with your calendar feed URL can read the events included in that feed. Keep the link private and regenerate it from Settings if it is shared.
  • Event organizers: Organizers can see attendee names, contact details, and checkout answers for tickets sold to their events.
  • Dancer profiles and connections: Anyone with the link to your page sees your name and photo, and signed-in users can find you by searching your name. Your dance styles, bio, badges, city, and upcoming events go only to people whose connection request you accept. Organizer and instructor pages are public.
  • Public Who's Going lists: When an organizer enables a public attendee list, attendee names may appear on the event page. Attendees you have not connected with are shown with a masked name (for example, “Alice D.”). Signed-in users can hide themselves in Privacy Settings; guests can opt out at checkout. Organizers still see your tickets.
  • Legal requirements: We may disclose information if required by law or to protect the rights and safety of users.

We do not sell your personal information.

Retention and your rights

We keep account and order data for as long as needed to provide the service, comply with legal obligations, and resolve disputes. You can update many preferences (profile, privacy, email notifications, and security) in Settings. You can request access to or deletion of your account by emailing [email protected].

Changes to this policy

We may update this Privacy Policy from time to time. We will revise the "Last updated" date when we do. Continued use of Danzeira after changes means you accept the updated policy.