We keep the materials needed to audit a run.
Aculeus may store case prompts, uploaded sources, public URLs, receipts, hashes, excerpts, source ledgers, reviewer notes, feedback, traces, exports, and account-access records.
Privacy and data handling
Aculeus stores investigation data to preserve evidence, auditability, and user control.
This statement describes pilot handling for uploaded sources, public-record receipts, run traces, reviewer notes, exports, access requests, and operational telemetry.
Stored data supports evidence integrity.
The data is used to reproduce source paths, verify citations, debug failures, review training traces, measure provider spend, and preserve a case audit trail.
Production traces do not update models directly.
User activity can become scored training data only after review, export, eval, shadow deployment, and promotion gates. Raw production use is not a live model-update loop.
Retention is controlled by dry-run before deletion.
Runs, traces, receipts, exports, and access requests must have documented retention windows. Deletion candidates are listed by retention dry-run before any destructive cleanup.
Role gates limit who can see and export data.
Admins can operate pilot controls, reviewers can handle evidence workflows, operators can run approved retrieval, and viewers receive read-only access where permitted.
Customers can request deletion or export review.
Deletion, export, and correction requests should be routed through the account owner so evidence preservation, customer obligations, and audit needs can be reconciled.