Updated 2026-09-30
Data Retention
Current retention posture for account, workspace, document, output, telemetry, and audit data.
PRAXIS is part of TACITUS, an independent experimental project operated by Giulio Catanzariti. No TACITUS legal entity has been incorporated. Institutional terms, data handling and contracting parties must be established before an evaluation. Nothing on this page excludes rights or liabilities that applicable law does not allow to be excluded.
Workspace Data
Workspace data is retained while an account or workspace remains active so PRAXIS can provide continuity across saved context, conversations, source receipts, documents, and outputs.
Generated artifacts and audit receipts are retained with the workspace unless deleted through supported product or support workflows.
Retention includes original uploaded files where stored, full extracted text, chunks/embeddings, capsule and review versions, conversations and generated products. Removing an attachment from a question does not itself erase these records.
Operational Data
Operational logs, health checks, runtime ledgers, and security audit artifacts are retained for reliability, abuse prevention, and incident response.
Logs, model traces and saved review/test evidence require separate handling from the main workspace. Redacted release evidence is not a guarantee that every operational record contains no user-derived text.
The beta does not publish a single fixed retention period covering every workspace, operational, backup and provider record. Specific periods and exceptions must be confirmed for the actual store and configuration; no retention days are implied here.
Deletion
Account deletion is treated as an erasure request where applicable. Completion must be checked across owner-scoped workspace records, uploaded and generated files, runtime records and relevant traces. Deleting an authentication account alone does not establish that all copies have been erased.
The supported erasure workflow retains a minimal deletion marker and cleanup receipt. Billing webhook deduplication and provider accounting, platform logs and backups, shared published ontology records, and optional external indexes require their own retention or cleanup handling. A pending external cleanup is not reported as completed erasure.
Legal, billing, security or backup exceptions and external provider records may require separate handling. Request a scope/status confirmation through security@tacitus.me; the current beta does not promise immediate removal from every backup or provider system.