Information Beaco may process
When a visitor uses a Beaco widget, the platform may process the messages and files they choose to send, voice transcripts when voice-to-text is used, a visitor identifier, current page, page journey, referrer, browser language, device/browser information, visit history and network information such as IP address. Workspaces may also collect contact information a visitor voluntarily provides.
For workspace users, Beaco processes account details, team-member Gmail addresses, settings, AI instructions, knowledge sources and operational records required to provide the service.
Approximate and precise location are different
Beaco may derive an approximate network location from IP/network information when available. This can include country, region, approximate city, timezone, ISP/network information and approximate coordinates. It should not be treated as exact physical location.
Precise location is separate. If a workspace enables that feature, the visitor's browser must request permission and the visitor must approve it. Beaco does not bypass browser location permission.
AI and website knowledge
Beaco may process public website content and workspace-provided knowledge so the AI can answer business questions. AI operations may also process conversation text for translation, reply assistance, knowledge-gap detection, lead intent and related product functions. Workspaces should avoid adding secrets or information they are not permitted to process.
Deletion and protected audit copies
Deleting a visitor through Visitor Intelligence is intended to remove the visitor's related stored workspace data according to the product's deletion workflow. Removing a Pro conversation from the normal Inbox is different: a protected audit copy may remain available to authorized Beaco platform administrators for security, abuse prevention, troubleshooting and platform administration until that audit copy is permanently removed under the available administrative controls or retention process.
Closed or dismissed conversations may remain in workspace history so the same thread can be reopened later.
Workspace owner responsibilities
Businesses using Beaco decide why they deploy the widget and what business information they ask visitors to provide. They are responsible for providing any notices, consents or policies required for their use case and jurisdiction, and for using visitor data lawfully.
Contact inquiries
If you submit the public Beaco contact form, we store the details you submit so the team can review and respond to the inquiry. Basic network information may also be stored for operational and anti-abuse purposes.