Privacy policy

1. About this page

This is sample text for a demo project. It is not a real privacy policy and not legal advice. It describes what this demo stores.

2. Data stored

The demo database stores the following, only to make the features work:

• Account: name or nickname, email, a hashed password, role (buyer, organizer or admin) and, if you add them, a photo and organizer profile details.
• Orders, simulated payments, tickets and refunds, including seats and check-in status.
• Likes, comments and notifications.
• Messages between organizers and administrators.
• Events, venues and images created by organizers.

3. Payments

No payment details are collected. There is no card form, and no payment provider receives anything.

4. Cookies and local storage

Ticketzy does not set cookies of its own. It uses the storage of your browser:

• Local storage: the login token (accessToken), your language (locale), your theme (ticketzy-theme) and whether you closed the demo notice (ticketzy-demo-notice).
• Session storage, which is cleared when the tab closes: the assistant conversation (ticketzy-assistant), a clock offset for the seat countdown (tz:clock-skew) and unsent form drafts.
• You can clear all of it in your browser settings. You will then need to log in again.

5. AI assistant

Text you type to the assistant is sent to the Ticketzy server, which asks an AI model for the reply. Do not type personal, payment or secret information.

6. Sharing

Your data is not sold and not shared with advertisers or analytics services. Organizers see the orders and attendees of their own events. Comments, likes and organizer profiles are visible to other visitors.

7. Keeping and deleting

Demo data can be reset at any time. There is no self-service account deletion in this demo. Ask through the contact page.

8. Contact

Use the contact page for questions about this sample policy.