Transparency
Cynch only observes what you explicitly allow.
Principle: Explicit allowlists
- Default is observe nothing.
- Scopes are explicit allowlists.
- Removing scope stops future ingestion only.
- No retroactive backfill.
Observed vs Not Observed (Across All Providers)
Observed, when explicitly scoped:
- Identifiers needed to route and correlate work (IDs, URLs, timestamps)
- Relationship signals linking conversations, decisions, and artifacts
- Minimal metadata required for traceability and explainability
Not observed by default:
- Full content bodies (messages, documents, files)
- Private communications outside explicit scope
- Secrets
- Behavioral or usage analytics
Enforcement boundaries
- Out-of-scope data is dropped at ingestion
- Scope is revalidated during processing
- UI reflects allowed scope explicitly
- No backfill occurs when scope changes
Credentials + access
- Credentials are stored as secrets to perform scoped ingestion
- Disconnecting stops future ingestion
- Visibility never exceeds source permissions
Retention and deletion
- Policy-driven and customer-controlled
- Default retains ingested metadata to preserve continuity unless removed by customer policy or disconnection
- Avoid retention-dependent features that require backfills
Exportability
Export tooling planned; contact if a snapshot is required before first-class export support.
Status semantics
- Ready: no action required
- Action needed: misconfiguration or unresolved continuity risk