Legal

Privacy Policy

Last updated October 24, 2026

Who we are

SeatMe is a seating planner for events, built and run by Esther Gross, who is responsible for the personal data described here (the "controller" under the GDPR). You can reach us about anything in this policy at esther@gross.gg. SeatMe has no advertisers, doesn't sell data, and doesn't use it for advertising.

If you're a guest

Hosts use SeatMe to plan their events, so your name and details may be here because a host added them. The host decides what to record about their guests and is responsible for having a good reason to, and SeatMe stores it for them. If you RSVP through a SeatMe link, the RSVP page only checks your name against the guest list; it never shows you anything else the host has written about you.

For questions about what a host has recorded about you, ask the host first. You can also contact us at esther@gross.gg and we'll help.

What we collect and why

Your account. Your email address, and a password if you choose one (you can also sign in with an emailed link). Optionally your first and last name and a recovery phone number, if you add them. Used to run your account.

Events and guests. Everything a host enters: the event's name, date and location, guest names, groups, emails, notes, tables, seating rules and seat assignments. Guest notes can include things like dietary needs or accessibility requirements; hosts should only record what's needed for the event. If you invite collaborators, we store their email address and role.

RSVPs. When a guest RSVPs through a host's link, we store their answer, meal choices and, if the host turned comments on, their comment. To limit misuse, we count RSVP attempts per visitor using a one-way code made from their IP address, never the address itself, and delete those counts within 2 days.

Uploaded files. Venue floor plans and menus you upload. They're stored privately: only people with access to the event (or, for saved venues, you) can open them.

Site visits. On our public pages we log the page, the referring site, any campaign tags in the link, and your browser type. To count distinct visitors we store a one-way code made from your IP address, browser and the date. It changes daily, so it can't follow you across days, and we never store your IP address. We also use Vercel Web Analytics, which counts page views without cookies.

Usage records. Basic logs of when you sign in, import a guest list or use the assistant, and a daily count of AI requests per account so we can apply fair-use limits.

Emails. If you sign up but don't get started, we may send one reminder with a sign-in link.

Feedback. Anything you send through the feedback form.

Our legal bases

We process account, event, RSVP and file data to provide the service you or your host asked for (a contract, GDPR Art. 6(1)(b)). Site-visit statistics, usage limits, security logs and the reminder email rely on our legitimate interest in running, protecting and improving SeatMe (Art. 6(1)(f)); you can object to these at any time. Connecting Pinterest and using the AI features are your choice each time.

AI features

When you use the assistant, ask SeatMe to read a floor plan or menu, or get decor suggestions, the relevant event data, file or Pinterest images are sent to Anthropic's Claude API to produce the answer. This only happens when you use those features. Anthropic processes this data on our behalf and doesn't use it to train its models.

Pinterest (optional)

If you connect Pinterest to an event, we store the access tokens for that connection on our servers. They are never sent to anyone's browser, and we use them only to read the board you select. SeatMe never posts, edits or deletes anything on Pinterest. You can disconnect at any time from the event.

Who processes data for us

  • Supabase: database, file storage and sign-in. Data is stored in the EU (Ireland).
  • Vercel: hosts the app, serves our images and fonts, and provides cookie-free page analytics.
  • Anthropic: the AI features described above.
  • Pinterest: only if you connect it.

Vercel and Anthropic are based in the United States, so some data is processed outside the EU. Those transfers rely on safeguards the GDPR recognizes, such as the European Commission's Standard Contractual Clauses or the EU-US Data Privacy Framework, as offered by each provider. Fonts and photos on SeatMe are served from our own domain, so your browser doesn't contact Google or Unsplash.

Cookies

SeatMe only uses cookies that are strictly necessary: one to keep you signed in, and a short-lived one that protects the Pinterest connection step. No advertising or tracking cookies, so there's no cookie banner.

How long we keep data

  • Accounts: until you ask us to delete yours.
  • Accounts never confirmed by email: deleted after 30 days.
  • Events, guests and RSVPs: until the event is deleted. Its uploaded files are removed within a few days.
  • Site-visit logs: 12 months.
  • AI and RSVP usage counts: 2 days.
  • Pinterest tokens: until you disconnect Pinterest or delete the event.
  • Feedback: as long as we need it to follow up.

Your rights

You can ask to access, correct, delete or export your personal data, to restrict how we use it, or object to processing based on our legitimate interests. Email esther@gross.gg and we'll respond within one month. You can delete guests and whole events yourself at any time in the app.

You also have the right to complain to a data protection authority. In France that's the CNIL (cnil.fr); elsewhere in the EU, your local authority.

Security

Access to every event is checked on our servers and in the database itself, files are private, and connections are encrypted. If a breach ever affected your data, we'd notify the authorities and, where required, you.

Children

SeatMe accounts are for adults. Hosts may list children as guests (for a family wedding, say); please record only what the event needs.

Changes to this policy

When this policy changes, we'll update the date at the top of this page.

Contact

Questions about this policy or your data? Email esther@gross.gg.