Workspace data
Application inputs, outputs, and tool activity remain scoped to the workspace and its configured retention policy.
Privacy / system policy
Minimal collection, clearly governed.
Read the data ledger ↓
Operational telemetry, workspace content, and account data follow separate collection and retention controls.
Data boundaries
What Aurora handles—and why.
Operational telemetry
Latency, routing, policy outcomes, and errors are collected separately from prompt and response content.
Contact details
Project enquiries are used to respond to the request and coordinate the next conversation.
Clipboard access
The developer copy action writes only the selected code block to the clipboard when requested.
Operating scope
Privacy follows the deployed system.
A production deployment requires a policy tied to its legal entity, vendors, infrastructure, data flows, retention, user rights, and jurisdiction.