1. Who we are
The Bookitive platform is operated by Jetlio, s.r.o., IČO 09967231, Voroněžská 2547/1, 616 00 Brno, Czech Republic, registered at the Regional Court in Brno, file C 121887 ("we"). Privacy contact: [email protected]. We have not appointed a data protection officer (the statutory thresholds are not met); privacy is led by the company director.
2. Our roles
Bookitive is a platform for running events and selling tickets. We act in different roles depending on whose data is involved:
- Controller — for organizer accounts, for visitors of this website, and for platform security and fraud prevention (see section 5): protecting all events on the platform from scalpers and abuse is our own purpose, so for that processing we decide the means and are the controller, similarly to how payment providers run their own fraud systems.
- Processor — for the data of ticket buyers and event guests, which we process on behalf of the event organizer under our Data Processing Agreement. The organizer is the controller of that data. If you bought a ticket, direct your requests primarily to the organizer of your event — we will help them fulfil them. A short summary for buyers lives at Information for ticket buyers.
3. What we process and why
Organizer accounts (controller, legal basis: contract) — name, email, password (stored only as a bcrypt hash), organization details, team members and roles, event settings.
Bank integration (processor for payment matching; contract) — if the organizer connects a bank account, we store its API token encrypted (AES-256-GCM) and read incoming transactions: amount, payment reference, date, and the payer's name or account number, solely to match payments to orders and process refunds the organizer initiates.
Buyers and guests (processor; the organizer's contract with the buyer) — name, email, optionally a phone number, selected seats, orders and their status, attendee names where the event requires them, ticket delivery records, and check-in records (scan time and result).
Phone verification (processor; the organizer's event settings) — where an event requires it, the phone number and a verification code are processed through our SMS provider.
Fraud prevention and anti-scalping (controller, legal basis: legitimate interest — protecting the platform and its events from fraud and ticket scalping) — for each order we process the IP address, basic device characteristics (a coarse, non-reversible hash of browser traits), purchase-behavior signals (order velocity per email, phone, IP and across events, disposable-email and scripted-client indicators, quantity and value), and compute a risk score. IP addresses may be checked against a geolocation and anonymizer database. Every order held by this system is reviewed by the organizer — no ticket is refused by automation alone. You can object to this processing (section 8); we have carried out a balancing test and an impact assessment for it.
Rotating tickets (processor) — where an organizer enables screenshot-proof tickets, a random device identifier is stored in your browser (localStorage) to bind the ticket to your device. You can clear it in your browser; details in the Cookie Policy.
Sponsor outreach (processor) — where an organizer uses sponsor campaigns, we process contact details of the approached companies (name, contact person, email, public data from their website) on the organizer's behalf, including drafting email text via our AI provider. No buyer data is involved in this flow.
This website — uses only technically necessary storage plus, with your consent, privacy-friendly analytics (PostHog, EU-hosted). Details and settings in the Cookie Policy.
4. Who we share data with
We use vetted providers under data processing agreements — the current list, including purposes, locations and transfer mechanisms, is maintained at Subprocessors. Primary processing takes place in the EU (AWS, Frankfurt region). Where a provider processes data outside the EEA, we rely on the EU–US Data Privacy Framework and/or the EU Standard Contractual Clauses, with the SCCs applying automatically if the framework ceases to be valid. We never sell personal data.
5. Automated decision-making
The fraud-prevention system assigns orders a risk score and may, per the organizer's settings, flag an order, request phone verification, or hold it for the organizer's review. Held orders are decided by a person (the organizer), not by the algorithm. Where an organizer enables automatic rejection at the highest risk level, that setting is the organizer's decision and buyers may contest the outcome with the organizer or with us at [email protected]; we will have a person review it.
6. How long we keep data
- Organizer accounts and event data — for the duration of the account.
- Orders and tickets — for as long as the organizer's and our legal obligations require (accounting and tax records in particular).
- Audit logs (including IP addresses and browser identification of administrative actions) — 365 days, then deleted automatically.
- Risk signals — kept with the order record.
- Expired unpaid reservations release their seats; the order record remains for payment traceability.
- After account termination: export available 30 days, deletion within 7 days of request, backups purged within 90 days (see Terms, section 15).
7. How we protect data
Communication with the service is encrypted (TLS). Passwords are stored as bcrypt hashes; bank tokens, SMTP credentials and ticket secrets are encrypted at rest (AES-256-GCM, keys manageable via AWS KMS). Access within an organizer's team is governed by roles — a door scanner sees check-in, not revenue. Administrative actions are recorded in an audit log. More in Security.
8. Your rights
You have the right to access, rectify and erase your data, restrict processing, data portability, and the right to object — including specifically to fraud-prevention processing based on legitimate interest. Exercise them at [email protected]. If you are a ticket buyer, contact the organizer of your event first — they are the controller; we assist them within 14 days. You may lodge a complaint with the Czech Office for Personal Data Protection (uoou.gov.cz) or your local supervisory authority.
9. Breach notification
If a personal data breach occurs, we follow a documented incident-response process: affected organizers are informed without undue delay (within 48 hours of confirming a breach affecting their data) and the supervisory authority within the statutory 72 hours where required.
10. Children
The Platform is intended for persons aged 15 and over (the Czech digital-consent age). Organizer accounts require legal capacity to contract or the consent of a legal guardian.
11. Changes
We may update this policy when features or providers change. Material changes are announced to organizers by email. The current version always lives at this address.
Effective from 1 September 2026