Security & Data Handling
This page explains, at a high level, how SynapticWorks approaches data security and handling so teams know what to expect when operating the platform.
Tenant isolation
SynapticWorks is designed with tenant isolation so each customer workspace is separated from others. This separation helps prevent cross-tenant visibility and supports safer multi-tenant operations.
In simple terms: one customer's data is not mixed into another customer's working context.
Data retention
By default, operational data is retained for 90 days.
Why retention exists:
- To support troubleshooting and reliability investigations
- To provide recent usage and operational reporting
- To help teams review recent workflow outcomes
After the retention window, data is removed according to platform retention processes unless different terms apply in your plan or agreement.
Anonymization of logs and messages
SynapticWorks applies anonymization practices to reduce direct exposure of sensitive information in logs and operational records where possible.
Examples can include:
- Masking direct identifiers
- Reducing raw payload visibility in selected log contexts
- Keeping operational metadata while minimizing personal detail
GDPR posture (high level)
SynapticWorks is built to support customers operating under GDPR expectations, including data handling controls and retention boundaries.
This page is not legal advice. For legal interpretation, customers should consult their counsel.
What users can generally expect:
- Clear retention behavior
- Separation of tenant data
- Operational controls that support responsible data handling
What data is logged vs what is stored
Logged data is typically used for platform operations, observability, and incident response.
Stored data supports product functionality, workflow state, and recent history available to users.
Not every stored field is logged, and not every log event contains full data payloads.
Public vs private doc distinction
Public documentation (like this page) describes platform behavior at a general level.
Private or customer-specific documentation may include implementation details, environment-specific settings, or contractual security terms.
Common data handling questions
### Is sensitive user message data stored forever?
No. By default, operational data follows a 90-day retention window unless your plan or agreement states otherwise.
### Can one customer view another customer data?
No. SynapticWorks uses tenant isolation to keep customer workspaces separate.
### Are logs the same as primary stored records?
No. Logs are mainly for operations and troubleshooting. Product storage supports feature behavior and recent historical access.