Trust & Security
Controls, data handling, incident posture, and implementation details. We're transparent about how we protect your event and attendee data.
Payments — Processed by Stripe. We never store card numbers. Stripe is PCI-DSS compliant and handles tokenization, encryption, and fraud prevention.
Role-based access — Admin, content manager, and check-in staff roles with scoped permissions. Team members see only what they need.
Check-in validation — Real-time ticket validation and duplicate detection. Scanned tickets are flagged instantly across all devices to prevent fraud.
Storage — Data is stored on Google Cloud (Firebase/Firestore). See our Privacy Policy for what we collect and how we use it.
Payouts — Direct to your Stripe account. We don't hold funds. No waiting on weekly batches or platform-held reserves.
Exports — Attendee and ticket data can be exported. Contact us for data retention and deletion specifics.
If you suspect a security issue or data incident, report it immediately:
Email: support@dionysus.dev — Subject: Security Incident
We respond to security reports promptly and will communicate status and next steps. For critical issues, we prioritize rapid assessment and mitigation.
We build for the day that matters — when thousands of attendees are trying to get in the door. Our infrastructure is designed to scale for peak festival periods (up to 1M concurrent users).
For SLA requirements, uptime guarantees, or status monitoring needs, contact us to discuss options.
Platform (ticketing, check-in, analytics) — Create an account, connect Stripe, and start selling. Most organizers are live within a day. We provide setup guides and support.
White-label mobile apps — Typically ~7 days from handshake to App Store, depending on developer account readiness and store review. Timeline breakdown:
See how festivals and conferences use Dionysus:
More case studies coming. Book a call to request references.
Questions about security, compliance, or implementation? support@dionysus.dev or book a call.