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 account email from the identity provider's sign-in. backlayer stores no name.
- Runner metadata for the machines a user enrolls (name, runner version, installed harnesses, when and from which network address it last connected).
- The full transcripts of the user's Claude Code and Codex sessions: prompts, replies, tool calls and their output, uploaded by the runner.
- Curator ("Dreaming") runs and their proposals.
- Which version of the sign-in notice each user accepted, and when.
- Project credentials: secrets users save for a project (
project_credentials), sealed server-side with AES-GCM under a key derived from the instance secretBACKLAYER_TOKEN_KEY. The API is write-only: it lists names and dates, never a value. Agent sessions in that project (its owner's and members') read the values through the runner; a session leased to an A2A context reads only the values the project owner last wrote. - Knowledge Base access tokens: each user's Outline OAuth refresh and access tokens (
outline_tokens), AES-GCM encrypted under the same key. - Tokens stored only as a SHA-256 hash: web sign-in sessions, machine enrollment codes, runner and session tokens, voice-call tokens, and A2A agent tokens (the agent token's plaintext is shown once, at creation).
- A2A: each agent token's binding (project, runner, harness) and expiry; A2A contexts and tasks, with a 200-character snippet of each task's message and the task's result, and the addresses a task asked to share its session with and the outcome for each; and an audit log of task events.
- Sharing records: who a session or a project is shared with (by email), including shares an A2A task requested on the owner's behalf (the session only), and the Knowledge Base document shares backlayer creates for the other shares.
- App state: projects with their names and instructions, session titles and status, push-notification subscriptions, per-session token usage, which skills a session used, and similar records the interface needs.
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:
- From the backend:
login(sent at sign-in, before the sign-in notice is shown or accepted),session_created(kind, harness, whether it has a project, whether it is a tandem secondary),session_shared,project_shared,agent_token_created(harness, lifetime in days),curator_run_started,curator_proposal_decided(approved or not),session_erased, and the allowlisted interface events ofPOST /api/usage. Each carries a pseudonymous user id,hex(HMAC-SHA256(BACKLAYER_TOKEN_KEY, user id))[:32], and no email, title, prompt, document name or transcript text. The Settings switch does not stop these. - From the browser:
$pageview,$pageleave,$identifyunder the same pseudonymous id, and a masked session replay of the backlayer interface (typed input, emails and titles masked; the chat, terminal, voice and curator areas not recorded). PostHog receives the browser's IP address and user agent with these requests. Each user can switch the browser side off in Settings.
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:
- the sign-in link the CLI prints travels from the runner to the server and is shown on the session's Chat card, held in memory only while the sign-in runs;
- the code the user pastes in the Terminal travels to the machine like any other keystroke.
Dictation audio never reaches backlayer: speech recognition runs in the user's browser or operating system.
Who can access it
- The instance operator can read everything above: the database, the logs and the containers. The operator also holds the key that decrypts project credentials and Knowledge Base tokens.
- Monitoring: with the operator's optional monitoring stack, every account on the operator's Google domain signs in to Grafana as Editor and can read the container logs.
- On a cloud machine, the user's Claude Code / Codex sign-in is stored in that machine's home volume on the operator's host. On the user's own machine it never leaves that machine.
- The team sees the skills and the Dreaming Backlog: findings derived by the curator and links to the reviewed sessions, never raw transcript copies. A link opens a session only under that session's existing sharing.
- People a session is shared with (including shares an A2A task requested on the owner's behalf) can read that session's chat and terminal, read-only.
- The owner and the members of a shared project can read every session in that project, read-only, and their sessions in it use the project's credentials.
- Agents holding an A2A token for a project: the project owner creates the token; the agent can start tasks in that project on the bound machine and read those tasks' results, and its sessions read the credentials the project owner last wrote.
Reviews
- The curator reviews only sessions their owner picks; the review runs as a session on one of the owner's machines, under the owner's own Claude Code sign-in, and every skill change waits for the owner's approval.
- An owner can keep any session out of future reviews from its menu. This applies to future reviews only: a review already started and past proposals stay as they are, and the session's sharing does not change.
- Users accept a versioned sign-in notice before using the web interface; the acceptance is recorded per user and version. Every version is kept verbatim and published at
/notices/<version>; the current one is/notices/2026-12. - Reviews of other members' sessions do not exist. They are a precondition of any team-wide or scheduled review, and such a review ships with a customer-controlled switch, off by default.
Providers and subprocessors
- Anthropic, through the user's own Claude Code sign-in and subscription: sessions, and the curator's reviews of the sessions the user picks.
- OpenAI, through the user's own Codex sign-in and subscription, when the user uses Codex.
- ElevenLabs, when the operator configures voice: the call's audio, and the Knowledge Base documents and skills the voice agent reads through its tools during the call.
- PostHog, when the operator sets
POSTHOG_KEY: the events and replay described above. - The operator's SMTP mail provider, when the operator sets
SMTP_HOST: share and revoke emails (owner and recipient emails, session titles, project names, Knowledge Base document titles and links), and security emails to the user (a new agent token, a revoked agent token, a machine connecting from a new network address, which the email names). - The OIDC identity provider used for sign-in (Google by default).
- The hosting provider of the instance.
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:
- finished A2A tasks (with their snippet and result), and ended A2A contexts with no task left, are deleted after 30 days;
- A2A audit rows are deleted after 90 days;
- the monitoring stack's log copy (VictoriaLogs) is kept 30 days;
- the Docker engine's own container logs have no limit set by the backlayer stack: they follow the host's Docker logging configuration and live as long as the container.
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:
- removes the user from
BACKLAYER_ALLOWED_EMAILS, so the next sign-in does not recreate the account; - 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; - 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; - deletes the user's cloud machine (Settings, or Portainer), which removes its container and home volume;
- 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;
- 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.