Beta data handling and account requests

Data used by the workflow

Snabb retains account identity and authentication records, selected project/source/workspace data, command output and artifacts, agent conversation/usage records, publication/preview identities, and billing/audit receipts needed by the selected workflow. A connected model provider handles the model requests under that provider’s account and policies.

Project secrets are write-only selections stored through the existing secret service. Secret groups require explicit selection. Provider connection credentials have their own custody and return lifecycle. Do not treat a global group scope as automatic injection into every agent command.

Saved workspace checkpoints are encrypted. Owner-private previews require their normal authenticated access handoff. These controls do not certify every possible artifact, transformed secret output or root-modified guest audit instrument.

Retention and deletion

Defaults include 90-day retained command output, 24-hour bounded live context and a seven-day archived workspace window. Project artifact/checkpoint settings and provider deadlines are separate. Effective settings, references, read leases and existing publication claims govern cleanup; the default is not a promise that every kind of data shares one deadline.

Permanent project deletion closes project access and new admissions first. The existing erasure owners remove registry references, secrets, object versions and project content and then verify expiry of outstanding write authorizations. A deleted project tombstone and financial/audit records are retained under their existing purposes. A project deletion receipt is separate from an account-wide deletion request.

An already-owned mirrored image can remain executable after its source credential is removed. Removing a Snabb secret does not revoke the token at Docker Hub, GitHub or another provider. Platform caches and provider-side physical retention have separate policies.

Request an account export or deletion

1. Sign into the owning account and open Organisation → Trust centre → Request an account data action.
2. Choose account export or account deletion in your request, identify the account and any projects that must be preserved, and retain the request identity. Keep passwords and tokens out of the message.
3. A service administrator verifies account authority, scope, shared project/payer boundaries and applicable retention before preparing an export or executing deletion. Submission alone does not fulfill the request.
4. Completion must be confirmed with the export’s verified delivery identity or the deletion disposition and retained-record explanation. Requests remain pending until that happens.

This is a manual process. General product support and a response-time commitment are not offered during this controlled preview. Published DPA and certification documents are not currently available in the portal; the request workflow does not imply their delivery.