Privacy Policy
Last updated: October 2026 (placeholder)
1. Who is responsible for your data
091 Solutions, Galway, Ireland operates EasyBook. [PLACEHOLDER: contact email for privacy requests and, if applicable, Data Protection Officer details.] This policy is written with the EU General Data Protection Regulation (GDPR) in mind.
2. Controller and processor roles
For organiser account data we are the controller. For the personal data of an organiser's customers (names, emails, bookings), the organiser decides why and how it is used and is the controller; we process it on the organiser's behalf. [PLACEHOLDER: confirm roles and add a data processing agreement if needed.]
3. What we collect
- Organiser details: name, email, business name, contact details, country and timezone.
- Customer details given when booking: name, email, phone (optional) and booking details.
- Technical data: basic page-view counts per site and security logs. We keep a log of transactional emails we send for each site (for example booking confirmations), which includes the recipient email address, so organisers and support can see what was sent. Application and error logs are kept free of email addresses. [PLACEHOLDER: confirm email log retention.]
4. Payments
Card payments are handled by Stripe. We do not see or store card numbers. Stripe acts under its own privacy policy. We receive payment status and amounts so we can show bookings and calculate the platform fee.
5. Why we use data, and the legal basis
To provide the service and run bookings (contract), to keep the platform secure and prevent abuse (legitimate interests), and to meet legal obligations such as tax records. [PLACEHOLDER: confirm the legal bases.]
6. Service providers
We use Google Firebase (authentication and database), Stripe (payments), Resend (email) and Vercel (hosting). [PLACEHOLDER: list international transfers and safeguards.]
7. Retention
[PLACEHOLDER: retention periods for bookings, accounts and logs.]
8. Cookies and local storage
[PLACEHOLDER: describe cookies and browser storage. Firebase Authentication stores a sign-in session in your browser's storage (such as IndexedDB or local storage) while you are signed in, and some preferences, such as dismissing a notice, are kept in local storage. State whether any analytics or marketing cookies are used and whether a consent banner is required.]
9. Where data is hosted
[PLACEHOLDER: state the Firebase/Firestore, Vercel and Resend hosting regions, whether data stays in the EU/EEA, and the safeguards (for example Standard Contractual Clauses) for any transfers outside it.]
10. Your rights
You may ask to access, correct, delete or export your data, to object to or restrict processing, and to complain to the Data Protection Commission (Ireland). Customers of an organiser should contact that organiser first.