Privacy policy

Pre-launch policy template. The operator must add its legal identity, contact address, retention schedule, jurisdiction and processor agreements before accepting customer data commercially.

Last updated: 18 October 2026

Information we process

Seatovo stores your account email, event details, guest names, groups, RSVP status, dietary information, private notes and table assignments. Only enter information needed to organise your event. Dietary information may reveal sensitive health or belief information; obtain an appropriate lawful basis before recording it.

Why we use it

We process this information to provide authentication, event planning, exports and billing. We do not sell guest lists or use them for advertising.

Storage and processors

Authentication and event data are stored with Supabase. If billing is enabled, Stripe processes payments; Seatovo does not store card details. The deployment operator controls hosting and the selected data region.

Privacy and sharing

Events are private to their owner. Private notes are excluded from standard exports. Only share catering exports with authorised staff. The demo uses separate sample data in your browser session.

Retention and your choices

Records are retained while your account is active until you delete an event or account. There is no automatic event expiry. Export your data in Settings. Account deletion removes application records; provider backups follow their retention schedules. Billing records required by law may remain with Stripe. Contact the installation operator to request access, correction or assistance.

Cookies

Essential authentication cookies maintain your session. The demo uses session storage. No analytics or advertising cookies are installed by this application.

Contact

The operator must configure a privacy contact before launch.