Data collection, use, and access
Understand what Runs Agents records, why it processes it, and which parties receive information.
On this page
Information recorded or derived
| Information | Purpose |
|---|---|
| Visitor and assistant messages | Maintain the conversation and support staff review. |
| Current website page and relevant form context | Interpret a message in its application context. |
| Form answers and submission results | Collect the requested information and record delivery outcomes. |
| Summaries, translations, classifications, and priority | Help staff understand and organize inquiries. |
| Supported contact details and evidence | Identify the relevant contact within the browser-scoped conversation record. |
| Browser identifiers, agreement state, and message drafts | Restore the visitor's local experience. |
| Staff account and configuration information | Authenticate the team and operate its workspace. |
The first saved visitor message creates the necessary visitor and conversation records. Viewing the greeting or accepting the local privacy screen alone does not create those records. Derived AI information can contain mistakes and should be checked against the original record when consequential.
How information is used
The system uses conversation context to answer questions, infer needs, recommend forms, prefill supported answers, translate relevant text, and prepare records for staff. In-chat submission follows agreement and final confirmation. Configure fields to collect information the destination actually needs.
Runs Agents does not use private conversations or personal information to train, improve, evaluate, or validate AI models. Answering a question using an AI model is processing the input; it is a different activity from training the model.
Who can access or receive information?
Authorized administrators and members can review workspace conversations. Configured notification recipients can receive summaries, contact details, and form information by email. The configured form destination receives submitted values. Your organization should authorize those recipients and manage staff access appropriately.
A browser visitor record groups conversations for that browser context; it is not verified personal identity. Do not treat shared-browser contact associations as proof of the current writer's identity.
Service providers
Cloudflare supplies hosting, infrastructure, and email delivery. Workspace record storage uses Cloudflare or Turso according to the selected arrangement. Merge Gateway routes AI requests to eligible model providers, which can vary.
Runs Agents sends AI requests only through services that Merge Gateway classifies as zero data retention. Providers can still process technical request information under their policies. Zero data retention for an AI route does not erase your workspace's saved conversation record and does not establish country-specific processing.
Provider references:
- Cloudflare privacy policy
- Turso privacy policy
- Merge Gateway privacy policy
- Merge Gateway zero data retention
Privacy notices and requests
The chatbot shows Runs Agents' Chatbot data handling notice and the organization's configured privacy policy and contact. The organization should explain its own inquiry handling and receiving services in its policy.
An employee from your organization should contact Runs Agents directly to request access, correction, or deletion of stored chatbot data. Records currently have no automatic expiry. Read Retention and deletion and Data residency.