Last updated August 30, 2026
Two kinds of data pass through Head Table: yours, and your guests'. They are governed differently, and this page says how.
Head Table is operated by Sesh Music LLC, a New York limited liability company. This policy covers headtable.live, the editor, share links, and the exports the product produces.
The split that matters: for your account — your email, your plan, your billing record — we decide what happens to the data, and we answer for it. For the guest lists you upload, you decide, and we only act on your instructions. In the language regulators use, you are the controller of your guest data and we are your processor. Section 10 sets out the terms we hold that data under.
The dietary field is open on purpose — “Kosher”, “Halal”, “Jain”, and “severe nut allergy” all have to survive contact with a caterer. That openness means the field can hold information about a guest's religion or health, which most privacy laws treat as a special category needing extra care.
We store it, render it on plans and place cards, print it on kitchen reports, and do nothing else with it. We do not profile on it, sell it, or train anything on it. Because you put it there, the lawful basis for holding it is yours to establish — usually the explicit consent your couple or client collected on their RSVP. Keep notes to what the kitchen and the room need; the notes field is not the place for a medical history.
One consequence worth knowing before you send a link: dietary requirements and meal choices are visible to anyone holding a share link, including view-only links. Guest notes are not — we strip them from every shared view.
We do not sell personal information, and we do not share it for cross-context behavioral advertising, as California uses those terms. We have never done either, and there is no mechanism in the product that could.
Four vendors, each doing one job, none of them permitted to use your data for their own purposes:
Beyond those, we disclose data only when the law requires it, and we will tell you before we do unless we are legally barred from it. If the business is ever sold or merged, your data moves with it under this policy, and we will say so in advance.
A share link carries a random 128-bit token — it is unlisted, not guessable, and not indexed. Anyone holding it sees the plan at the role you granted: view, comment, or edit. Revoking a link in the editor kills it immediately.
Treat a link as you would a printed seating chart: once it leaves your hands you cannot control who reads it, so send it to the people who need it and revoke it when the event is over.
Only the cookies that keep you signed in. No analytics, no advertising pixels, no third-party trackers, no cross-site profiling — which is why you have never seen a cookie banner here, and why you will not.
Wherever you live, you can ask us to show you what we hold, correct it, export it, or delete it, and you can object to processing or ask us to restrict it. Email hello@headtable.live from your account address and we will answer within 30 days. We do not charge for this, and we will not treat you worse for asking.
If you are a guest rather than a customer — your name is on someone else's seating chart — the planner who uploaded you decides what happens to that record. Write to us at hello@headtable.live and we will route your request to them and support them in answering it.
UK and EU residents may complain to their local supervisory authority. Data is stored in the United States; where transfers out of the UK or EEA need a legal basis, we rely on the European Commission's standard contractual clauses and the UK addendum.
When you upload guest data, these terms apply and form our data-processing agreement. We will: process guest data only to provide the service and on your documented instructions; keep everyone with access under confidentiality obligations; apply the security measures in section 11; use only the sub-processors named in section 5 and give you notice before adding another; help you answer guest requests and regulator questions; delete or return guest data when your account closes; and make available the information you need to verify all of this.
The subject matter is seating and catering planning, the duration is the life of your account, and the categories are event guests and the attributes in section 2. If your client needs a countersigned agreement on their own paper, email hello@headtable.live and we will sign one.
Access is enforced in the database itself with row-level security, so one account cannot read another's events even if the application is wrong. Data is encrypted in transit and at rest. Share tokens are generated with a cryptographic random source. Payment credentials never touch our infrastructure.
No system is perfect. If a breach affects your data, we will tell you without undue delay and within 72 hours of becoming aware where the law sets that clock, and we will tell you what happened, what was affected, and what we did — not that we take your privacy seriously.
Head Table is a professional tool and is not for anyone under 16. We do not knowingly create accounts for children. Guest lists routinely include children as seated guests, entered by an adult planner — that is the only way a child's name reaches us, and it stays limited to name, meal, and seat.
If we change this policy in a way that matters, we will email account holders and update the date at the top before it takes effect. Questions, requests, and complaints all go to hello@headtable.live, and a person answers them.