Privacy policy
In short
- Stored in the EU. Your workspace lives on Google Cloud in Belgium.
- Private to your account. No other customer can see it. Our admin screen shows plans and usage counts, never your content.
- Not used to train AI. We send what a request needs to Anthropic's Claude API, which by default doesn't train on it. We never sell personal data.
- Yours to control. Access, correct, delete, export or object at any time, and delete everything yourself from Account in the app.
- Your guests stay yours. For people who register through a form you publish, you are the controller and we only process their details for you. We never contact them ourselves.
This box is a summary. The sections below are what actually applies.
1. This policy and the GDPR
SeatCue is operated from Bulgaria, in the European Union, and we handle personal data under the EU General Data Protection Regulation (Regulation 2016/679, the GDPR) and the Bulgarian Personal Data Protection Act.
In practice that means five things you can hold us to:
- We only collect what the service needs, and we tell you what that is in section 3.
- We have a lawful basis for every use, set out in section 4.
- Your workspace stays in the EU, on Google Cloud in Belgium.
- We don't sell personal data, and the AI provider we use doesn't train its models on your data by default.
- You can access, correct, delete, export or object at any time, and complain to a regulator. See section 10.
If you are a customer and need a data processing agreement for your own compliance file, email frontrow@seatcue.ai and we'll send one.
2. Who is responsible
Inverted Digital Ltd, UIC 206353756, VAT number BG206353756, registered at 8 Starcin Str., Veliko Tarnovo, Bulgaria ("SeatCue", "we") is the controller for the personal data described in this policy. Contact us at frontrow@seatcue.ai or +359 88 351 7300.
When customers put personal data about other people into their SeatCue workspace, such as speakers, guests or contacts, the customer is the controller and we process that data on their behalf. Questions about that data should go to the organisation that added it.
3. What we collect
| Data | Examples | Source |
|---|---|---|
| Account data | Name, email, sign-in method | You, or Google when you sign in with it |
| Profile answers | Role, industry, organisation, city, types of events | You |
| Workspace content | Event briefs, brand kits, logos, photos, tasks, budgets, generated content, assistant messages | You and your team |
| Data about other people | Speaker names, photos and bios; guest and contact lists | Your organisation, with us as processor |
| Demo requests | Name, work email, company, role, events a year, plan of interest, message, the page you sent it from | You, through the form on this website |
| Files you upload to build a brand kit | A brandbook, presentation, one-pager or screenshots, read once to extract colors, fonts and tone | You |
| Guest and registration data | Details people enter on a registration form you publish, plus guest lists you upload: name, email, and whatever else you choose to ask for | The people who register, or you |
| Bug reports and suggestions | Your message, your email, the screen you were on, your browser | You, when you send feedback from the app |
| Usage and technical data | IP address, browser, log data, AI requests per account | Automatically |
| Website analytics | Pages viewed, clicks, approximate location, device type | Google Analytics, only if you accept analytics cookies |
| Billing data | Company details, VAT number, invoices | You |
We don't ask for special categories of personal data. Please don't put them in your workspace.
4. Why we use it and our legal basis
| Purpose | Legal basis under the GDPR |
|---|---|
| Create and run your account and provide the service | Performance of a contract, Article 6(1)(b) |
| Security, preventing abuse, fixing problems and improving SeatCue | Legitimate interests, Article 6(1)(f) |
| Reply to demo requests and follow up about them | Steps you ask for before a contract, and legitimate interests |
| Website analytics | Consent, Article 6(1)(a), which you can withdraw at any time |
| Invoicing, accounting and tax records | Legal obligation, Article 6(1)(c) |
5. AI processing
To generate content, SeatCue sends the information a request needs, such as your brief and brand kit, to Claude, an AI model provided by Anthropic through its commercial API. Anthropic processes this data as our service provider. By default, Anthropic doesn't use inputs or outputs from its commercial API to train its models.
Some features search the web for public information about venues, suppliers, companies and events. Review AI output before you use it.
6. Registration forms: who is responsible for what
SeatCue lets you publish a registration form for your own event. When someone fills it in, their details go into your workspace.
For that data, you are the controller and we are the processor. In plain terms: it is your data about your guests. You decide what to ask for, why, and how long to keep it. We only store and process it to run the service for you, and we act on your instructions.
- What you must do. Set consent wording that describes what you will use the details for, link to your own privacy notice on the form, ask only for what you need, and answer your guests if they ask for access or deletion.
- What we do. Store the entries in the EU, keep them private to your workspace, never contact your guests ourselves, never sell or share their details, and never use them to train AI models.
- Consent is recorded. Each entry stores the exact wording shown and the moment the box was ticked, so you can evidence consent if you are ever asked.
- Deletion. Delete a guest in the app and the entry goes. Delete your workspace and everything goes with it.
If you need a data processing agreement for your compliance file, email frontrow@seatcue.ai and we'll send ours, or work from yours.
7. Who can see your workspace
Your workspace is private to your account. Other SeatCue customers can never see it: the database refuses any request for another account's data.
Inside SeatCue, two different things are worth separating:
- What our admin screen shows. The team running SeatCue sees a list of accounts with the name and email used to sign up, the sign-in method, when the account was created, when it was last used, the plan and its end date, and how many AI requests the account made this month. It does not show the content of your events, your briefs, your guests or anything you generated.
- What technical administrators can reach. We operate the database your workspace is stored in, so a small number of named people at SeatCue can technically open stored records, including workspace content. We do this only to fix a fault you've reported, to investigate a security problem or suspected abuse, or where the law requires it. We don't read workspace content to browse it, to build our own event ideas, or for marketing.
Access is limited to people who need it to run the service, everyone with access is bound by confidentiality, and Google Cloud keeps administrative access logs. If you'd like a copy of your data or want it deleted, see your rights below.
8. Who we share data with
We don't sell personal data. We share it only with:
- Google Cloud and Firebase for hosting the app, the database and sign-in. Workspace data is stored in the EU (Belgium).
- Anthropic for AI processing, as described above.
- Our website hosting and email providers for hosting this website and receiving demo requests. Demo requests are emailed to us and a backup copy is kept on our web server.
- Google for Google Analytics on this website, only if you accept analytics cookies.
- Your organisation: people on your team can see shared workspace content.
- Authorities or professional advisers where the law requires it or to protect our rights.
9. International transfers
Some of our providers may process data outside the European Economic Area, including in the United States. Where they do, we rely on an adequacy decision such as the EU-US Data Privacy Framework, or on the European Commission's standard contractual clauses, with additional safeguards where needed.
10. How long we keep it
- Account and workspace data: while your account is active, then deleted within 30 days after you close it, and from backups within a further 35 days.
- Demo requests from people who don't become customers: up to 24 months.
- Invoices and accounting records: as long as Bulgarian accounting and tax law requires.
- Security and usage logs: up to 12 months.
- Analytics data: up to 14 months in Google Analytics.
11. Your rights under the GDPR
You can ask to access, correct, delete, restrict or port your personal data, object to processing based on legitimate interests, and withdraw consent at any time without affecting earlier processing. Email frontrow@seatcue.ai and we'll respond within one month.
You can also complain to the Bulgarian Commission for Personal Data Protection (www.cpdp.bg) or to the supervisory authority where you live or work.
To delete your account and workspace data, open Account in the app and choose Delete account data, or email frontrow@seatcue.ai from your account email.
12. Cookies
We use essential storage to run our website and app, and Google Analytics cookies on our website only if you accept them. The full list, how long each lasts and how to change your choice are in our cookie policy.
You can change your choice at any time with .
13. Security
We use encryption in transit and at rest, access controls and least-privilege permissions. No system is completely secure; if a personal data breach affects you, we'll tell you as the law requires.
14. Children
SeatCue is a business service and isn't intended for anyone under 18.
15. Changes to this policy
We'll post updates on this page and change the date at the top. For material changes we'll also tell account owners by email or in the app.