Version 2026-08-16
Privacy notice
How Tika uses buyer, account and organizer information.
Pre-launch draft. Insert the controller's registered identity, privacy contact and approved retention schedule before launch.
Data we process
We process account identity, organizer and event information, buyer name and email, order and payment references, issued-ticket and check-in records, security logs, support messages and required technical identifiers. Tika does not need to store full payment-card details when hosted payment pages are used.
Why we process it
Information is used to create accounts, sell and deliver tickets, control admission, communicate event changes, prevent fraud, process refunds, support users, maintain accounting records and meet legal obligations. Optional marketing requires a separate choice and is not a condition of purchase.
Who receives it
Data may be shared only as needed with the responsible event organizer, payment and email providers, hosting and security suppliers, professional advisers and competent authorities. Organizers receive only information necessary to deliver their event and support attendees.
Retention and security
Records are kept only for the documented operational, accounting, dispute and legal periods that apply to them, then deleted or anonymized. Access is role-based and important administrative actions are audited.
Your choices and rights
You may request access, correction, deletion, restriction, portability or objection where applicable, and may complain to the competent data-protection authority. Some records must still be retained when required by law or an unresolved transaction.
Cookies and sign-in
Strictly necessary cookies keep sessions and checkout secure. Analytics or marketing cookies must remain disabled until separately accepted. Google sign-in is optional and is governed by Google's own privacy information in addition to this notice.