Privacy policy.

EERRAA is an open-source AI agent platform. You can run it two ways: self-hosted on your own infrastructure, or on our hosted beta.

If you self-host, your data stays on your systems and this policy barely touches you. We do not receive your account info, your project config, or your conversation logs.

If you use the hosted beta, we process the minimum needed to run the service: your account info, your project configuration, and the conversation logs your agents generate. That is what the rest of this page is about.

Account info: your name, email, and organization, so we can sign you in and attribute your work.

Project configuration: the settings for each agent you build, including tool definitions, MCP connections, knowledge documents you upload, and policies. Secrets in this config (model keys, per-user credentials) are encrypted at rest with Fernet.

Conversation logs: the messages between your end users and your agents, plus the tool calls, retrievals, tokens, latency, and cost for each turn. This is what powers your dashboard, sessions, and analytics.

Basic operational data: standard request logs needed to keep the service running and secure.

You bring your own model key. When your agent runs, we use your key to call your chosen provider (Anthropic, OpenAI, or Google). Your prompts and your users’ messages are sent to that provider under your account, governed by their terms and their privacy policy.

We never see your model spend and never route your tokens through a shared account. We store your key encrypted, and we use it only to make the calls your agents make.

To run the service: authenticate you, execute your agents, retrieve from your knowledge base, call your tools, and show you logs and analytics.

To keep it working and safe: debug issues, enforce rate limits and budgets, and prevent abuse.

We do not sell your data. We do not use your conversation content to train models.

When you embed the widget, your end users talk to your agent. The user context you pass (an id, and any profile data you choose to send) is processed to personalize and, in signed mode, to authorize private features.

You are the controller of your end users’ data. You decide what to send and what to tell them. We process it on your behalf to run the agent you configured.

Conversation logs and analytics are retained for as long as your project needs them, subject to your plan. You can delete sessions, knowledge documents, and credentials yourself from the dashboard and the API.

If you close your account, we delete or anonymize your data within a reasonable period, except where we must keep something to meet a legal obligation.

When you run EERRAA on your own infrastructure, every byte lives with you: account info, project config, encryption keys, knowledge, and conversation logs. We do not receive any of it.

Self-hosting is the strongest privacy option, and it is free and open source.

Secrets are encrypted at rest with Fernet. Custom tool webhooks are SSRF-guarded. Signed identity is HMAC-signed with a short validity window. Data is isolated per organization.

For the full picture, see the security page.

This is a beta policy and it will change as the product matures. We will update this page when it does.

Questions about privacy? Email hello@eerraa.online.