Back to home
veilink / Privacy

Privacy includes the product itself.

Understand where each request and record goes.

Persistent public records

The local service stores public execution, refund and team approval records in user-local SQLite. It does not store signed transaction bytes, raw proofs, wallet keys or raw recovery tokens. Private worker sessions are cleared on lock or wallet change.

Providers receive required request data

RPC and quote requests share required public addresses and amounts. Privacy indexers and relayers process protocol requests. Public addresses remain public even when displayed inside a privacy workspace.

Inference requires data sharing

Only a submitted question and selected quote are sent to Gateway and model providers. Balances and history are not appended automatically. Never paste secrets; provider data policies apply.

Real exports have consequences

Invoices, signed statements and encrypted exports are real user-created documents. Clipboard and downloaded records remain under your control. Hiding a page cannot revoke copies already shared.

Continue exploringExplore workspace