Data & usage

nvoken stores the data required for its runtime responsibilities: Agent revisions, Turn execution state, optional Conversation transcripts, optional MemorySpace content, tool work, checkpoints, and usage evidence.

Your application remains authoritative for users, membership, product data, permissions, billing, and product-level orchestration.

Usage follows immutable Turn facts

Every model call is attributed from the exact admitted Turn: App, tenant, actor, Conversation, MemorySpace, behavior source, Agent revision when present, and narrowed limits. Reporting never re-resolves an Agent's current revision.

Use the usage time-series, breakdown, and record APIs for operational reporting. Keep your own billing ledger when your product charges customers; nvoken usage is evidence, not your customer invoice.

Content erasure does not rewrite accounting

Deleting a Conversation, MemorySpace, or eligible Turn erases its retained content according to that resource's contract. Model-call and other operational facts can survive with immutable attribution so deletion does not restore spend capacity or change past usage totals.

Standalone Turn content has bounded retention even though its execution record remains durable. Conversation retention and compaction are configured explicitly when continuity is selected.

Secrets

Machine credentials are shown once. Reusable provider keys and delivery secrets are encrypted at rest. Caller-ephemeral provider keys are retained only as long as accepted work needs them for recovery, then cleared after settlement.

Do not put product secrets in metadata, logs, or MemorySpace namespaces.