Admin

Governance and data safety

Operate export, erasure, and retention controls with a separate admin guard.

API bearer

not set

Production routes may reject data-ops until the API bearer is saved.

Admin header

empty

Sensitive actions send this value only as X-Second-Brain-Admin-Token.

Database

check

Status endpoint has not confirmed migration state.

Corpus

0 sources

0 documents, 0 chunks visible to the admin console.

Operation setup

Choose the protected token and source before running data actions.

Admin tokenStored only in this page state; refresh clears it.Source

Select a source to preview the exact export/delete target.

Current state from the authenticated status endpoint.

Worker queueunknown

LLM modeunknown

Last documentNever

Return the selected source and documents as JSON.

Choose a source to enable export.

Delete the selected source and its indexed subtree.

Choose a source before enabling deletion.

Type selected source ID

Null retained raw text past the selected age while leaving searchable chunks intact.

Older than days

Scope: all documents with retained raw text older than 180 days. The indexed chunks remain available for search and chat until source erasure.

Keep destructive operations manual, source-scoped, audited by the backend, and separate from normal bearer-token access.

Export before erasure when you need a reviewable data snapshot.

Use retention purge for privacy cleanup; use source deletion for full erasure.

Do not paste the admin token unless you are actively running one of these operations.