Skip to content

Legal

Privacy Policy

Last updated

Draft: under review, not yet in effect. Details in brackets are still to be filled in.

Summary in plain words

  • Site Can Talk adds a chat and voice assistant to business websites. It answers visitors from that business's own website and documents.
  • If you chat with a website that uses us, what you type or say is used to answer you and is shared with that business.
  • Your voice goes straight from your browser to OpenAI to be answered. We keep a text transcript, never the recording.
  • We only get your name, email or phone number if you choose to give them.
  • The business controls its visitors' data. We process it for them.
  • Our team may access conversations and leads to give support and fix problems.
  • We don't sell personal data, use it for ads, or use conversations to train AI models.
  • We keep data while the business's account is open. Ask us and we'll delete it.
On this page

Who we are

Site Can Talk is run by [legal name], [postal address and country]. In this policy, “we” and “us” mean Site Can Talk.

This policy covers:

  • our website, and the dashboard where businesses set up their assistant
  • the chat and voice assistant (“the widget”) that businesses add to their own websites, and the chat page they can share as a link or QR code
  • the replies the assistant sends on Messenger, Instagram and WhatsApp when a business connects them

Questions about privacy: [contact email].

Who decides what happens to your data

Businesses that use Site Can Talk (“owners”) add the widget to their website. For the conversations and contact details their visitors share, the owner is the controller: they decide why the data is collected and what happens to it. We are their processor: we handle it only to run the service for them, as this policy describes.

For owners’ own account data, such as their email address, settings and plan, we are the controller.

If you chatted on a business’s website, that business is the best place to start with questions about your data. You can also contact us, and we’ll help or pass your request on.

What we collect

From owners

  • Your email address, to send sign-in links, lead alerts, a weekly summary and a monthly report.
  • If you sign in with Google, Google tells us your email address and your Google account ID. We keep both, so the same Google account always opens the same dashboard. We don’t get your password or anything else in your Google account.
  • Your website’s address and its public pages. We read your site so the assistant can answer from it, and read it again about once a week to stay up to date. Our crawler follows your robots.txt.
  • What you add in the dashboard: your business profile, documents you upload or paste, answers to visitors’ questions, and settings such as your alert email, WhatsApp number, webhook address, opening hours and next-step links. We turn uploaded files into text and keep the text, not the file.
  • Connected accounts. If you connect a Facebook Page, Instagram account or WhatsApp number, we keep its ID and name, and an access token from Meta, which we encrypt.
  • Billing. Lemon Squeezy runs checkout and payments. We receive your plan, its status and a subscription ID. We never see your card details.
  • How you use the service: your plan, the voice minutes and chat messages used each month, and the status and value you record for each lead.

From website visitors

When you use the widget on a business’s website, we collect:

  • Your messages and the assistant’s replies, saved as a transcript the owner can read.
  • Voice calls. A call only starts when you tap to talk, and uses your microphone only with your browser’s permission. Your voice goes straight from your browser to OpenAI, which answers in real time. We never receive or keep the recording. We keep a text transcript of the call.
  • Your contact details, only if you choose to give them: your name, email, phone number and what you need, typed in the chat, said in a call or entered in the contact form. They go to the owner as a lead.
  • Questions the website couldn’t answer, so the owner can add the answer.
  • Where your visit came from: the address of the page that sent you (without anything after a “?”), any campaign tags in the link (utm_source, utm_medium, utm_campaign) and the first page you opened. The owner sees this next to your conversation or lead.
  • A random visitor ID kept in your browser (see Cookies and browser storage).
  • For voice calls, a salted hash of your IP address, not the address itself, to limit how often calls can start.
  • Your approximate country, which Cloudflare works out from your IP address. We use it only to read a phone number you type, and don’t store it.

From people who message a business on Messenger, Instagram or WhatsApp

If a business connects these, the assistant answers its messages. We receive your messages and your ID on that platform (on WhatsApp, your phone number), and keep the conversation as a transcript for the business. WhatsApp voice notes are sent to OpenAI to be turned into text. We keep the text, not the audio. On WhatsApp, your number can be passed to the business as a lead so they can reply to you.

Technical data

Like any website, our servers receive technical data such as your IP address, browser type and the time of each request. Cloudflare, which runs our servers, uses it to deliver the service and block abuse, and we keep short-lived logs to find and fix errors. We don’t use advertising or analytics trackers.

Why we use it

  • To run the service: answer visitors, show them the right page, pass leads to the owner, and send sign-in emails, alerts and reports.
  • To keep it safe and fair: stop bots and abuse, and apply each plan’s limits.
  • To bill paid plans through Lemon Squeezy.
  • To fix problems when something breaks.

Under laws like the GDPR, our legal bases are our contract with owners and our legitimate interest in running a secure, working service. For visitors’ data, the owner is the controller and decides the legal basis.

We don’t sell personal data, use it for advertising, or use conversations to train AI models.

Who we share it with

We share personal data only with the owner of the website you used, with the providers below, who process it so we can run the service, and with authorities when the law requires it.

