Big Live CMS Platform Privacy Policy
Last Updated: August 2026 · Governing Event Organisers, Promoters, and Administrative Users of the Big Live CMS & Backstage Management Platform.
This Privacy Policy outlines how Big Live (operated by Rhythm Labs) handles personal and organizational information collected from event organizers, festival promoters, enterprise partners, and administrative staff ("Organizers") who access the Big Live Content Management System (CMS), Backstage dashboards, and related platform APIs.
Note: For attendees and fans using Big Live festival mobile applications, please refer to our dedicated Mobile App Privacy Policy.
1. Roles and Data Processing Relationships
Under the Privacy Act 1988 (Cth), Australian Privacy Principles (APPs), and international data protection standards (including GDPR):
- Data Controller: The Event Organizer is the Data Controller responsible for defining the event parameters, attendee interaction rules, and policies governing data collected from festival attendees.
- Data Processor: Big Live acts as a Data Processor, maintaining the cloud infrastructure, synchronization engines, content delivery networks, and real-time databases that power the Organizer's festival apps.
2. Information Collected from Organizers
When you register an organization or event account on the Big Live CMS, we collect:
- Account & Administrative Credentials: Full name, organizational email address, phone number, organization name, and authentication tokens.
- Billing & Commercial Records: Enterprise billing address, primary contact details, payment transaction identifiers, and subscription tiers.
- Event Asset & Operational Data: Artist lineups, stage schedules, geospatial venue coordinates, emergency contact lists, vendor applications, push notification logs, and branding assets.
- System & Audit Logs: Timestamped records of administrative actions (e.g. content updates, moderation actions, push broadcast triggers) to ensure platform traceability and security.
3. Use and Processing of Organizer Data
We use organizational and administrative data to:
- Provision and authenticate access to the Big Live CMS and event management dashboards.
- Synchronize festival schedules, maps, and content across cloud databases and client mobile applications.
- Execute push notification broadcasts and real-time emergency safety messaging.
- Deliver event analytics, attendance metrics, and performance insights to authorized managers.
- Provide customer support, onboarding assistance, and technical troubleshooting.
4. Data Storage, Security & Isolation
Big Live employs a multi-tenant cloud architecture hosted on Google Cloud Platform and Firebase. We implement comprehensive security safeguards:
- End-to-end data encryption using TLS/HTTPS for all data in transit and AES-256 for data at rest.
- Strict tenant isolation to ensure organizational datasets cannot be accessed by unauthorized third parties.
- Role-based access control (RBAC) allowing event organizers to delegate permissions (Admin, Editor, Staff, Moderator) within their team.
5. Sub-Processors & Third-Party Services
We engage trusted enterprise sub-processors to deliver core platform services:
- Cloud Infrastructure: Google Cloud Platform / Firebase (Firestore, Cloud Functions, Storage, Hosting).
- Push Notification Delivery: Apple Push Notification service (APNs) and Firebase Cloud Messaging (FCM).
- Mapping & Geospatial Services: OpenStreetMap, Mapbox, and Google Maps API.
6. Data Retention, Portability & Deletion
Event data and analytics remain accessible in the CMS for the duration of the subscription agreement. Organizers can request full export of their event datasets or execute permanent account and event deletion at the conclusion of an event cycle by contacting our data operations team.
7. Contact and Inquiries
For questions regarding platform privacy, data processing agreements (DPAs), or security compliance:
