Code.
No file contents, prompts, model output, tool arguments, or environment variables in telemetry.
Trust
Trust is a product feature.
What Picasso sees. What it never sees. What you control.
picasso / trustindexed
Trust
Trust is a product feature
What Picasso sees. What it never sees. What you control.
CodeNo file contents, prompts, model output, tool arguments, or environment variables in telemetry.
Identity in eventsNo IP addresses, raw account IDs, provider keys, OAuth tokens, or subscription balances in telemetry.
Financial detailNo per-user financial numbers in telemetry events.
picasso telemetry logpicasso telemetry export > events.jsonpicasso telemetry deleteWhat stays out.
Identity in events.
No IP addresses, raw account IDs, provider keys, OAuth tokens, or subscription balances in telemetry.
Financial detail.
No per-user financial numbers in telemetry events.
What can be collected.
Session shape.
Counts, duration, model family, tokens, and cost bands.
Loop events.
Counts, durations, and error rates.
Tool events.
Per-tool counts and timings.
Crash reports.
Path-redacted crash data.
Memory privacy.
Memory is retrieval data for your account. It is not training data. It is not shared with sponsor systems. You can inspect it, export it, edit it, and clear it.
Studiomemory / plans / goals / replay
memorysketchescanvasesgoals
memoryauth module uses argon2id
plan3 files, 2 risks, 4 checks
goal62 percent complete
replay48 strokes recorded
Evidence is redacted by default.
Operational records can prove setup gates, provider validation, managed usage, sponsor attribution, drift checks, and export receipts without exposing code, prompts, model output, tool arguments, provider credentials, or memory contents.
Redacted exports.
JSON and CSV exports remove sensitive fields before audit receipt creation.
Immutable receipts.
Export artifacts can carry row counts, digests, retention metadata, and audit linkage.
No-evidence states.
Admin pages show missing evidence plainly instead of filling the gap with assumed readiness.
Support records stay scoped.
Support and admin records are redacted by default. Raw session, goal, memory, or episode-package evidence requires a user-initiated, scoped, time-boxed support grant.
Time boxed.
Access windows expire instead of becoming standing permission.
Scoped.
Grants describe the evidence class they allow.
Audited.
Support access is treated as evidence, not background access.
Cache policy has privacy boundaries.
Cache policy defaults to observe or private behavior, derives provider cache keys from a stable workspace fingerprint, and leaves file-content caching off unless explicitly allowed.
Public-safe artifacts.
Cache evidence redacts prompts, code, memory bodies, tool output, credentials, ad metadata, and raw account IDs.
Provider capability.
Cache hints can be blocked when the route or model does not support the requested mode.
No silent sharing.
Cache behavior is policy, not an implied side effect.
Telemetry controls.
Telemetry is designed around product health, not code collection. Usage telemetry is opt-in, crash reporting is independently controllable, and the scrubber rejects or redacts sensitive keys, secrets, PII patterns, prompts, code, memory, file content, credentials, and financial data before events are accepted.
picasso telemetry logpicasso telemetry export > events.jsonpicasso telemetry deleteData deletion.
Memory and account state are not meant to be hidden storage. The control surface gives users direct commands for clearing retained project context and account data.
picasso memory clear --allpicasso auth delete-account