How we handle the data you connect to us.
Fydelitics ingests behavioral and audit-log data from systems like Microsoft Purview and Agent 365 as part of Readiness Control Plane's Demonstrated readiness signal. Here's what governs how that data is handled today.
What governs how we handle enterprise data.
Encryption in transit and at rest
Data connected to Fydelitics is encrypted both while moving between systems and while stored.
Least-privilege access
Access to customer data is scoped to what a given role actually needs.
Data minimization
We ingest what's needed to compute readiness signals, not a wholesale copy of every connected system.
Consent-scoped ingestion
Behavioral data ingestion is authorized at the organizational level, with a documented notice process.
Sub-processor transparency
Any third party that touches your data is disclosed, not hidden.
No model training on your data
Your data computes your own readiness signal — not used to train models for other customers.
What to ask us directly.
Real, current answers on data residency, retention periods, incident response, and sub-processors are available on request.