This overview is informational. Your order form, Business Associate Agreement, Zero Data Retention Agreement, and other signed terms control if they differ from this page.
Compliance status
SOC 2 audit-ready
MSPilot’s security program is designed and operated against the SOC 2 Trust Services Criteria.
HIPAA on request
HIPAA is enableable with MSPilot. We accept Protected Health Information only under a signed Business Associate Agreement and through the services and configurations covered by that agreement.
Zero data retention
Capture is off for every client. Prompt and completion content is kept only after that client turns capture on.
Regional deployment
Customer environments can be deployed in the United States, Canada, the European Union, the United Kingdom, or Australia.
Security controls
MSPilot operates safeguards appropriate for a multi-tenant cloud service, including:- Multi-factor authentication for sensitive systems
- Role-based access control and least privilege
- Tenant isolation and authorization boundaries
- Encryption in transit and at rest
- Security and audit logging
- Vulnerability scanning and remediation
- Incident response procedures
- Tested backups and recovery procedures
- Vendor and subprocessor risk management
- Secure data retention and disposal processes
AI data handling
MSPilot does not use Customer Data to train third-party foundation models and does not sell Customer Data. We maintain written zero-data-retention terms with Microsoft Azure AI Foundry and Anthropic for the applicable services and resources. Retention is set per client on Conversations. Capture is off for every client until that client turns it on.- Zero data retention
- Optional AI analytics
- HIPAA
While capture is off for a client, prompt and completion content is processed to return a response and is not retained after the request is fulfilled. MSPilot may retain operational metadata needed to authenticate, secure, meter, support, and audit the service.
HIPAA safeguards
In the product, HIPAA shows as not enabled. Enable HIPAA opens a dialog that asks you to email support@mspilot.io. MSPilot turns it on with you before any protected health information is processed. A signed BAA is still required. A client with HIPAA enabled useshttps://{region}.hipaa-gateway.mspilot.io. That hostname is not proxied. Deployment shows the URL, and the install script and MDM profile use it. A device that is already enrolled switches to it on the next config pull. Do not point that client at https://{region}.gateway.mspilot.io.
For BAA-covered deployments:
- MSPilot acts as a Business Associate, or as a subcontractor to a Business Associate, for PHI processed through the services defined in the BAA.
- PHI is limited to approved services and configurations.
- Microsoft Azure and Anthropic are engaged under written business associate terms for the applicable services.
- Prompt and completion content is not used for model training.
- Access, security, incident response, breach notification, and secure disposal obligations are documented in the BAA.
- Customers remain responsible for using only approved workflows and for meeting their own HIPAA obligations.
Data residency
An organization has one home region. The client’s Environment tab shows Microsoft Azure, that region, and Production or Sandbox. It does not move the client between regions. MSPilot supports deployments in:🇺🇸 United States
Deploy customer environments in a supported United States region.
🇨🇦 Canada
Deploy customer environments in a supported Canadian region.
🇪🇺 European Union
Deploy customer environments in a supported European Union region.
🇬🇧 United Kingdom
Deploy customer environments in a supported United Kingdom region.
🇦🇺 Australia
Deploy customer environments in a supported Australian region.
Privacy and data rights
Our Privacy Policy explains what personal data we collect, why we process it, how we share it, and the rights available to individuals. You can request access, correction, export, or deletion of personal data by emailing support@mspilot.io. When MSPilot processes data on behalf of an MSP, we coordinate with that MSP to support the request.Service providers
MSPilot uses service providers for infrastructure, AI inference, analytics, monitoring, and other operational functions. The current Privacy Policy is the source of truth for our public subprocessor disclosures. Current disclosed providers include Microsoft Azure, Vercel, Cloudflare, Anthropic, Microsoft Azure AI Foundry, PostHog, and Sentry.Security documentation
Customers and prospective customers can request security materials, subject to appropriate confidentiality requirements. Available materials may include:- Security questionnaires
- Architecture and data-flow information
- Security and privacy policies
- Control descriptions and supporting evidence
- Penetration-test information
Legal resources
Privacy Policy
Review how MSPilot collects, uses, protects, and shares personal data.
Terms of Service
Review the terms governing use of MSPilot.
Cookie Policy
Review the cookies and similar technologies used by MSPilot.
Contact MSPilot
Ask about compliance, security, privacy, BAAs, or retention options.
Frequently asked questions
Is MSPilot SOC 2 compliant?
Is MSPilot SOC 2 compliant?
MSPilot’s security program is designed and operated against the SOC 2 Trust Services Criteria, and all controls and evidence are complete.
Can MSPilot process PHI?
Can MSPilot process PHI?
Yes, but only after both parties sign a BAA and confirm the applicable services, models, region, and configuration are covered.
Does MSPilot train models on Customer Data?
Does MSPilot train models on Customer Data?
No. MSPilot does not use Customer Data to train third-party foundation models.
Can we choose our retention period?
Can we choose our retention period?
Capture is off for every client, so nothing is stored until that client wants it. When capture is on, a workspace admin picks 30, 90, 365 days, or indefinite on the client’s Conversations tab. See Conversations.
How do HIPAA retention settings differ?
How do HIPAA retention settings differ?
The same rule applies. Capture is off for every client until that client enables it. A BAA does not store prompts, and it does not turn capture on. Operational metadata and logs for usage, security, and HIPAA audit evidence can still be kept.