Support

Quick checks

Before contacting support

1. Confirm that you installed the official burnbook npm package.
2. Run burn doctor to inspect collector availability and configuration.
3. Run burn status to confirm authentication and the last successful sync.
4. Run burn sync once and note its content-free success or error category.

Safe support bundle

Do not send transcripts

A useful support report includes the output of burn --version, operating system, collector name, the error category printed by the CLI, and approximate time. Remove usernames and company information when they are not necessary.

Never send prompts, responses, source files, diffs, terminal history, API keys, device tokens, signing keys, or MCP credentials.

Email the safe metadata to tech@burnbook.dev. Suspected vulnerabilities belong in the separate security reporting process.

Device management

Revoke server access or remove local state

1. Open Dashboard → Device credentials to review a device's label and last use.
2. Select Revoke to stop that device credential from making future Burnbook API requests.
3. Run burn uninstall on the device to remove Burnbook-owned hooks and scheduling.
4. Decide whether to sync or discard queued evidence before deleting the local Burnbook directory with your operating system's file manager.

Revocation and burn uninstall do not erase the local signing key, device token, cursors, or spool. Burnbook has no CLI command that silently deletes those files.

Account deletion

Delete server data from the dashboard

1. Remove automation on each device with burn uninstall.
2. Open Dashboard → Delete all Burnbook data.
3. Enter your handle and select Delete account.
4. Delete the local Burnbook directory separately on every device if you do not want to retain local keys, credentials, cursors, or queued evidence.

Account deletion removes the active server account, evidence, snapshots, device credentials, and settings and ends existing Burnbook sessions. It cannot delete files stored on your devices. The privacy note explains backup retention.

Evidence integrity

Reviews and appeals

Integrity states protect the meaning of public credentials without presenting an automated signal as a public accusation. Burnbook does not publish detector details or enforcement thresholds.

• Active: evidence is in good standing and can become publicly eligible when the other publication requirements are met.
• Under review: public profiles, credentials, and rankings are temporarily hidden while the evidence is reviewed.
• Cleared: review is complete and evidence can become publicly eligible again.
• Banned: evidence remains excluded from public credentials and rankings after an integrity decision.

Requesting a review

1. Open the Evidence integrity panel in your private dashboard.
2. Select Request integrity review. Only one request can be pending at a time.
3. A reviewer evaluates the content-free evidence and audit history already held by Burnbook. Do not submit transcripts, code, credentials, repository content, or company information.
4. An approved appeal changes the account to Cleared. If the decision is upheld, the existing integrity state remains in place.

Review requests do not guarantee a particular outcome or resolution time. You can continue using private account controls while a review is pending.

Evidence V2

Upgrade before the V1 window closes

Burnbook accepts Evidence V1 for 30 days after production activates V2. The API advertises the exact deadline through its Sunset header. After that deadline, V1 syncs return 426 Upgrade Required; already accepted evidence remains on your account.

1. Install the latest official package with npm install -g burnbook@latest.
2. Run burn doctor and confirm your collector is available.
3. Run burn sync. Pending content-free evidence remains in the local spool until acknowledged.
4. Run burn status and confirm the latest supported snapshot.

Upgrading never requires uploading transcripts, source code, paths, diffs, commands, reasoning, or tool payloads. If migration fails, keep the spool intact and send only the safe support metadata above.