What happens to visitors' conversations

When you're done, you know where conversations with your Chirps are kept, what Chirp Builder stores about visitors, and what a visitor can clear.

Who this is for: Chirp owners on any plan, and anyone who chats with a Chirp. Visitors don't need an account.

Conversations stay in the visitor's browser

Chirp Builder doesn't keep what visitors and your Chirp say to each other, so nobody can read it there: not you, not your team and not us.

• On the Chirp's own page (and on your custom domain), each chat is saved in the visitor's browser and listed beside the chat. A new visitor's empty list says "Your chats are saved in this browser only."
• In a chat on another website (an embed), nothing is kept: the conversation ends when the visitor leaves the page.
• Your preview in the editor keeps nothing either. Reset starts it again.
• Files and pictures a visitor attaches, and pictures the Chirp makes, stay with the chat in the browser. They aren't stored on our servers.

Chats are kept per browser and per web address. Another device, another browser or a private window doesn't see them.

What Chirp Builder keeps about visitors

Nothing that says who a visitor is, unless they choose to give it to you:

• A record of each answered message: which Chirp and model, the tokens, what it cost, where the chat ran (the Chirp's page, an embed or your domain) and the name of the website the visitor came from, like facebook.com. Not the text. Analytics counts these.
• An anonymous visitor code, made from a random code the visitor's browser keeps (or from a hashed network address when the browser can't keep one). It's different on each Chirp and can't be turned back into a person. It's how visitors and returning visitors are counted.
• A hashed network address in the counters that stop abuse, such as too many messages or wrong access codes. Counters are removed after 2 days.
• Messages that got no answer: only that one failed, and why (a limit, the Chirp being unavailable, or an AI error).
• What visitors choose to give you: a lead form (their name, email, the consent they ticked and whether they want updates), or the email they confirm to open a protected Chirp. See The Leads page and exporting leads and Who can open a Chirp.
• Actions: each call's operation and result, for 30 days. When a visitor is asked to confirm a change, what would be sent is stored encrypted and erased once they answer, or within an hour after the request runs out. The answer itself is kept for 90 days. See Recent calls and failing-call alerts.

Email codes for protected Chirps are stored only as a one-way hash, and work for 15 minutes.

Where messages go to get an answer

• To the AI model, through your OpenRouter account: each message with the conversation so far, the text of attached files and the newest pictures, plus your instructions and what's needed from your knowledge files. OpenRouter and the model's provider handle them under their own policies and your OpenRouter account's settings. See What OpenRouter is, and who pays for what.
• Web search, if you switched it on, also runs through OpenRouter.
• Actions: what the Chirp fills in, often from the visitor's messages, goes to that service. Changes ask the visitor first, unless you chose otherwise.
• Leads go wherever you send them: your email, your email service or your webhook.

Chirp Builder doesn't pass the visitor's network address on to any of these.

What a visitor can clear

• One chat: the bin beside it in the chat list. It deletes straight away, without asking.
• Everything on that site: clear the site's data for chirpbuilder.com (or your domain) in the browser's settings. This removes their chats with every Chirp there, forgets remembered access codes and sign-ins and that they sent a lead form (the lead itself stays with you), and they count as a new visitor.
• What they gave you: only you can remove a lead or an email sign-in. If a visitor asks, delete their lead on the Leads page, or click the X beside their email under People who signed in. Leads already sent to your email service or webhook stay there: remove them there too.

Hide the chat list (Creator and up)

In Settings, Public branding, switch off Show visitors their earlier chats beside the chat ("Turn off for a simpler, single-chat page."), then click Save branding. It applies to the workspace you're in.

Visitors then get a New chat button instead of the list. Their chats are still saved in their browser, but they can't see or delete them one by one. Clearing the site's data still removes them.

Good to know

• There's no built-in privacy notice on the chat page. A lead form can link to your privacy policy, and so can the welcome text or the button under the chat.
• Visitors who give their email to open a Chirp are told: "Your email is shared with the creator so they know who visited. It doesn't sign you up for any mailing list."
• Fonts on Chirp Builder's pages come from Google Fonts, so a visitor's browser connects to Google. There are no ad or tracking scripts.
• Deleting a Chirp doesn't delete the leads it collected.
• Course tutors keep their conversations in the student's browser too: see Student data in your Academy.
• To see what you and your team can see about visitors, read What you and your team can see about visitors.