This notice is about talksociety.ai — the voice demos on it, the conversations people have with our own AI, and the emails, calls and texts that reach us. It says what we collect, why, who else sees it and how to have it deleted. If you would rather just ask a person, email hello@talksociety.ai.
Who we are
Talk Society LLC, 1111 Lincoln Road, Suite 500, Miami Beach, FL 33139, United States, is the controller of the information described here. Email hello@talksociety.ai.
What this notice covers — and what it does not
It covers this website and our own agents: the demos, our own AI ("Book a demo") — here and behind the "Talk to it now" button on our ads on a partner website — the AI Concierge on this site and on the pages of a partner website that shows it, our own telephone line, the ordinary business contact that follows, and — when we switch it on — a call we place to a business we have found to introduce ourselves. That last one is not running at the moment; when it is, we keep the business's details, the call's transcript and a short summary until you ask us to delete them, and a note never to call again for as long as we are trading.
It does not cover an agent we have built for one of our clients. When you speak to a voice agent on another company's phone line or website, that company decides what the agent does and what happens to the conversation — they are the controller and their privacy notice applies. We run the agent on their instructions, as their processor, under our agreement with them.
What we collect, and when
When you try a voice demo in your browser
Pressing Start asks your browser for the microphone. Your audio then flows directly from your
browser to our speech provider; it does not pass through our servers, and we do not record or store any audio. What we keep is the session: which demo it was,
when it started and ended, how long it ran, a written transcript
of the conversation, what the agent did in it (what it booked, quoted, scored or logged), the
outcome shown on your screen, what the session cost us to run, your IP address and, if the link
you arrived from carried a campaign tag (the utm_source
and utm_campaign
in its address), that tag. The links in our own emails use it to
name the email they are in, never the person it was sent to. While the
call runs, your browser also reports technical figures about the connection: how much
of the audio went missing, had to be filled in or arrived late, the delay, the amount of data,
the audio format, whether the connection was up or had dropped, whether it was direct or
relayed and over which network protocol, and which of your browser's audio players played the
agent's opening line, with the state and sample rate of your browser's audio system and, if the
first player failed, the step it failed at. These
figures never include an IP address or port. We keep them with the session to diagnose sound
problems.
The demo businesses are invented and nothing said to one is acted on in the real world. Please use made-up details rather than real customer, patient or candidate information — the terms ask the same.
When a demo calls you
Two demos ring a real telephone instead of using your browser. For those we also keep the number you typed; our telephony provider places the call and processes its audio, and unlike a browser demo that audio passes through our servers on its way to the speech provider. The demo may also send you up to two text messages as part of the scenario, if you ticked the box asking for them (see Text messages below). Again we keep the transcript and the session record (including a link's campaign tag, as above), not an audio recording. Please use your own number.
When you ask the AI Concierge
The AI Concierge answers questions about MoonPay. It cannot see any account you hold with MoonPay. We keep it the same way as a browser demo: the session record, a written transcript and the technical figures about the connection, and no audio. When it cannot answer from what it already knows, it may send your question, as the concierge puts it, to our speech and language model provider's web search.
A partner website may show the same concierge in a panel on its own pages, with a note that it is ours. There we run it and keep it exactly as on this site, and we also keep which website the call was started on and the address of the page (its path, never anything after a "?"). If you start the call by tapping a suggested question, that question is the first line of the transcript. On an article, the article's title is given to the concierge for that call so it knows what you are reading; we do not store it as such, though if the concierge looks the article up, what it finds is part of the call like anything else it says. We do not send the partner's servers anything about the call. The call itself runs in your browser on the partner's page — your microphone, the concierge's voice and the panel showing the call's progress are all in that page — so it is subject to that page, as well as to this notice.
When you talk to our own AI, or ring our line
Our AI's job is to understand what you would want built and to get you a meeting. It takes what you tell it: your name, your company and role, what you want built, the volume and the systems involved, your telephone number and your email address — and it reads the number and the address back so you can correct them. If you ask it to, it books a meeting with us, which creates an event in our calendar and sends a calendar invitation to that address. If you would rather not book, it takes a time to call you back instead.
On our own telephone line, your caller ID is the number we use. After a browser conversation on this site the page shows a short form with the number and address our AI heard, pre-filled, so you can check or correct them. A browser conversation with our AI is kept the same way as a browser demo, including the technical figures about the connection described above.
Our ads on a partner website may carry a "Talk to it now" button. Pressing it starts the same conversation with our AI, kept the same way, and we also keep which website and page the call was started on (its path, never anything after a "?"). Nothing of ours is shown on that page afterwards — no form — so the address and number our AI reads back on the call are the ones it uses. We do not send the partner's servers anything about the call. The call itself runs in your browser on the partner's page: your microphone, our AI's voice and the ad showing whose turn it is to speak are all in that page, so the call is subject to that page, as well as to this notice.
What you say in those conversations reaches our team: a summary of the enquiry, the contact details you gave, the partner website and page if the call started on one, and the link's campaign tag, if there was one, are sent to our internal alerts channel so that a person picks it up.
When you email us
We keep your message and your address so we can reply and keep track of the conversation.
When we make you a video
If you ask us for a closer look at what we would build, we may make a short video for your business. It can show your name, your company, its phone number and its logo, and its voices are generated with our speech provider. The video is kept by our media storage provider and plays on a page of ours that is not listed anywhere and asks search engines not to index it. Anyone with the link can watch it, so the link is hard to guess and we send it only to you. Ask us and we will delete the page and the video.
Automatically, as you browse
Our servers log ordinary request information — IP address, the page requested, the time, browser and referrer — to keep the site running, secure and within its fair-use limits. The site sets one essential cookie of its own.
A post on our blog plays a news video in YouTube's privacy-enhanced player. Nothing loads from YouTube until you press play or a chapter. When you do, YouTube (Google) receives your browser's IP address, our site's address and details of your browser, and may store identifiers in your browser, under Google's own privacy policy.
Our home page, our product pages (AI receptionist, AI answering service, AI sales agent, AI voice agents, pricing, home services, real estate, insurance and car dealerships), our guide to full-duplex voice AI, our blog and these policy pages also load Google's advertising tag. When one of those pages loads, the tag sends Google your browser's IP address, the full address of the page you are on (including anything after a "?" in it) and of the page you came from, the page's title, details of your browser and screen, the identifiers Google keeps for your browser and, if you arrived by clicking one of our Google ads, that click's identifier. It also tells Google when a visitor has a real conversation with one of our demos, the AI Concierge or our AI, or books a meeting with us on that call. We use it to see which of our ads bring people here and which lead to those; Google can also use it to show our ads to people who have visited, on other sites and apps. The cookies it sets are listed on the cookie notice, and Google uses what it receives under its own privacy policy. The tag is not on a video page we make for you, and that page tells your browser not to pass its address on, so Google does not receive it from the page you open next. Its buttons carry only which industry and demo to open and the name of the campaign the video belongs to, and the tag on the page they open does receive those.
The same tag also sends what it collects to Google Analytics, Google's website-statistics service, for our account there, together with how long you stay on a page, how far you scroll down it, the links you follow to other sites, and when you start or send a form. We use it to see how the site is used: how many people visit, how they arrived, which pages they open, and how many of them have a real conversation with a demo or our AI, or book a meeting on that call. Its cookies are on the cookie notice too.
Text messages (SMS)
Talk Society LLC ("Talk Society") sends text messages only to a number typed into one of our phone demos, and only if you ticked the separate box under it asking for texts. That box is unchecked to start with and optional: the call goes ahead whether or not you tick it. If you do, the demo may send you up to two texts during that call, such as the confirmation of a booking made in the scenario or a link you asked for in it. Consent to receive texts is not a condition of purchase. If you text one of our numbers yourself, we may reply automatically to say who we are. Message frequency: up to two texts for each phone demo in which you tick the box. Message and data rates may apply. Reply STOP to stop them, START to receive them again or HELP for help, or email hello@talksociety.ai. The full SMS terms are in our terms of service.
For each opt-in we keep the number you typed, which demo it was, the date and time you started it with the box ticked, and the IP address it came from, with the demo's session record described above. If you reply STOP, we keep a note that the number has opted out, so that we do not text it again unless you reply START.
We do not sell or share your SMS opt-in data or personal information with third parties for marketing purposes. In this section, personal information means the mobile number you give us for texts and the record of your consent; what Google's advertising tag collects as you browse is described above. No mobile information will be shared with third parties or affiliates for marketing or promotional purposes.
Why we use it
- To run the demo you asked for — we cannot hold a conversation without processing what is said. Where consent is the right basis, your browser asks for the microphone and you can refuse or stop at any time.
- To answer your enquiry — to reply, to book the meeting, to prepare a proposal, and to take the steps you asked for before any contract.
- To keep the service working and honest — security, abuse and spend limits, diagnosing faults, and reviewing how our own agents behaved on a call so we can put right anything that went wrong.
- To measure our advertising — to see which of our Google ads bring people to this site and lead to a real conversation with a demo or our AI, or a meeting booked on that call (what counts as a real conversation is decided from a language model's reading of the call, as described below), and to show our ads again to people who have visited.
- To see how the site is used — with Google Analytics: how many people visit, how they arrived, and which pages and demos they use, so we can make the site better.
- To meet our legal obligations — including keeping records where the law requires it.
Where the GDPR or UK GDPR applies, our lawful bases are your consent (the microphone), the steps taken at your request before a contract and performance of a contract (your enquiry and any engagement), our legitimate interests in running and securing the service and in understanding enquiries about it, and compliance with legal obligations.
Who else sees it
We use service providers to run the calls and the site — a speech and language model provider, telephony, hosting, database, media storage, email, scheduling, our internal alerts channel and, for our paying customers, card payments (Stripe, on the account of the merchant of record named in our terms). Each one is named, with what it does, on our subprocessors page. They process what we send them to provide their service to us. Google is listed there too: what its advertising tag collects (above), it also uses under its own terms.
Our team reads how calls go. After every call you make to one of our agents — a demo, our own AI or the AI Concierge, on this site, on our phone lines or on a partner's page — a short written summary goes to our internal alerts channel: which agent it was, where the call started, how long it ran, what it cost, what was talked about, and how many calls the same connection or number made that day, with a link our team uses to read the transcript here (the transcript itself is not sent to the channel). A language model writes the summary from the transcript and, while the call runs, notes whether each thing the caller says is about what that agent is for. Our team reads that note to judge whether to limit people who use the agents for something else; it does not change, end or block anyone's call. For a call started on one of our pages that carries that tag, it is also what decides whether the call was a real conversation for the advertising tag described above. Once the model has read something the caller said as being about what the agent is for — or, for a caller who has said only a word or two, which the model is not asked to read, once the agent has done its job for them, or once our AI has booked them a meeting — and the model has not by then read anything they said as abusive, the page tells Google that the visitor had a real conversation. Our code adds only that to what the tag already sends, never what was said.
We also share information with professional advisers where we need to, with authorities where the law requires it, and with a buyer if the business is ever sold — in which case this notice travels with it.
When we meet you on a video call
The meeting our AI books is a Google Meet with someone from our team, and we record and transcribe it, so that what we build matches what was agreed. The recording is made by our own AI, Erika, who joins the call as a participant through our provider Recall.ai: Recall.ai records the meeting's audio and video and writes a transcript that shows who said what. While she is in the call the meeting's audio — everyone's voices — also goes to our speech provider, so that she can follow the conversation and answer when she is spoken to, and we keep a written transcript of what she heard as well. Her tile names her as Talk Society's AI, and she is built to say she is an AI when she speaks.
You are told when the recording starts: as she joins, we post a message in the meeting's chat saying the meeting is recorded and send it to people who join after her, and her tile says so too. If you would rather it were not recorded, say so and we will stop and delete the recording and every transcript of it.
Recall.ai keeps the recording for seven days and then deletes it. In that time our team can watch it, or save a copy to build from. We record who on our team opened it, so that when you ask us to delete it, anyone who saved a copy is asked to delete it too. We keep the written transcripts with the rest of your enquiry, on the same terms as below.
We do not sell your information for money, and we do not use demo conversations to train our own models. Our providers process content to return a response under their business terms with us. The one thing that goes to an advertiser is what Google's tag collects as you browse the pages of ours that carry it, including the conversions it reports, described above: because it lets Google show our ads to people who have visited, the law may treat it as selling or sharing for cross-context behavioural advertising.
How long we keep it
Demo sessions, enquiry records and correspondence are kept for as long as they are useful for the purposes above — running and improving the service and following up an enquiry — and we have not set a fixed schedule for the agency site yet. We would rather say that plainly than publish a period we do not enforce. If you want yours gone sooner, ask us and we will delete it.
Your choices and rights
Whatever your location, you can ask us to give you a copy of what we hold about you, correct it, or delete it. Email hello@talksociety.ai and tell us enough to find the record — the number you typed, the address you gave, or roughly when you used the site or when we met. We will not treat you differently for asking.
Depending on where you live you may also have the right to object to or restrict our use of your information, to receive it in a portable form, to withdraw consent at any time, and to complain to your data protection authority. Californian residents have the rights described above. Google's advertising tag may count as selling or sharing personal information as the CCPA defines those terms. Blocking third-party cookies leaves the tag's cookies on this site in place, so it can still recognise your browser; blocking all cookies for this site also stops the voice demos and the contact form working, and even then the tag still sends Google your IP address, the page and your browser details. A content blocker that blocks Google's tag stops it entirely, and nothing else on the site depends on it. Google's My Ad Center limits how Google personalises ads for you. The site does not yet have a switch of its own that turns the tag off for you, and does not yet act on a Global Privacy Control signal from your browser.
Children
This is a website for businesses. It is not directed at children and we do not knowingly collect information from anyone under 16. If you believe a child has used it, tell us and we will delete what we have.
Where it is processed
We are in the United States and our providers process information there and in other countries where they operate. If you are in the UK, the EEA or Switzerland, transfers are made under appropriate safeguards, such as the European Commission's standard contractual clauses.
Security
The site runs over HTTPS. Access to enquiry and demo records is limited to the people who need it, credentials are held as secrets rather than in our code, and we keep no audio of a demo or of a call with our AI — a recording we never make is a recording that cannot leak. (We do store one short clip per demo of the agent's own opening line, which we generate ourselves; there is nothing of yours in it.) The one recording that is made is of a video meeting with our team, as described above: Recall.ai holds it and deletes it after seven days, and when you ask us to delete it, anyone on our team who saved a copy is asked to delete it too. No service is perfectly secure, and we do not pretend otherwise.
Changes
If we change this notice we will update the date at the top. Where a change materially affects how we use information we already hold, we will take reasonable steps to tell the people affected.
Contact
Talk Society LLC
1111 Lincoln Road, Suite 500
Miami Beach, FL 33139
hello@talksociety.ai