In short
This policy explains what we collect, why, who sees it, how long we keep it and how to delete it.
Export or delete your dataDRAFT. For lawyer review. Not legal advice. The applicable Maldives law and any registration duties are not stated. See the points marked [LAWYER].
Tiket.ing Privacy Policy
Version [version]. Effective [effective date].
1. Who we are
[Pixel Haven legal name], [registered address] ("Pixel Haven") runs tiket.ing. Contact: [privacy contact email]. [LAWYER: confirm legal name, any registration, and any person we must appoint.]
2. Two roles
- For your account and the security of the platform, Pixel Haven decides why and how your data is used.
- For your booking with an organiser, and for people lists an organiser loads (for example a school's students), the organiser decides why and how the data is used. Pixel Haven stores and processes that data for the organiser. The organiser's own privacy notice applies too.
[LAWYER: confirm this split.]
3. What we collect
| Who you are | What we collect | Why |
|---|---|---|
| Customer with an account | Name, email, optional phone; sign-in details (Google identity ID, sign-in link records); device and session details with a hashed IP address | To give you an account, sign you in safely and show your tickets |
| Guest customer | Name, email, optional phone, for the booking | To confirm the booking and send tickets |
| Customer booking | Booking and ticket details, payment status and references (not card numbers), answers to the organiser's form, files you upload for the form or a bank slip | To complete and manage the booking for the organiser |
| Parent or guardian | The above, plus the link between you and your child at a school, and your requests (link, deletion) | To let you book for your child and manage the school's record |
| Student (where a school lets students book) | Name, school ID, grade, class, email if the school uses it | To book for yourself |
| Organiser staff | Name, email, role, sign-in and two-factor details, device registrations, and an audit trail of actions | To run the organiser's account safely |
| Everyone | Technical data: hashed IP address, browser type, error reports, request logs without personal content | To keep the service safe, find faults and prevent abuse |
Card numbers are entered on the payment gateway's page and are not stored by tiket.ing. [Confirm per gateway.]
4. Children's data (schools)
4.1 A school may load a list of its students and their parents or guardians. This is children's data. The school decides what it holds. We ask the school to hold the minimum: school ID, name, grade, class and, if needed, subjects.
4.2 We do not ask schools for date of birth, address, photo, ID number, medical information, religion or nationality. A school that adds such a detail takes responsibility for it, and the detail is marked private by default.
4.3 Only the school's staff with the right role can see a child's record. Private details need a separate permission. Teachers see only the conferences they host. Every time staff look at a child's record, the system logs who looked and when.
4.4 Children's names never appear in web addresses, in our logs, in error reports or in analytics. We do not use analytics on school pages.
4.5 The school sets how long it keeps children's data. When the time ends, the data is deleted automatically.
4.6 A school's staff can delete a child's data. A parent or guardian can ask the school to delete it from their account, and the school decides. Pixel Haven support can delete it when the school asks in writing.
4.7 Deleted data can stay in backups for up to [35 days] until they are replaced. [LAWYER]
4.8 [LAWYER: age at which a person is a child; whether parental consent is needed; what a school must tell parents.]
5. How we use data
To run the service (accounts, bookings, tickets, check-in); to send messages about your booking and account; to prevent fraud and abuse; to keep records the law requires; to improve reliability (using counts and error reports, not personal profiles); and to answer your requests. We do not sell personal data. We do not use it for advertising. [LAWYER: confirm the legal basis for each use.]
6. Who we share data with
- The organiser you book with, for your booking.
- Service providers who help us run the platform: Cloudflare (network, bot checks, file storage); Google (sign-in with Google, sending email); the organiser's chosen SMS provider (for example MessageOwl); the payment gateway the organiser uses (for example BML Connect or MIB); push notification providers (
[provider]); and our hosting provider ([hosting location]). - Authorities where the law requires. [LAWYER]
- Nobody else. We do not share one organiser's data with another organiser.
7. Where data is stored
[hosting location]. Some providers above may process data outside the Maldives. [LAWYER: state transfers and safeguards.]
8. How long we keep data
| Data | Time |
|---|---|
| Account | Until you delete it (with a short grace period) |
| Sign-in tokens | A day after they expire |
| Sessions | 30 days after they expire |
| Bookings, payments, invoices | [retention for financial records] |
| Contact details on old bookings | Removed [N] months after the event |
| Form answers and people lists | The period the organiser sets, then deleted |
| Import and export files | 7 days |
| Security and access logs | 24 months |
| Application logs and error reports | 30 days |
| Backups | Up to [35 days] |
[LAWYER: confirm each period.]
9. How we protect data
Each organiser's data is separated in the database. Payment credentials and signing keys are encrypted with a key kept outside the database. Platform staff use two-factor sign-in and can enter an organiser's account only for a recorded reason. We log access to children's data. Files are private and served through short-lived links. We use headers and checks to protect the site. No system is perfect. If something goes wrong with your data, we will tell the affected organisers [breach notice time] after we confirm it, and we will help them tell you. [LAWYER: breach duties.]
10. Your rights
Subject to the law, you can ask to see your data, correct it, export it, delete it, or object to its use. You can export your account data and delete your account in your account settings. For data held by an organiser (for example a school's list), ask the organiser. We will help them respond. [LAWYER: list the rights the law gives and how long we have to answer.]
To ask us: [privacy contact email]. To complain: [regulator]. [LAWYER]
11. Cookies and tracking
We use only the cookies needed to run the service (26.7). We use no advertising or analytics cookies. [Owner decision on analytics: OPEN-20-08.]
12. Changes
We will post changes here and tell you by email or in your account when the change matters. [LAWYER: notice.]
Earlier versions
Questions? Contact us