Answer Cloud processes account information, published content, website activity, and chat/form interactions to operate the service. Review the Privacy Policy and Terms of Service for the governing terms. This page explains practical product behavior and request paths.
Know what each integration collects#
| Area | Examples |
|---|---|
| Account and access | Account email, workspace memberships, authentication metadata. |
| Website analytics | Requested URLs, referrers, user agents, timestamps, and event metadata. |
| Content | Published pages, drafts, uploaded CMS assets, generated reports. |
| Chat and forms | Messages, conversation records, volunteered contact information, submitted fields. |
| Billing | Subscription status and Stripe-related payment records; Stripe processes payment details. |
On-site chat is your site's interaction history. It does not reveal private conversations visitors have in unrelated AI services. A form submission can save its fields and contact details in a conversation and queue team notifications. Use forms for contact and inquiries; avoid collecting passwords, payment details, or other secrets.
Export the minimum useful transcript#
An authorized agent can use get_chats with an explicit site, time range, role filter, and cursor pagination. The tool excludes dedicated contact fields and internal message metadata. However, contact details or other personal information typed into ordinary message text can still appear in content. Review and redact text before sharing an analysis or exporting it elsewhere.
Set include_messages: false for an inventory or message_roles: ["user"] when only the customer's language is required. Store exports in a destination appropriate for their sensitivity. The MCP export is not a complete account-data download or a deletion mechanism.
Control external-site tracking#
For an external embed, analytics.enabled: false disables analytics event collection. To also avoid initializing the bundle's tracking state, set analytics.tracking: false. analytics.track_forms: false disables its generic form-event tracking. Configure settings before the script runs and verify your consent flow in the browser.
These browser controls do not automatically remove previously stored events, server/edge logs, submitted forms, or chat records. Hosted integrations receive generated settings; use supported platform configuration and ask support if your required consent behavior is not exposed.
Request retention or deletion help#
The privacy policy describes retention by operational and legal need rather than giving one duration for every data category. To request an account export, deletion, or a retention clarification, email privacy@answer.cloud. Use support for operational data questions. Identify the account, workspace/site, data category, and requested scope without attaching unnecessary private records.
Ask the team to confirm applicable retention, deletion scope, contractual requirements, and any records that must remain. Archiving a CMS page removes public content while preserving its record; it is different from deleting account data.
See security and reporting tools.