Our own team may access conversations, transcripts and leads to give support and fix problems. We don’t use them for anything else.

  • Cloudflare hosts our servers and database, runs our search index, turns uploaded documents into text, reads websites, and runs the security check (Turnstile) and rate limits. It handles everything the service stores, plus technical data such as IP addresses.
  • OpenAI writes a summary of each website from its pages, answers chat messages, runs voice calls, turns speech into text, drafts the business profile and voices the name-pronunciation preview. It receives website content, conversations and voice audio. Under its API terms, OpenAI doesn’t use this data to train its models, and keeps it for up to 30 days to check for abuse, unless the law requires longer (see OpenAI’s data controls).
  • Resend sends our emails: sign-in links, lead alerts and reminders, weekly summaries and monthly reports. It receives email addresses and the email content, including lead details in alerts.
  • Google signs you in when you choose “Continue with Google”. Its sign-in script runs on our sign-in page only, under Google’s privacy policy.
  • Lemon Squeezy sells our paid plans as merchant of record: checkout, payment, sales tax and invoices. It receives the owner’s email address and account ID. Card details go straight to Lemon Squeezy.
  • Meta delivers WhatsApp lead alerts to owners who add a WhatsApp number, and carries messages on the Messenger, Instagram and WhatsApp accounts a business connects. It receives a lead’s name, contact and need in WhatsApp alerts, and the messages and replies on connected accounts.

Lemon Squeezy and Meta also handle data under their own privacy policies, because you deal with them directly when you pay or use their apps.

If an owner sets up a webhook, we also send each new lead to the address they chose. That is the owner’s own system.

Cookies and browser storage

We only store what the service needs to work. There are no advertising or analytics cookies.

On our website and dashboard

  • wct_s (cookie, 30 days) keeps you signed in to the dashboard. Scripts on the page can’t read it, and it’s only sent over HTTPS.
  • wct_in (cookie, 30 days) only says you’re signed in, so our pages can show a Dashboard button. It holds nothing else.
  • g_state (cookie, set by Google on our sign-in page) remembers if you closed Google’s sign-in prompt, so it doesn’t keep asking.
  • wct_fbu (cookie, 10 minutes) holds an encrypted Facebook sign-in token while you choose which Page to connect.
  • theme (local storage, until you clear it) remembers whether you chose the light or dark dashboard.

On websites that use the widget

The widget stores these in the visitor’s browser, on the business’s website. Each website keeps its own, so they can’t follow you from one website to another.

  • wct:vid (local storage, until you clear it) is a random ID for your browser on that website. It links your chats there, limits voice calls, and lets a call continue when the assistant opens another page.
  • wct:<site ID> (session storage, until you close the tab) holds your current chat (its ID and recent messages), so it stays open as you move between pages.
  • wct:src (session storage, until you close the tab) holds where your visit came from (see What we collect).
  • wct:conv (session storage, removed on the next page) lets the chat or call pick up again after the assistant opens another page.
  • wct:nudged and wct:quiet (session storage, until you close the tab) remember whether the widget already showed its hint, or you closed it, so it doesn’t keep asking.

The security check runs Cloudflare Turnstile in a small frame loaded from our server. Cloudflare uses signals such as your IP address and browser details to tell people from bots. Its Turnstile privacy addendum explains what it collects.

How long we keep it

  • Sign-in links work once and expire after 15 minutes. We store them only as hashes.
  • Conversations, leads and unanswered questions are kept while the owner’s account is open, so the owner can follow up. Nothing is deleted automatically yet. Owners, or visitors through them, can ask us to delete them at any time.
  • Website pages are refreshed about once a week. Pages that disappear from the website, or that the owner removes in the dashboard, are deleted from our copy and our search index.
  • Documents and answers an owner removes are deleted from our database and search index shortly after.
  • Connected accounts: disconnecting one deletes our connection and its access token.
  • Voice recordings: we never store them. OpenAI keeps API data for up to 30 days to check for abuse.
  • Owner accounts and websites are kept until the owner asks us to delete them. There’s no delete button in the dashboard yet, so email [contact email].
  • Backups: deleted data can stay in our database provider’s automatic backups for up to 30 days.
  • Payment records are kept by Lemon Squeezy under its own policies.

How we protect it

  • Data travels over encrypted connections (HTTPS).
  • Sign-in links work once and are stored only as hashes. The sign-in cookie is signed, and scripts can’t read it.
  • Access tokens for connected Meta accounts are encrypted before we store them.
  • Our API keys stay on our servers. A visitor’s browser only gets a voice-call key that expires within a minute.
  • Lead webhooks are signed, so owners can check they came from us.
  • Each lead alert links to a private page for that lead. Anyone with the link can open it, so owners should keep alert emails and messages private.

No system is perfectly secure. If a breach affects personal data, we’ll tell the owners affected without undue delay.

Your rights

Depending on where you live (for example under the GDPR in the EU and UK), you can ask to see the personal data we hold about you, correct it, delete it, get a copy, or object to or limit how we use it.

  • Owners can do much of this in the dashboard: change settings, remove pages, documents and answers, download leads as a CSV file, and disconnect accounts. For anything else, including deleting your account, email [contact email].
  • Visitors: contact the business whose website you used, since it controls your data. You can also email us. Tell us the website, roughly when you chatted, and the email or phone number you gave, so we can find it.

We may need to check it’s really you. We reply within one month. You can also complain to the data protection authority where you live.

Children

Site Can Talk is for businesses and isn’t aimed at children. We don’t knowingly collect children’s personal data. If you think a child has shared personal data through the widget, contact the business or us and we’ll delete it.

International transfers

Our providers are mostly based in the United States and run services around the world, so your data may be processed outside your country. Where the law requires safeguards for these transfers, we rely on our providers’ data processing terms, such as the EU Standard Contractual Clauses.

Changes to this policy

When we change this policy, we’ll update the date at the top. If a change affects how we use your data in a meaningful way, we’ll email owners before it takes effect.

Contact

[legal name]
[postal address and country]
[contact email]