RESOURCES · DOCS · AGENT STUDIO · TRUST

Privacy and telemetry

What stays local, what telemetry can be enabled, what exports contain, and how redaction works.

Talk to AI Labs All docs

SECTION

Trust

Where this entry sits in the docs index.

READ TIME

8 min

Pace it for a coffee or a coffee break.

SECTIONS

Each one stands alone and is copy-paste safe.

INSTRUMENT READOUT · TRUST

THE WALKTHROUGH

What you will actually do.

STEP 01

↳ TRUST

Default posture

Telemetry is off by default. When enabled, events cover product actions such as connect, compose, record, replay, export, crash opt-in, and update checks. Trace payloads, API keys, prompts, tool outputs, headers, and local file paths are excluded or redacted.

The user can inspect the local event log before anything is sent and can disable telemetry from Settings at any time.

Provider keys live in the OS keychain on desktop.

↳ CHECK

Trace cards redact secrets before export.

↳ CHECK

AuraOne intake packets show a privacy preview before upload or contact-form handoff.

↳ CHECK

Crash reports require explicit opt-in and scrub local paths.

↳ CHECK

← PREVIOUS

FAQ

Sandbox guide

TRUST

Next time, it's already a replay.

The path you just read becomes the path you can repeat. One trace, one artifact, one gate the next release has to clear.

Talk to AI Labs All docs

Privacy and telemetry | Agent Studio Open Docs