FullSeat AI

Privacy Policy

Last updated October 17, 2026

FullSeat lets businesses create AI sales agents that present on video calls with their prospects. It is operated by OrgFrame AI Inc ("we", "us"). This policy explains what we collect when you use the FullSeat website and service, why, how long we keep it, and the choices you have. We collect what we need to run the service and keep it only as long as we need it.

Two kinds of people use FullSeat: customers (the businesses and their staff who create agents, with an account) and prospects (the people those agents meet, who book or join a meeting without an account). Where a section applies to one of them only, it says so.

The short version

  • Meetings are transcribed, not recorded as video. What is said in a meeting is turned into text live so the agent can respond; the transcript and a summary are kept for the customer whose agent held the meeting. We do not store the audio or video of the call.
  • Prospects are told who they are talking to. The agent is presented as an AI agent of the customer's business.
  • We do not sell personal data, show advertising based on it, or use meeting content, portraits or voices to train AI models.
  • Payments are handled by Stripe. We never see or store full card numbers.

What we collect from customers

  • Account details: your name and email address, and either a password (stored only as a secure hash by our sign-in provider, Neon Auth) or your Google sign-in. With Google we receive your name, email address and profile picture and nothing else; we do not read your calendar, mail or contacts through sign-in.
  • Organisation and billing: your organisation's name, the plan it is on, invoices and usage (meetings held and their length). Card details go directly to Stripe; we keep Stripe's customer and subscription identifiers.
  • Agents: everything you give an agent: its name, title, personality, company and product knowledge, pricing, slides, documents, videos, scripts, demo sequences and credentials for demo environments. Demo credentials are stored encrypted. This content is sent to AI models during meetings so the agent can present and answer.
  • Portraits and voices: the appearance you pick for an agent (one of our library portraits or a photo you upload) is sent to our avatar provider, PortraitFlow, which animates it and designs a synthetic voice from the picture and your description. The voice is generated, not a recording of anyone. Upload only photos you have the right to use (see the Terms of Service).
  • Integrations you connect: if you connect a CRM (HubSpot, Pipedrive or Salesforce), a calendar or an email account, we store the access tokens needed and exchange the meeting, prospect and follow-up data you ask us to sync. You can disconnect an integration at any time in Settings, which stops the exchange.
  • Usage and technical data: sign-in times, the actions taken in the dashboard, and limited technical logs (addresses, browser type, errors) that help us keep the service running and secure.
  • Cookies: a sign-in session cookie, and small preferences. We do not use advertising or cross-site tracking cookies.

What we collect from prospects

  • Booking and intake details: the name, work email, company and anything else you enter when you book a time or join a meeting through a customer's link. The customer whose agent you meet sees this.
  • The conversation: during the meeting your speech is converted to text live and sent, with the agent's instructions, to the AI model that decides what the agent says next. Your camera video is shown to the agent's system for presence detection and is not stored. The transcript, the agent's notes (questions you asked, objections, interest) and a summary are kept and shared with the customer. Audio and video of the call are not stored.
  • Follow-up: if you ask for information or agree to be contacted, the customer may email you through FullSeat; we keep those emails as part of the meeting record.
  • Technical data: the address and browser used to join, for security and troubleshooting.

FullSeat processes a prospect's information on behalf of the customer whose agent they met. That customer decides how long the meeting record is kept and answers requests about it; write to them first, or to us at support@fullseat.ai and we will pass the request on.

Who processes data for us

We use service providers to run FullSeat. Each one receives only what its job needs, under agreements that limit its use to providing the service to us:

  • Neon (database and sign-in), Fly.io and Cloudflare (hosting, networking, file storage).
  • LiveKit (real-time audio and video for meetings) and Daily for some meeting rooms.
  • AI model providers (Google Gemini, OpenAI, Anthropic, Voyage AI) that transcribe speech, write the agent's replies, summarise meetings and index documents. Under our agreements with them, content sent through their APIs is not used to train their models.
  • PortraitFlow (the animated avatar and its synthetic voice; receives the portrait and the text the agent speaks, never the prospect's audio).
  • Browserbase (cloud browsers for recorded product demos) and Mailgun (email delivery).
  • Stripe (payments) and Google (optional sign-in; the calendar and CRM services a customer chooses to connect).

We do not sell personal data and do not share it with anyone for their own marketing.

How long we keep things

  • Accounts, organisations and agents: until you delete them or close the account. Deleting an agent deletes its content, portrait registration and voice.
  • Meeting transcripts, notes and summaries: for as long as the customer keeps them; a customer can delete a meeting record at any time.
  • Prospect booking details: with the meeting record they belong to.
  • Billing records: for the period tax and accounting law requires.
  • Technical logs: a short rolling period, normally under 30 days.

Your choices and rights

  • Access, correction and deletion: customers manage their account, agents and meeting records in the dashboard; write to us for anything the dashboard does not cover. Prospects may ask the customer they met, or us, to see or delete their meeting record.
  • Google sign-in: you can remove FullSeat's access at any time in your Google Account's security settings; your account then needs a password to sign in. FullSeat's use of information received from Google APIs follows the Google API Services User Data Policy, including its Limited Use requirements.
  • Integrations: disconnect any connected service in Settings.
  • Marketing email: we send service messages only; there is no marketing list to opt out of.
  • Depending on where you live you may have further rights (for example under the GDPR or the CCPA) to object to or restrict processing, to data portability, and to complain to a supervisory authority. We honour them on request at support@fullseat.ai.

Security

Data travels over encrypted connections and is stored with providers that encrypt it at rest. Access inside OrgFrame AI Inc is limited to the people who operate the service. Demo credentials are encrypted before storage. No system is perfectly secure; if we learn of a breach that affects you, we will tell you and the authorities as the law requires.

Children

FullSeat is a business service and is not directed at children under 16. We do not knowingly collect their information; if you believe a child has provided some, write to us and we will delete it.

International transfers

We are based in the United States and our providers run there and in other countries. Where the law requires, transfers rest on standard contractual clauses or an equivalent safeguard.

Changes

When this policy changes in a way that matters, we update the date above and tell customers by email or in the dashboard before the change takes effect.

Questions? Write to support@fullseat.ai. See also our Terms of Service.