Attendee personal data is encrypted at rest. Chobble Tickets does not use it for attendee marketing or list events in a public marketplace.
Your attendees have real reasons for privacy
If you're running any kind of 18+ event, your attendees are trusting
you with sensitive
information. Their name, email address, and the fact that they attended
your event are all things they may not want anyone else to know about.
Chobble Tickets encrypts all personally identifiable information at rest
using
hybrid RSA-OAEP + AES-256-GCM encryption.
Even if someone gained access to the database, they could not read
attendee names or contact details without credentials for an authorised
keyed user. The application decrypts those fields when an authorised
owner or manager needs to use them.
Attendee data is encrypted at rest.
Authorised keyed users can decrypt attendee details.
Stored database records do not contain readable guest details.
What happens on commercial platforms
Commercial ticketing platforms make money by connecting attendees with
more events. The platform treats your attendees' data as a marketing
asset.
On Eventbrite, attendees who buy a ticket to your event will see
recommendations for "similar events" and receive marketing emails based
on their attendance history. For someone who attended a private adult
event, that means the platform is actively trying to surface related
events to them, which could appear in a shared inbox or on a screen at
the wrong moment.
Chobble Tickets does not do this. There is no event discovery feature,
no recommendation engine, and no marketing emails sent to your
attendees. The only emails they receive are the booking confirmation and
any messages you choose to send yourself.
No "similar events" recommendations.
No marketing emails to your attendees.
No event discovery or public directory.
Your event, your branding
Chobble Tickets is white-labelled by default. Your attendees see your
event name and your branding on the booking page, not a ticketing
platform's logo. There is no public event directory linking your event
to a wider catalogue.
If you self-host, the booking page can run on your own domain. Chobble
Tickets does not require an attendee account or add a public event
directory. Paid bookings continue to the hosted checkout of the
organiser's selected Stripe, Square or SumUp account.
For events where attendees prefer not to have the name of a ticketing
platform appearing in their email inbox or bank statement alongside the
event name, this matters.
Your domain, your branding.
No public event directory.
No third-party account required.
Built for events where discretion matters
Encrypted attendee data
Attendee personal information is encrypted at rest. Stored names and contact details require credentials for an authorised keyed user, including an optional recovery owner if enabled.
Fully auditable
The complete product source is published under AGPL-3.0-only, so its collection, storage and integration code can be inspected.
Self-hostable
Run Chobble Tickets on Bunny Edge, Deno Deploy or a Docker-capable host. Configured payment, email and integration providers receive the data needed for their services.
No advertising, no data sales
No data harvesting
Chobble is a community interest company. There is no advertising revenue and no data economy subsidising the price. Your attendees will not receive marketing emails from the platform.
No public event directory
There is no discovery page, no "events near you" feature, and no way for anyone to browse a list of events hosted on the platform. Your event is only visible to people you share the link with.
Flat fee
Chobble charges a flat fee with no per-ticket charges. The business model is based on the fee you pay, not on monetising your attendees' data.