Analytics data is stored in a location selected by the customer—currently New York (US), Amsterdam (Netherlands), or Sydney (Australia). Our global infrastructure is geo-distributed and operates on an anycast network. For more information, please visit our Network Map
We minimize data collection. We only require basic account information (email, org name). If Analytics is enabled, we log DNS queries and metadata (e.g. source IP, hostname, MAC address if the agent is installed). See Log Reference
All data is encrypted using AES-256 at rest and TLS 1.2+ in transit.
Yes. You can delete all Analytics (DNS log) data at any time via the Dashboard.
Yes, in two optional features:
Yes. Admins can enforce:
Yes, Control D achieved SOC 2 Type II compliance in June 2025, with auditors ensuring that the company has top-tier internal security protocols to protect all sensitive data.
Yes, for more information on how Control D facilitates GDPR compliance, please refer to our blog post on the topic.
Yes. Control D meets Microsoft’s Supplier Security and Privacy Assurance (SSPA) requirements, confirming our adherence to Microsoft’s Data Protection Requirements (DPR) for safeguarding sensitive and high business impact data. Our compliance is reviewed and attested through the SSPA program.
No. Customer data is never used to train our AI systems.
We strive for accuracy, and while AI models can sometimes generate incorrect information or "hallucinations", our support chatbot is designed to minimize these occurrences. For our malware filter, false positives are a possibility, but administrators have full control over its aggressiveness settings to ensure optimal performance.