Privacy policy

1. Who is responsible

• The event organiser is the controller for the data of their event's buyers and attendees. They decide what to ask and what to use it for.
• Piletikohver is the processor: we store the data and make it available to the organiser, but we do not use it for our own marketing and do not sell it on.
• For an organiser account's own data (name, email, password, logins) we are the controller.

2. What we collect

• name and email address — to send the ticket and to find the order
• phone number, if the organiser asks for it
• answers to the organiser's additional questions (attendee name, organisation, dietary preference and so on)
• order contents: ticket types, quantity, total, discount code, seat, language
• IP address and time of purchase — to prevent fraud and automated buying
• entry time, when the ticket is scanned at the door

3. Organiser account data

• name, email address, organiser name and contact details
• a password hash — we neither store nor see the password itself
• sessions, last login time and role on the account

4. Purposes and legal bases

• Issuing, sending and checking tickets — performance of a contract (GDPR art 6(1)(b)).
• Organiser notifications about changes and cancellations — performance of a contract.
• Running the account and logging in — performance of a contract.
• Preventing fraud and abuse, including limiting login attempts — legitimate interest (art 6(1)(f)).
• Accounting and statutory duties — legal obligation (art 6(1)(c)).
• Marketing emails — only with consent (art 6(1)(a)), which can be withdrawn at any time.

5. Who sees the data

• The event organiser and the users they authorise. A door-staff user sees only the attendee name and ticket validity — not prices or contacts.
• Email delivery: messages are sent through the SMTP service of Zone Media OÜ (Estonia).
• Hosting: the application and the database run on a server located in Estonia.
• To show a map, the event page loads map tiles from OpenStreetMap, which sees the visitor's IP address at that moment.
• Authorities, where the law requires it.

6. How long data is kept

• Orders and tickets: up to seven years after the event, because accounting law requires transactions to be retained.
• Answers to organiser questions: deleted with the order, or earlier if the organiser deletes them.
• Organiser account: until the account is closed, plus three months so that closing can be reversed.
• Login sessions: until logout or expiry.
• Server logs: up to 90 days.

7. Your rights

8. Security

• The connection is encrypted (HTTPS) and strictly required (HSTS).
• Passwords are hashed with scrypt; even we cannot recover the original.
• A ticket code carries 192 bits of randomness — it cannot be guessed.
• Login attempts and code lookups are rate limited so that passwords and order codes cannot be brute forced.
• Each organiser sees only their own data; access is checked on the server for every request.

9. Automated decisions

10. Changes

11. Contact