Data Handling
What Cynch collects, stores, and deliberately avoids.
Data Cynch observes
Cynch observes events and relationships within explicitly defined scope.
Metadata related to messages, decisions, and state changes
References between artifacts (links, IDs, relationships)
Timing and sequence information related to work events
Cynch does not ingest full message bodies, documents, or files beyond what is required to understand relationships.
Data Cynch stores
Stored data is limited to what enables continuity.
Event identifiers
Relationship mappings
Source references
Minimal metadata required for traceability and explainability
No data is stored without a continuity purpose.
Data Cynch does not store
Full message histories
Document contents beyond references
File bodies
Private communications outside permitted scopes
Behavioral analytics outside continuity scope
If data does not contribute to alignment, it is not retained.
Retention and lifecycle
Retention is policy-driven and customer-controlled
By default, retained metadata preserves continuity until removed by customer policy or source-system deletion.
Retention exists to support continuity, not analysis or optimization
Data usage boundaries
Observed data is never used for:
Advertising
Profiling
Performance scoring
Behavioral optimization
Observed data is used only to:
Detect continuity risks
Surface explainable signals
Data ownership
Source systems remain the system of record
Cynch does not claim ownership of user data
Deletion or access changes in source systems are respected
Cynch reflects reality. It does not redefine it.
Contact
For legal or data rights inquiries, see Contact.