Scope
This Privacy Policy explains information practices for Bigtop’s event-hosting service. A static demo deployment does not send form data to a server. A production service may process account, organizer, attendee, billing, and technical information needed to provide the service.
Organizer and attendee data
Attendee data belongs to the event organizer. Bigtop processes that information on the organizer’s instructions to provide registration, event access, interaction, and replay functions. Organizers remain responsible for appropriate attendee notices and any consent required by law.
Information collected
A production account may include name, email, country, event configuration, registration responses, audience interactions, replay metadata, and support communications. Subscription payment details may be processed by a payment provider rather than stored directly by Bigtop. For paid ticket pages, the organizer connects its own Stripe account and controls its payment relationship.
Use and sharing
Information may be used to operate the service, authenticate users, provide support, prevent abuse, maintain security, and comply with legal obligations. Service providers may process information on Bigtop’s behalf under contractual safeguards. Bigtop does not sell attendee data as a product. Organizers decide how event registration information is used within the service, subject to law and these terms.
Retention and deletion
Retention depends on the account, event, and plan. Replay windows are specified by plan. Organizers can request deletion where applicable, subject to legal, security, billing, and backup requirements. A production privacy program should publish its operational retention schedule and regional rights process.
Your choices
Depending on location, individuals may have rights concerning access, correction, deletion, restriction, portability, or objection. Requests should be directed through the production contact process. This static project intentionally leaves contact fields blank.
Security
Bigtop uses reasonable administrative, technical, and organizational measures appropriate to the service. No internet service can promise absolute security. Organizers should use strong credentials and limit team access to people who need it.