- Every client gets their own server, their own database bound to localhost and their own encrypted credential store; there is no shared data pool.
- We do not use your data to train AI models. To do their work, agents send text to an AI model provider, so your data is shared with that provider for that purpose.
- Credentials are encrypted at rest with AES-256-GCM and every access is logged.
- MyZone runs automated security checks, and we commit to notifying affected clients within 72 hours of a breach.
- Your data and the custom work built specifically for you stay yours, unless your agreement says otherwise.
Is my data kept separate from other clients?
Every client gets their own server, their own database bound to localhost, and their own encrypted credential store. There is no shared data pool, so your data is kept separate from other clients by design.
Application and agents run under separate system users with isolated permissions. One organization's data is kept separate from another's by design.
Which security controls protect my server?
Server hardening
- TLS 1.2 and 1.3 only. Weak ciphers (RC4, DES, 3DES, NULL, EXPORT) are blocked.
- Firewalled ports. Only what's needed is open.
- Key-only SSH. Passwords are disabled, and repeated failed logins trigger automatic IP banning.
- Unattended security updates, so critical patches land promptly.
- No version disclosure, and no stack traces or internal paths in error responses.
Data handling
We access your data only to run and support your system, as your agreement sets out.
- We do not use your data to train AI models.
- No analysis or aggregation of your conversations.
- Calls to model providers go directly to the provider and back, not through us.
- Server access only to run, maintain and support your system, as your agreement sets out.
Credentials
- Encrypted at rest with AES-256-GCM before they ever touch the database.
- Accessed only through a logged credentials service, every access recorded.
- Our rules keep credential values out of chats and logs.
- Automated leak detection scans logs, memory, and documents for accidentally exposed secrets.

How is security checked after launch?
MyZone runs an automated security loop with three phases: offensive scanning, defensive monitoring, and a full audit pass. We will confirm in writing how often it runs on your server and how findings are handled.
Probe for weakness
Looks for leaked secrets, injection surfaces, over-privileged access, tampered code, poisoned memory, and exposed endpoints.
Watch for drift
Monitors dependency vulnerabilities, configuration drift, behavioral anomalies, audit-log integrity, and the external perimeter.
Verify and report
Confirms the loop ran completely, scores its integrity, and compiles a report with any escalations.
External perimeter checks
Certificate health and expiry monitoring, protocol and cipher validation, and DNS security records (SPF, DMARC, CAA).
Zero-trust posture
Finite session lifetimes, no wildcard permissions, credential-access logging, and alerts on dormant agents or stale credentials.
We describe the model and the coverage here, not the specific tooling.

How are files and web pages screened before they reach the AI?
Agents read files and fetch URLs. We will confirm in writing the safeguards that apply when agents read files, email and web pages.
Governance, Response & Recovery
Severity tiers and response times
Human approval is required before any high-impact action. Each access to saved passwords and keys is recorded.
Backups and recovery
- We will confirm in writing what is backed up, how often, where the backups are kept and how fast we can recover.
- Daily, weekly, and monthly database backups, stored separately.
Breach notification
In the event of a security breach, we commit to notifying affected clients within 72 hours.
Choose your data residency
Pick where your server is hosted. Regions include:
- Europe (Germany, Finland)
- US East (Virginia)
- US West (Oregon)
- Asia Pacific (Singapore)
Custom arrangements are available on request.
| Severity | What happens | Response |
|---|---|---|
| Critical | Handled within support hours. We do not provide 24/7 monitoring or emergency response. | Support hours |
| High | Investigated and a fix planned. | Support hours |
| Medium | Triaged and scheduled. | This week |
| Low | Bundled into routine maintenance. | Next maintenance window |
Trusted Providers
We integrate with providers who maintain strong data practices, and we keep the list short and transparent.
- Your hosting region is provided by an infrastructure partner subject to the data regulations of your chosen region.
- Stripe handles billing, with no card data stored on your server.
What happens to my work if I leave?
Your data and the custom work built specifically for you stay yours, unless your agreement says otherwise. The MyZone platform that runs the agents stays MyZone's. Contract term and notice are in your agreement. We will confirm in writing how an export of your work is done, what it includes, and how your data is deleted from our systems after you leave.
Read the full ownership & portability guide →
We lead with concrete controls because they're strong on their own, and we don't overstate what we haven't earned.