What you and your team can see about visitors

The counts, leads and sign-ins you see about your visitors, who on your team sees them, and what nobody can see.

EssentialsCreatorBusinessAcademyFor: Account owner, Workspace admin, Editor, Viewer

When you're done, you know what you can see about the people who chat with your Chirps, and who on your team sees the same.

Who this is for: account owners on any plan, and the people they work with.

What you see

  • Counts, not conversations. Analytics shows conversations, messages, Visitors (estimate), cost and errors, by day and by Chirp. On Creator and up it adds returning visitors, where chats ran and the websites visitors came from (only the site's name). See Analytics for your Chirps.
  • Leads: what a visitor typed into a lead form (name and email), the consent they ticked, whether they want updates, where they filled it in and when. Nothing from the chat. See The Leads page and exporting leads.
  • People who signed in: for a Chirp or Collection that asks for an email (Creator and up), each email and when it last signed in, with a CSV. See Who can open a Chirp.
  • Recent calls of Actions: when, which operation, whether a visitor, your preview or a test made it, and the result. "Only the operation and the result are kept (calls for 30 days, confirmations for 90). No questions, answers, sent values or keys." See Recent calls and failing-call alerts.
You see counts, not conversations or who visitors are.

What nobody can see

  • Conversations. They stay in the visitor's browser, so there's nothing to read: not for you, your team or Chirp Builder staff. See What happens to visitors' conversations.
  • Who a visitor is, unless they gave you their details. There's no location, device or network address.

Your OpenRouter account may list each request with its model, tokens and cost. What OpenRouter keeps beyond that depends on your settings there.

Who on your team sees what

Team members only see the workspaces you share with them.

OwnerWorkspace adminEditorViewer
Analytics, cost includedYesYesYesYes
Leads and their CSVYesYesNoYes
Deleting a leadYesYesNoNo
People who signed in (with its CSV) and the invited listYesYesNoNo
Recent calls of ActionsYesYesYesYes
Instructions, knowledge files and the access codeYesYesYesYes
Billing and your account's OpenRouter keyYesNoNoNo

Editors don't have Leads in their menu. Editors come with the Creator, Business and Academy plans; workspace admins and viewers with Business. See Invite people to your workspaces and Working in a workspace someone shared with you.

Chirp Builder staff

Chirp Builder staff can open your account's content when helping with support. Changes they make show in a Chirp's History as Support, and any test chat they run uses your OpenRouter account.

AI apps you connect see what their access level allows: see What Actions and connected AI apps can do.

Good to know

  • A sign-in or a lead isn't permission to send marketing emails. Only leads who ticked "updates" asked for them. Visitors who sign in with their email are told it's shared with you and doesn't sign them up for any mailing list.
  • When a lead form emails you about new leads, the emails go to the account owner's email address.
  • Usage records are kept while your account exists. Your plan sets how far back Analytics shows: 30 days on Essentials, 90 on Creator, 12 months on Business and Academy.
  • CSV files hold personal details. Keep them as carefully as the Leads page itself.

Checked against the app on October 27, 2026.