Skip to content

PRIVACY.md

Latest commit

 

History

History
61 lines (47 loc) · 2.63 KB

PRIVACY.md

File metadata and controls

61 lines (47 loc) · 2.63 KB
Raw

Privacy Policy

daimon is self-hosted software: each deployment has its own operator who runs the bot, holds the Anthropic API key, and controls the database. This document describes what a default daimon deployment stores and the rights available to end users through the /privacy command. It does not cover any specific operator's practices beyond what the software itself does — for questions about a particular deployment, contact that server's operator.

What is stored

For each tenant (a Discord server or Slack workspace that has installed the bot), daimon stores:

  • Workspace/guild configuration — the tenant's installed agents, environments, and skill bindings.
  • Thread/session mappings — which Discord thread or Slack conversation maps to which Managed Agents session, so conversations can continue across messages.
  • Usage and billing events — turn counts and credit/usage records used to enforce the operator's configured usage limits.
  • Agent credentials — any bound external credentials (e.g. a GitHub personal access token used by get_cli_token), encrypted at rest.

Conversation content itself (messages, agent responses) lives in Anthropic's Managed Agents service, not in daimon's own database. daimon's database holds identity, namespacing, and provenance metadata only.

Your rights via /privacy

Every daimon deployment exposes a /privacy slash command (Discord) or equivalent panel (Slack), available to any user, in DM or in a shared channel. It lets you:

  • View what is stored about you under the current tenant.
  • Export your stored data.
  • Delete your stored data ("delete me"), removing your per-user records from that tenant.

These actions apply to the tenant the command is run in. If you interact with daimon across multiple servers/workspaces, each tenant's data is handled independently — see the next section.

Data isolation

Data is scoped per tenant at the database tenant_id layer. Guilds and workspaces never see each other's data, even though many tenants may share a single operator's Anthropic API key. There is no cross-guild or cross-workspace sharing of stored data.

Operator responsibility

Each daimon deployment is run by its own operator, who controls the Anthropic API key, the database, and the infrastructure the bot runs on. Direct any data questions specific to a deployment to that deployment's operator, not to the daimon project.

Operators who wish to publish their own privacy policy (for example, one covering jurisdiction-specific commitments) can set DAIMON_PRIVACY_POLICY_URL to point the Policy button at their own page instead of this document.