← Privacy
For administrators and data protection officers

Data processing

For customer administrators and data protection officers: what a backlayer instance stores, who can read it, which providers process it, and how it is deleted. Every instance serves this note at /data-processing. The user-facing summary is the instance's /privacy page; it names the same providers, retention and deletion path.

What is stored and where

The instance database (PostgreSQL in the instance's stack):

The Knowledge Base (Outline, in the same stack): documents, the team's skills, the Dreaming Backlog, and a read-only copy of each project's instructions. Outline keeps its own account for each user from the same sign-in.

Logs: the backend and the runner containers write logs to the Docker engine on the operator's host. With the operator's optional monitoring stack, a copy goes to VictoriaLogs.

Metrics: aggregate counters with no user ids, emails, session ids or free text.

PostHog, only when the operator sets POSTHOG_KEY:

Not stored: Claude Code or Codex credentials or tokens are not stored by the backlayer backend, its Portainer environment or its database. They are not logged either. They do pass through the backend in transit:

Dictation audio never reaches backlayer: speech recognition runs in the user's browser or operating system.

Who can access it

Reviews

Providers and subprocessors

Retention

Transcripts, curator runs and the rest of the instance data are kept until deletion is requested (a session's content until the user erases that session, see Deletion), with these exceptions:

Web sign-in sessions, enrollment codes and voice tokens expire and stop working; their rows are not purged on expiry.

Deletion

A user can erase any of their own sessions from its menu; a tandem's two sessions are erased together, and there is no undo. The erase stops the session if it is running, then deletes from the instance database its transcripts (subagent transcripts included), its shares, token usage, skill uses and session tokens, its title, first prompt and activity, its place in curator runs, and the text of the A2A tasks that ran in it (message snippet, reply, result and audit detail; the task and audit rows stay, without that text). It removes the Knowledge Base memberships its shares created. The session's row stays without content, so a link to it opens as erased. A curator run that was reviewing the session goes on without it; findings already in the Dreaming Backlog stay. An erased review (curator) session keeps its runs and proposals, which hold no transcript text: its pending proposals are declined and its runs finished. Knowledge Base documents the session wrote, skills already changed by approved proposals and server-side PostHog events stay; logs age out as above. Claude Code / Codex keep their own copy on the machine that ran the session (the user's machine, or the cloud machine's home on the operator's host); erasing in backlayer does not remove it. A review session keeps the text of the sessions it read, in the user's curator chat, until the user erases that review session.

Account deletion is on request to the instance administrator (the PRIVACY_CONTACT address shown on /privacy). For a full erasure the operator:

  1. removes the user from BACKLAYER_ALLOWED_EMAILS, so the next sign-in does not recreate the account;
  2. deletes the user's row from users. This cascades to everything the database keys to the user: sessions and transcripts, runners with their addresses, curator runs and proposals, projects with their credentials and shares, tokens, push subscriptions, A2A records, notice acceptances and Outline tokens. Credentials the user saved in other owners' projects belong to those projects and stay, with no author;
  3. deletes the shares of other users' sessions and projects that name the user's email (session_shares, project_shares), which are keyed by email, not by user;
  4. deletes the user's cloud machine (Settings, or Portainer), which removes its container and home volume;
  5. when PostHog is enabled, deletes the user's events, person and replays in PostHog by their pseudonymous id, recomputed from the user's id as above;
  6. lets the logs age out (30 days for the monitoring copy; the Docker engine's logs when the containers are recreated).

Knowledge Base documents and the user's Outline account are deleted by the team's own Knowledge Base admin.

Operator runbook

Who accepted which notice version, and when, as CSV:

docker exec <backend> backlayer acceptances

The columns are email,version,accepted_at. Every acceptance comes first, then one row with an empty version for each allowlisted user who has signed in but has not accepted the current version.

backlayer · Privacy