astralaneAstralane / Developers
Privacy and retention
The primary database records operational metadata, not prompt or generated response bodies.
What is persisted
Workspace/key identity, public/selected model, route metadata, token counts, costs, latency, status, attempts, and accounting entries. A keyed HMAC request fingerprint supports idempotency without retaining the request body. Raw prompts and outputs are not logged by the application.
What still sees the content
The browser playground, gateway memory, and selected upstream process requests during execution. Upstream retention is governed by the actual provider contract; metadata-only Astralane storage is not the same as upstream zero retention.
Zero data retention
zdr:true accepts only routes and accounts explicitly configured for contractual ZDR. The flag does not create a provider commitment. An operator must review the real agreement before enabling the capability.
Production privacy work
Before public launch, review log infrastructure, error-reporting payload filters, backups, retention periods, deletion workflows, subprocessors, privacy notice, data-processing agreements, and legal requirements. This page is technical product documentation, not a finalized legal privacy policy.
Native core and mock HTTP checks have run. Full dependency install, PostgreSQL/Redis integration, production builds, and browser flows still require local verification. See the repository verification report before deployment.