Privacy Notice

Last updated: May 31, 2026

What this covers

This notice explains the general privacy behavior of GoClaw software. A specific GoClaw deployment may have its own configuration, storage location, logs, connected channels, and AI providers.

Data GoClaw may process

Depending on configuration, GoClaw may process chat messages, prompts, responses, session history, uploaded media, generated files, tool results, logs, pairing records, user identifiers, workspace files, memory records, and credentials stored by the local operator.

Where data is stored

GoClaw is designed to be local-first. Runtime data is usually stored on the machine where the operator runs GoClaw, often in SQLite databases and local files. Operators are responsible for securing that machine, backups, file permissions, and retention settings.

Third-party providers

If an operator connects GoClaw to LLM providers, messaging platforms, databases, observability tools, MCP servers, or other APIs, relevant prompts, files, identifiers, and tool data may be sent to those services. Their own terms and privacy policies may apply.

Website analytics and fonts

This website may load third-party services such as Google Analytics and Google Fonts to measure basic site usage and render typography. These providers may receive technical information such as IP address, browser details, page URL, and timestamps according to their own policies. If analytics is not configured, no analytics property is intentionally active.

Memory and logs

GoClaw can persist memory and logs so agents can work across sessions. Do not enter personal, confidential, regulated, or secret information unless the deployment is configured and authorized to process it.

Your choices

For a deployment operated by someone else, contact that operator to request access, correction, export, or deletion of your data. For this site, contact: security@ulab.mn.