NewSeatPlan for non-profits: charities get a free, co-branded Event Manager workspace for a year. Apply now →

Privacy & Data Protection

Privacy Policy

Last updated: 18 October 2026

Privacy Policy

This Privacy Policy explains how ZNZ Systems Ltd. ("we," "our," "us") collects, uses, and protects your personal data when you use SeatPlan.io - our web application (the "Service").

1. Information We Collect

If you do not sign up:

  • Your seating chart is stored only in your browser's local storage. It is automatically deleted at midnight and never transmitted to our servers.

If you email yourself a link to your chart:

When you ask us to email you a link to continue your chart on another device, we send that one email and keep the address with the chart, along with when we sent the link. We email you again only if you tick the box to agree and then open the chart from the link in that email, which confirms the address is yours. We record when you ticked the box and when you confirmed.

Once you have confirmed, we send at most two more emails about that chart: one when its free 48 hours end, and one two days before we delete it. A chart that has an address kept with it is deleted 30 days after it was last edited instead of 7. Each of these emails has an unsubscribe link, which stops them for every chart you asked about. We delete the address when its chart is deleted, unless you confirmed and have not unsubscribed, and you can ask us to delete it at any time.

If you sign up for an account:

  • We collect the following guest information you choose to enter:
  • • Name
  • • Email address
  • • Dietary requirements
  • • Comments
  • We also collect your account details through our authentication provider when you sign in.

If you use subscription features (templates, events, collaboration):

  • Templates and events you create, including event names, dates, and room configurations.
  • Guest seating data within your templates (names, dietary requirements, table assignments).
  • Collaboration invitations: email addresses of clients you invite to view or edit your seating charts.
  • Email engagement data: when collaboration invitation emails are opened or links are clicked.

If you use Guest Photos:

Guest Photos is an album a host buys for one seating chart, or an Event Manager buys for one event. Guests reach it through the seat finder QR code or their personal seat link, find their name, and share photos and short videos.

  • From guests who share: the photos and videos they upload; the name they pick from the guest list and its table; the date and time their phone reports for each photo or video, so the album can be sorted; a hashed device identifier, so their phone can manage its own uploads; and, for 48 hours only, a hashed form of their IP address to limit abuse. Guests do not create an account.
  • Location and camera details are removed. Every photo is re-encoded and stored without its embedded metadata (EXIF, XMP, IPTC), so GPS location and camera make and model are dropped. Every video is rewritten without its location, device and creation-time tags.
  • Who sees what: the host sees every upload, with the name of the guest who sent it. Guests see their own uploads and the photos the host chose to share with everyone, which show the sender's first name. Nothing in an album is public or indexed by search engines.
  • Event albums: an album bought for an event belongs to that event. Anyone who edits events in the Event Manager's organisation can manage it. The Event Manager may also give their client access by entering the client's email address; we keep that address to send the client single-use sign-in links, until the access is revoked or the album is deleted.
  • Hosts and buyers: we keep who bought the album and the payment details Stripe returns, as for any other purchase.

2. How We Use Your Information

We use your information to:

  • Provide and save your seating charts.
  • Allow you to manage guest lists and event planning.
  • Authenticate and secure your account.
  • Run Guest Photos albums: file each photo or video under the guest who shared it, show guests what the host shares, and limit abuse.

We never use Guest Photos photos or videos for advertising, to promote SeatPlan.io, or to train AI models, and we never sell them.

We do not sell or rent your personal information. If you accept optional analytics cookies, limited information may be shared with advertising partners we use for conversion measurement, as described in the Cookies and Analytics section below.

3. Cookies and Analytics

Cookies we use:

  • Essential cookies: Required for the site to function (authentication, session management). These cannot be disabled.
  • Guest Photos cookies (essential): each one is limited to a single album. gpc_<album> is a signed record of which guest you picked, so your uploads are filed under your name. gph_<album> keeps an event's client signed in for up to 7 days after they open their emailed link.
  • Analytics cookies (optional): When enabled, PostHog may set cookies for richer analytics and session replay, and we may load the Pinterest Tag, TikTok Pixel, Meta Pixel and Google Ads tag for ads measurement. Whether these are off or on by default depends on where you are located (see below); your explicit choice always takes precedence.

