Privacy Policy
Last updated: November 2026
This policy explains what FindYourSeat knows about you, what it does with it and what you can ask us to do. It covers two groups of people: organisers, who have an account and build seating charts, and guests, whose names an organiser has added to an event.
Who we are
FindYourSeat is operated by [LEGAL ENTITY NAME], [POSTAL ADDRESS]. For anything about your personal data write to privacy@findyourseat.app. For everything else write to support@findyourseat.app.
What we hold about organisers
- Your account. Your email address and a hash of your password (we cannot read the password itself). If you add a passkey we store its public key and identifier, never its private key; your fingerprint, face or device PIN never leaves your device.
- Your profile. Your name and any other details you choose to add on the account page.
- Your events. Event names, dates and venues, floor plans, guest lists, seat assignments and the messages you write for guests.
- Your plan. Which plan you are on, its status, and the references and invoice amounts Stripe gives us. We never receive or store your card number.
- Messages you send us. Feedback you submit on the site and email you send to us.
- Technical records. Our server records requests (IP address, browser type, the address requested and the time), sign-in attempts, and a log of account, security, billing and admin actions. We use these to run the service, find faults and stop abuse. How long each is kept is listed under "How long we keep it".
If you joined the waiting list before launch, we hold the email address you gave us, when you joined, the IP address you used and your browser's identification (its name and version and your operating system). We use the address only to tell you about the launch; the IP address and browser identification help us spot misuse of the form.
What we hold about guests
Organisers add their guests to an event. For each guest that is a name and, if the organiser chooses to add them, an email address and a phone number, plus the table and seat the guest is given. The organiser decides what to add and is responsible for having the right to share it with us. We hold this information on the organiser's behalf and use it only to provide the seating chart.
Every event has a public page, opened with the event's code or QR code. Anyone who has the code can search that page by name and see a matching guest's name, table and seat. If the organiser wrote a message for you, it is shown after you find your seat. A guest's email address and phone number are never shown on the public page.
If you are a guest and want your details corrected or removed, ask the event's organiser, or write to privacy@findyourseat.app and tell us which event it is.
How we use it
- To provide the service: sign you in, store your events and show guests their seats.
- To take payment for paid plans and apply the right plan to your account.
- To send you email about your account, such as address confirmation and password resets.
- To keep the service secure and working.
We do not sell personal data. We do not show advertising. We do not use analytics or advertising trackers, and we do not use your events, guest lists or public pages to promote FindYourSeat.
Who else receives data
| Company | When | What it receives |
|---|---|---|
| Stripe | When you buy or manage a paid plan | Your email address, the plan you chose and the payment details you type on Stripe's own pages. Card numbers go to Stripe only; they never reach our server. |
Email is sent through our own mail server (kod.us), not through a mailing company. It handles the recipient's address and the message, and tells us when a message bounces or is reported as spam. We give personal data to others only as set out above, or when the law requires us to.
Where it is kept
Accounts, events and guest lists are stored in a database on our own server in the United States. If you use FindYourSeat from another country, your data is transferred to and kept in the United States.
Cookies and browser storage
We use only what the site needs to work. There are no tracking cookies, so there is no cookie banner to answer. The Cookie Policy says more.
| Name | Kind | What it is for | How long it lasts |
|---|---|---|---|
| Sign-in cookie (fys_auth) | Cookie | Set when you sign in. It tells the site that the following requests come from you, so you stay signed in. Scripts on the page cannot read it. | Until you sign out. With "Keep me signed in" it lasts 14 days from your last visit; without it, it ends when you close the browser, and at the latest 14 days after your last visit. |
| Request-check cookie (fys_csrf) | Cookie | Set when a page contains a form. It lets the site reject a form that another website tries to submit in your name. | Until you close the browser |
| theme | Browser storage | Your choice of the light or the dark theme. It stays in your browser and is never sent to us. | Until you clear the site's data |
| fys.profilePromptDismissedUntil | Browser storage | The time until which the "finish your profile" reminder stays hidden after you dismiss it. It stays in your browser and is never sent to us. | 7 days after you dismiss the reminder |
How long we keep it
- We keep your account, events and guest lists for as long as your account is open.
- Deleting an event hides it; it does not erase it. A deleted event can no longer be opened by you or through its public page, but the event and its guest list stay in our database.
- To have an event, a guest list or your whole account erased, write to privacy@findyourseat.app from the email address of your account.
- Stripe keeps payment records under its own policy.
- The records below, which the server keeps to run the service, are deleted on this schedule:
| Record | What it holds | How long it is kept |
|---|---|---|
| Passkeys | For each passkey you add: its public key and identifier, the kind of authenticator, the name you gave it, and when it was added and last used. The private key stays on your device or in your password manager; we never receive it. | Until you remove the passkey or your account is erased |
| Email links | For each verification or password-reset link we send: a hash of its code (not the code itself), the account and when it expires. | Deleted one day after the link expires |
| Sign-ins | For each browser signed in to an account: a hash of its session code (not the code itself), the account, when it signed in, when it was last used and, after a sign-out, when and why it ended. No IP address or browser details. | Deleted one day after the sign-in cookie would have expired, whether or not you signed out sooner |
| Sign-in attempts | For each attempt to sign in: the account (when the address is known), whether it worked, the IP address and the time. | 90 days |
| Audit log | Account, security, billing and admin actions: which account did what and when, with the IP address for actions taken on the site. | 365 days |
| Outgoing email | For each email we send through our own mail server (kod.us): the recipient's address, the subject, the kind of message and whether it was sent. The message text is deleted as soon as the message has been sent or can no longer be sent. | 90 days |
| Email block list | Addresses that unsubscribed from the waiting list, whose mail bounced permanently or that reported our mail as spam, with the reason and the date, so that we do not send that mail to them again. | An unsubscribe entry until the address joins the waiting list again. Bounce and spam entries with no end date, because removing one would let the mail start again; write to us to have one removed. |
| Waiting list | The email address you gave, when you joined, the IP address you used and your browser's identification (its name and version and your operating system, as your browser reports them). | No end date is set yet. Unsubscribing stops the mail and marks the entry as unsubscribed, and joining again starts it again; write to us to have it deleted. |
| Health checks | Results of the site's own checks of its database and services. No personal data. | 30 days |
What you can ask for
You can ask us for a copy of the personal data we hold about you, to correct it, or to erase it. Depending on where you live you may have further rights, including the right to complain to your data protection authority. Write to privacy@findyourseat.app. We may ask you to show that the request comes from you.
Security
The site is served over HTTPS. Passwords are stored as hashes. The sign-in cookie cannot be read by scripts on the page. Card payments are handled entirely by Stripe. No system is perfectly secure; if we learn of a breach that affects you, we will tell you.
Changes to this policy
When we change this policy we change the date at the top. If a change affects how we use data we already hold about you, we will tell you by email before it takes effect.
Contact
[LEGAL ENTITY NAME]
[POSTAL ADDRESS]
Privacy: privacy@findyourseat.app
Support: support@findyourseat.app