Privacy & data · Updated September 19, 2026
A clear data boundary.
This notice describes the data paths implemented in the current Aurelia codebase and the additional disclosures required before general availability.
What Aurelia processes
- A public wallet address when you choose to connect.
- A short-lived signature challenge used to prove control of that address. The signature does not authorize token movement.
- Credit balances, quote nonces and confirmed purchase events when the Credits service is enabled.
- Basic security and operational logs supplied by the hosting environment.
Prompts and model providers
When inference is enabled, prompt content is sent through Aurelia to the model provider selected for the request. The Aurelia Credits database is designed not to persist prompt or response content. Provider retention and training policies remain a separate boundary and must be reviewed for every enabled route.
What becomes public
Wallet addresses, token transfers, approvals, staking activity and contract interactions are public onchain records. They may remain visible permanently and can be analyzed independently of Aurelia.
Browser storage
Aurelia may use browser session storage for a short-lived authentication token and local interface state. Clearing site data or disconnecting removes the local session but cannot erase public blockchain records.
Retention and control
Operational retention periods, subprocessors and regional rights procedures will be published before general availability. Until then, Aurelia does not request a legal name, profile or seed phrase. Never provide a seed phrase or private key to Aurelia or anyone claiming to represent it.