A private conversation.

Information you provide

Before the demo, you may optionally provide your first name, offer, audience, monthly booked-call or new-lead volume, and current process challenge so the agent can start with useful context. These details remain in the open page, are sent only when you start the live session, and are not placed in the page URL or browser storage. If you skip this step, the agent asks for the relevant context conversationally. Anything you enter or say is processed by OpenAI as part of the live voice session. Setters.ai does not separately save the optional prep form answers to a database, CRM, or mailing list. Details repeated in the conversation can be included in its recording and transcript.

Voice processing

If you start the demo and grant microphone permission, your browser sends microphone audio directly to OpenAI's Realtime service so the agent can respond. OpenAI generates a live transcript displayed in the page. Public Confirmations and Setting demos may be recorded automatically: Setters.ai saves visitor and agent audio, transcripts, and session milestones in private storage for quality review and improvement. Recordings and transcripts may include names, email addresses, or other details spoken during the demo. They are retained until manually deleted; contact us below to request deletion. Access is restricted to authorized operators. Internal QA and simulated booking demos are not recorded by Setters.ai. OpenAI processes the supplied details and audio under its applicable API data controls and retention terms. If you choose to book by voice, the name and email you say are also processed by OpenAI so the agent can complete the requested action.

Session lifecycle

The demo uses a short-lived credential that cannot expose the permanent server API key. Closing or refreshing the page discards the in-page prep details and stops microphone access. Audio and transcript portions already saved remain in private storage; interrupted uploads may leave an incomplete recording. Both public product demos can collect a name and email by voice, check real availability, and create a Google Calendar event only after explicit spoken confirmation. Internal QA demos use simulated availability.

Calendar bookings

For a real booking, Setters.ai temporarily stores the confirmed name, email, offered times, campaign attribution, and booking status for up to 30 minutes in Upstash Redis. A successful booking persists in the Setters.ai team's Google Calendar and the invited attendee's calendar according to their Google settings. Google receives the attendee details and sends the invitation. Closing the page does not cancel an event already created. Reply to the invitation or email the contact address below to correct or cancel it.

When separate booking emails are enabled, we also keep the booking event identifier, recipient email, and delivery state in Upstash for up to 30 days to send your confirmation and pre-call reminders. Google receives the recipient address and message contents to send these appointment emails from our team’s Gmail account. Copies remain in the sender’s Gmail Sent folder under that account’s retention settings. They do not subscribe you to a newsletter. We check the calendar before sending and stop reminders when the event is cancelled or you decline the invitation.

Visitor and campaign measurement

We use Vercel Web Analytics to measure public page views, approximate unique visitors, referring sites, country, browser and device categories, and demo and booking milestones. We remove query strings and fragments from reported page URLs and exclude internal QA pages. Event properties contain only the product and a stage or error category, never names, emails, prep answers, audio, transcripts, or booking credentials. Vercel Web Analytics does not use tracking cookies. Global Privacy Control and the measurement opt-out below also disable this visitor analytics collection.

Setters.ai may collect allowlisted campaign parameters, landing path, demo milestones, error categories, and Meta click or browser identifiers. Campaign attribution is kept in session storage for the current browser session. Meta Pixel may set cookies and receive page or funnel events. After a real booking, Setters.ai may send Meta's Conversions API the booking event, a hashed email address, a hashed internal booking identifier, and available campaign identifiers. Prep answers, audio, and transcript text are not sent to Meta. Global Privacy Control signals and the choice below disable browser marketing measurement. These controls do not disable demo recording, which is separate from marketing analytics.

Hosting and security data

Hosting and security providers may process standard request information such as IP address, browser type, requested page, and timestamp for reliability, access logging, abuse prevention, and rate limiting. Pseudonymous identifiers are used where practical.

Contact

Questions can be sent to hello@setters.ai.