Privacy
What backlayer stores about you and why. Administrators and data protection officers: see the full data-processing note.
What we store
In this instance's database:
- Your account email from sign-in.
- Runner and machine metadata for the computers that run your sessions, including the network address each last connected from.
- Full transcripts of your 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 you accepted, and when.
- Secrets you save for your projects (project credentials), encrypted. They can be written and listed by name but never read back through the app; agent sessions in that project can read them.
- Your Knowledge Base access tokens, encrypted, so backlayer can act in the Knowledge Base as you.
- Sign-in sessions, machine enrollment codes, runner, voice and A2A agent tokens, stored only as a hash.
- For A2A agent tokens you create: the tasks agents send with them (a short snippet of each message) and their results, and an audit log of those tasks.
- Who you share a session or project with, and the Knowledge Base document shares created for those shares.
- App state: your projects with their names and instructions, session titles and status, push-notification subscriptions, per-session token usage and which skills a session used.
Elsewhere:
- Knowledge Base documents, skills and the Dreaming Backlog, which live in the team's Knowledge Base.
- Server and container logs on the operator's host, and aggregate usage metrics with no user ids or text.
- PostHog, only when the operator enables it, under a pseudonymous user id (a keyed hash, not your email), with no message text, titles or document names:
- from the server: your sign-in (sent when you sign in, before this notice is accepted), and when you create a session, share a session or project, create an agent token, start a curator run, decide a proposal or erase a session, plus which interface features you use;
- from your browser: page views and, when enabled, session replay: a recording of how you move through the backlayer interface (clicks, navigation, timing); typed input, emails and names such as session, project and document titles are masked, and the chat, terminal, voice and curator areas are not recorded. PostHog receives your IP address and browser details with these requests.
Why we store it
- To show the chat view of your sessions.
- The curator ("Dreaming") reviews sessions you pick to improve the team's shared skill library.
- Product analytics and troubleshooting.
Curator reviews
- The curator reviews only sessions you pick yourself. Reviews of other members' sessions do not exist.
- Proposals from a review are recorded in the team-visible Dreaming Backlog as derived findings and links to the sessions you picked; raw transcripts are not copied there. Opening a link follows each session's existing sharing.
- You can keep any session out of future reviews from its menu. This applies to future reviews only and changes neither the session's sharing nor past proposals.
- Before you first use backlayer, a sign-in notice summarises this page; we record which version you accepted. A new version is shown to everyone again. Every version is kept verbatim and published at
/notices/<version>; the current one is /notices/2026-12.
Who processes it
- Anthropic, through your own Claude Code sign-in and subscription: your Claude Code sessions and the curator reviews you start.
- OpenAI, through your own Codex sign-in and subscription, when you use Codex.
- ElevenLabs, for voice, when the operator configures it: the call's audio and the Knowledge Base documents and skills the voice agent reads during the call.
- PostHog, for product analytics and session replay, when the operator enables it.
- The operator's mail provider, when email is configured: share and revoke emails (your email, recipients' emails, session titles, project names, Knowledge Base document titles and links) and security emails to you (agent token created or revoked, a machine connecting from a new network address).
- The sign-in identity provider (Google by default) and the hosting provider of this instance.
What we never store
Your Claude Code or Codex credentials or tokens: backlayer does not store or log them. You sign in only inside Claude Code or Codex in your machine's terminal. The sign-in link it prints passes through backlayer to the Chat card, and sign-in codes you type in the Terminal pass through backlayer to your machine like any other keystroke and are not stored. On a cloud machine, that sign-in is stored in the machine's home volume on the operator's infrastructure; on your own machine it never leaves it.
- Audio from dictation: speech recognition runs in your browser or OS (Chrome and Edge may send audio to Google/Microsoft, Safari to Apple); backlayer never receives audio.
Who can access it
- The instance operator can read the stored data (database, logs and containers) and holds the key to the encrypted items.
- Your team sees the skills and the Dreaming Backlog's findings and links; a link opens a session only under that session's existing sharing.
- When the operator runs the monitoring stack, accounts on the operator's sign-in domain can read the server and container logs.
- People you share a session with can read that session's chat and terminal. In a shared project, its owner and members can read every session in it, and their sessions there use the project's credentials.
- Agents holding an A2A token for a project, created by the project's owner, can run tasks there on the bound machine and read those tasks' results; their sessions use the credentials the project owner saved.
Retention
Transcripts and the rest of your data are kept until deletion is requested (a session and its transcript until you erase that session), except: finished A2A tasks and their results are deleted after 30 days; the A2A audit log is deleted after 90 days; the monitoring copy of the logs is kept 30 days, and the container logs on the operator's host follow the host's logging settings.
Contact and deletion
You can erase a session yourself from its menu: this removes it and its transcript from backlayer for good. Claude Code / Codex keep their own copy on the machine that ran the session (your 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 your curator chat, until you erase that review session. Findings already recorded in the Dreaming Backlog stay; their links then say that the session was erased. Account deletion stays on request to the administrator.
For questions or deletion requests, contact your instance administrator. On request, the administrator deletes your account and everything stored for it in this instance's database (sessions and transcripts, machines, curator runs, projects and their credentials, tokens, shares and the rest), your cloud machine, and, when PostHog is enabled, your events and replays there; logs age out. Knowledge Base documents and your Knowledge Base account are deleted by your team's Knowledge Base admin.
This notice is not legal advice.