Where you are located:

  • EEA, United Kingdom, Switzerland, Turkey, and China: optional analytics and advertising cookies are off until you accept them via the cookie banner, which we show on your first visit.
  • Everywhere else (for example the United States): optional analytics and advertising cookies are enabled by default under an opt-out model, and we do not show the banner unless you ask for it. You can opt out at any time via the Cookie Preferences link in the footer and choosing Essential Only.
  • If we cannot determine your location, we treat you as if prior consent were required.
  • We honor the Global Privacy Control (GPC) signal: when your browser sends it, optional cookies stay off until you explicitly accept them.

Cookieless analytics (PostHog):

Whether or not you accept analytics cookies, we use PostHog for privacy-focused audience measurement. If you choose Essential Only or dismiss the banner, PostHog runs in cookieless mode: it does not set analytics cookies and uses a daily rotating identifier instead of tracking you across sessions.

  • Cookieless mode collects high-level usage such as page views, referrers, browser, device type, and country-level location, plus a limited set of funnel events.
  • We respect your browser's Do Not Track setting.
  • We keep standard campaign parameters (UTM tags) for attribution and exclude other URL search parameters and hash fragments before tracking.
  • Personal data (guest names, emails, event names, and similar) is removed before any data is sent.

Advertising measurement (Pinterest, TikTok, Meta and Google):

When analytics cookies are enabled (by your acceptance, or by regional default as described above), we may load the Pinterest Tag, the TikTok Pixel, the Meta (Facebook and Instagram) Pixel and the Google Ads tag to measure ad effectiveness and conversions. Pinterest, TikTok, Meta and Google may process a hashed form of your account email (and, for TikTok and Meta, your phone number if you added one) when you are signed in, and our servers may report sign-ups, checkouts and purchases directly to Pinterest, TikTok, Meta and Google with the same hashed details, the ad click identifiers from your visit, your IP address and your browser's user agent. This follows the same choice as the tags: on by default where no prior consent is required, and only after you accept where it is. None of this happens if you choose Essential Only.

Full analytics (PostHog with cookies):

When analytics cookies are enabled (by your acceptance, or by regional default as described above), PostHog (hosted in the US) may also set cookies to collect richer anonymised usage data such as features used and interaction patterns. This helps us improve SeatPlan.io.

  • We respect your browser's Do-Not-Track signal.
  • All personal data (names, emails, dietary information, guest details, table names, event names) is stripped before any data is sent to PostHog.
  • URL query parameters and fragments are removed before tracking.

Session recording:

Session replay is available only when analytics cookies are enabled (by your acceptance, or by regional default as described above). PostHog may record anonymised session replays to help us understand user experience issues. These recordings have the following safeguards:

  • All text on the page is masked — no guest names, emails, dietary information, or other personal data is visible in recordings.
  • All element attributes are masked — form values, input contents, and HTML attributes are hidden.
  • Recordings capture interaction patterns (clicks, scrolls, navigation) only, not your actual data.

Managing your preferences:

You can make or change your cookie choice at any time via the Cookie Preferences link in the footer, which re-opens the cookie banner. Your explicit choice is remembered and always overrides any regional default.

4. How Long We Keep Your Data

Basic account data:

  • Guest data is stored for 7 days after the expiry of your access.
  • If you do not extend your account, we delete your account and all associated guest data within 7 days.
  • If you have not signed up, your data is deleted automatically at midnight from your browser.

Subscription features (templates, events, collaboration):

  • Templates and events are stored while your subscription is active, plus 7 days after expiry.
  • Collaboration tokens expire after the duration you set (1-90 days).
  • Client email addresses from collaboration invitations are deleted immediately when the collaboration token expires.
  • Email engagement data (opens and clicks) is deleted along with the collaboration token.

