← Back to backlayer
Privacy notice

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:

Elsewhere:

Why we store it

Curator reviews

Who processes it

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.

Who can access it

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.

backlayer