プライバシーポリシー

This policy explains how Seat Down Please handles personal data. The short version:

• The organizer of an event decides why attendee data is collected and is the controller. We are the processor acting on the organizer’s behalf.
• For organizers’ own account data we are the controller.
• We do not sell personal data and we do not run ad tracking.

1. What data we handle

• Account: email, display name (from Google or entered by you) and sign-in method.
• Organizer content: events, ticket types, venues and seat maps, and the seating-plan images and PDFs you upload.
• Attendee data: name, email, tickets and seats, from Luma sync, free registration or entered by the organizer.
• Logs: sign-in and action logs, mail logs and error logs, used for security and troubleshooting.

2. Why we use it

To provide the Service (sign-in, seat maps, seat selection, check-in, notifications), to keep accounts and the Service secure, to fix problems and to answer your messages. We do not use data for advertising.

3. AI processing (Google Gemini)

When you upload a seating-plan image or PDF for AI recognition, the file is sent to Google Gemini through its API. When you use the AI chat editor, your messages and the current seat-map layout (seats, tables, labels) are sent as well.

We do not send attendee lists, emails or ticket data to the AI. If your image already has names written on it, they are sent too, so please cover them before uploading. How Google handles API content follows the terms that apply from Google at the time.

The original image is kept with your venue so you can re-run and check it, and is deleted when the venue is deleted.

4. Using venue data to improve seat map recognition

To make the AI draw seating plans more accurately, we keep the record of each venue import: the seating-plan images, PDFs or descriptions you upload, what the AI read and asked, your answers, your conversation with the AI and the changes it proposed (and which ones you applied or undid), your manual edits, and the seat map and total you finally saved. We use this to find recognition mistakes, compare models and improve how plans are read.

• This is on by default and explained on the upload page. You can turn off “Use my venue data to improve recognition” in account settings: nothing new is collected and what was already collected is deleted within an hour. An organization can also email us to leave out its whole workspace.
• This data stays in our own Cloudflare account, only our operations staff can access it, and it is never sold or given to other companies, nor used to train other companies’ models.
• It never includes buyer or attendee data (names, emails, tickets, payments). Seat names, descriptions and chat are text you wrote and may contain names; we mark those fields and always filter them before any outside use.
• When a venue is deleted, its import records are deleted too. The original uploads are kept for as long as the dataset record exists.

5. Luma integration

The organizer authorizes us with their own Luma API key. From Luma we read the event’s guests, ticket types and ticket status to produce seat-selection links and check-in lists, and we may adjust Luma ticket capacity as the organizer configures. The key is stored encrypted and never shown on a page.

Luma is the seller and payment processor, and payment details never pass through us. How Luma handles data is described in Luma’s own privacy policy.

6. Email delivery

Sign-in codes, seat invitations, tickets and reminders are sent through our email delivery provider (currently Cloudflare Email Service). The message and recipient address are kept in our outbox for retries and troubleshooting.

7. Providers and where data lives

• Cloudflare: hosting, database, file storage and email.
• Google: sign-in (if you choose Google), AI recognition and web fonts.
• Luma: only for events the organizer connects.

These providers may process data in the United States or other countries.

8. Cookies

We use only essential cookies: your sign-in session and language choice. There are no advertising or cross-site tracking cookies. Web fonts load from Google Fonts, so your browser connects to Google.

9. Retention and deletion

• Account and event data: kept until you or the organizer ask for deletion.
• Sign-in sessions and codes: expire and are purged regularly.
• Mail and action logs: kept for a reasonable period for security and audit (period to be decided).
• Venue import records (used to improve recognition): kept until you turn the setting off, delete the venue or ask for deletion.

To delete your account, venues, events or attendee data, email us. We confirm it is you first and aim to act within 30 days. Data in backups disappears as the backups rotate.

If you are an attendee and want to see or delete your data in an event, contact the event organizer first. You can also email us and we will help pass it on.

10. Your rights

Depending on where you live you may ask to access, correct, export or delete your data, or object to certain processing. Email us with your request.

11. Security

We use encrypted connections, access limits, audit logs and sign-in rate limits to protect data, but no system is perfectly secure. If you notice a problem please tell us right away.

12. Children and changes

The Service is not designed for children under 13.

When this policy changes we update the date and tell you separately about significant changes.