Guest Photos:

  • An album is online for 12 months from its 11th photo or video. You can then view and download it for 30 more days, after which its photos, videos and guest names are deleted.
  • An album that never reaches its 11th photo or video is deleted 24 months after you bought it. A refunded album is deleted 7 days after the refund.
  • While an album is kept, your account is kept too. Your seating chart and guest list are still deleted 7 days after the chart's access ends. Only each guest's name and table stay with the album, so every photo keeps its name.
  • Your account is deleted 7 days after your last album is deleted, unless another plan keeps it. We email you before an album closes and before it is deleted.
  • For guests who share photos we keep the photo or video, the name they picked from the guest list, a hashed device identifier so their phone can manage its own uploads, and, for 48 hours only, a hashed form of their IP address to limit abuse.
  • An event album follows the same clock as a chart album. It stays available to the organisation's editors even if the Event Manager plan lapses, until the album is deleted.
  • When a host removes a guest from an album, or we erase a guest at their request, their photos, videos and name are deleted. We keep only a marker made of the album and the guest-list entry's random identifier, with no name, so the guest cannot be added back by mistake.

Operational retention and cleanup:

  • We may delete design sessions that are not linked to a user account after they have been inactive for a period (for example 7 or 30 days), as part of routine maintenance.
  • We may remove historical layout snapshots when they no longer relate to an existing session, for example after a session has been deleted.
  • We may delete user accounts that have no remaining paid or trial access after an extended period following expiry (for example more than 7 days), subject to safeguards such as outstanding billing checks.
  • We may delete accounts that have never purchased persistence or subscription features when they show no meaningful activity for at least 7 days.
  • If you started a checkout that did not complete, we exclude your account from routine cleanup of unpaid accounts for 30 days after that attempt so we can help you finish it. After those 30 days, the rule above applies again. We may then delete the account only if it has no paid or trial access and shows no meaningful activity for at least 7 days.
  • When you create a free account, we send you a short series of emails over about two weeks. While that series is running, we exclude your account from routine cleanup of unpaid accounts, for at most 21 days after the series starts. If you unsubscribe, or once the series ends, the 7-day rule above applies again.

5. Legal Basis for Processing (GDPR)

We process personal data on the following bases:

  • Contract: to provide you with the Service when you sign up.
  • Consent: when you voluntarily enter guest details into the application.
  • Consent: for PostHog analytics cookies and session recording in the EEA, UK, and Switzerland, which there require your explicit opt-in via the cookie banner.
  • Legitimate interest: for analytics cookies and advertising measurement in regions that do not require prior consent, where they run under an opt-out model with the Cookie Preferences control always available.
  • Legitimate interest: for essential cookies required for the Service to function.
  • Legitimate interest: for limited, cookieless audience measurement through PostHog when analytics cookies are not accepted.

6. Your Rights

Under GDPR, you have the right to:

  • Access a copy of your personal data.
  • Request correction or deletion.
  • Restrict or object to processing.
  • Request portability of your data.

You may exercise these rights by contacting us at hi@seatplan.io. We respond within one month of receiving your request, as required by Article 12(3). We will first confirm your identity through your registered email address, so that we never hand your data to someone else.

What you receive

An access or portability request returns an archive containing everything we hold about your account: your account details, every seating design and guest list, billing records, collaboration invitations and their delivery history, notification records, AI import usage, and the connection metadata (IP address, browser) we captured. It is provided as JSON, which is structured and machine-readable as Article 20 requires, together with spreadsheet-readable copies of your guest lists. The archive includes a manifest listing every category of data we considered and, where a category is not included, why. If you have Guest Photos albums, it lists them, their guest names and every photo and video, with download links that work for 7 days.

The archive contains your account and your own content, including the guest lists you created — for those you are the controller and we are your processor, so they are yours to receive. It never contains another customer's account data. It also does not include data held on our behalf by Clerk, Stripe, Resend, PostHog, or Sentry — ask us and we will obtain that for you.

If you shared photos as a guest

Photos and videos you share into a Guest Photos album are held for that album's host, who decides what happens to them. To remove yours, delete them from the album page in the browser you used, or ask the host. If you can't reach the host, email hi@seatplan.io and we will remove your photos, videos and name from that album. Once removed, you cannot share into that album again.

For an event album, the host is the event's organisation and the client they gave access to.

If you host albums, your data export includes them, with download links for your photos and videos that work for 24 hours.

What we keep after deletion

When you ask us to delete your account we remove it and everything associated with it, including designs you had previously deleted yourself. Two things are kept deliberately:

  • Invoices and payment records held by Stripe, which we are legally required to retain for accounting purposes (Article 17(3)(b)). Your Stripe customer record, including your saved payment methods, is deleted.
  • The internal record that your data was accessed or deleted, and by whom, kept for 24 months (Article 6(1)(c) and (f)).

Staff access to your data

Our staff can only access your data through an internal console restricted to SeatPlan.io administrators. Before looking up your account, generating a sign-in link for it, exporting your data, or deleting it, a staff member must record why they need it and how you contacted us.

That justification, and every internal action that reads or changes data identifying you, is written to an audit record that cannot be edited or deleted, and is kept for 24 months. Internal reports that contain only totals — for example how many customers are on each plan — are not recorded against you, because they do not identify you. You may ask us for the record of who has accessed your account.

7. Data Security

We apply technical and organizational measures to protect your data, including encryption at rest and in transit. Authentication is handled by our authentication provider, and application data for the Service is stored within AWS infrastructure in the Frankfurt region. Guest Photos photos and videos are stored with Cloudflare, Inc. in a private Cloudflare R2 storage bucket located in the United States. The bucket has no public address: every photo and video is reached only through a signed link that we create for a signed-in host or an identified guest, and that link expires within about an hour. Uploads go straight from the guest's phone to that bucket over an encrypted connection, and the database decides when each file is deleted.

8. Third Parties

We only share data with essential service providers acting as data processors:

  • Authentication provider – user sign-in and account management.
  • AWS (Frankfurt) – hosting, compute, primary storage for application data (including guest information), and real-time collaboration infrastructure for live updates and presence indicators.
  • Resend – email delivery for collaboration invitations, Guest Photos notices to hosts, and sign-in links for event clients. Resend may track when emails are opened and when links are clicked.
  • PostHog (US) – product analytics. Runs in cookieless mode without analytics cookies by default; with your consent, may also set cookies for richer analytics and session recording. All personal data is stripped before transmission. Text and element attributes are masked in session recordings.
  • Stripe – payment processing for subscriptions. Stripe processes your payment information directly; we do not store card details.
  • Cloudflare, Inc. (R2, United States) – stores the photos and videos guests share into Guest Photos albums, in a private bucket located in the United States that is not publicly accessible. Cloudflare stores the files on our behalf, under our instructions.

All providers comply with GDPR and implement adequate safeguards. For US-based providers (for example PostHog, Stripe and Cloudflare R2), and where our authentication provider processes data outside the EU/EEA, we rely on Standard Contractual Clauses (SCCs) or equivalent safeguards.

9. Collaboration Features

If you subscribe to our service, you may invite clients to collaborate on your seating charts:

  • You invite clients by entering their email address. We send them a unique, time-limited link to access your seating chart.
  • Clients can access your seating chart without creating an account.
  • You can revoke a client's access at any time.
  • Some elements of the seating chart may be restricted by you as the organiser.
  • We log when clients access the collaboration link for security purposes.

10. International Transfers

We aim to keep your data within the EU/EEA. If data is transferred outside the EU/UK, we use Standard Contractual Clauses (SCCs) or other legally required safeguards.

Guest Photos photos and videos are the exception. They are stored by Cloudflare, Inc. in a private storage bucket located in the United States, where most of the guests who share them are. If you are in the EU/EEA, the United Kingdom or Switzerland and you share into, or host, an album, those files are transferred to the United States. We rely on Standard Contractual Clauses with Cloudflare, together with Cloudflare's certification under the EU-U.S. Data Privacy Framework and its UK and Swiss extensions. The rest of the album's data (guest names, tables and the album's settings) stays in our database in Frankfurt.

11. Contact Us

For questions or to exercise your GDPR rights, contact us at: