Security at dPanel.ai

Security is core to dPanel.ai because you trust us to orchestrate your AI workspace and, optionally, to hold your provider keys. This page summarizes the safeguards we use. No system is completely secure — see the Terms of Service and Privacy Policy for the governing commitments.

1. Encryption

Traffic to dPanel.ai is served over TLS (HTTPS). Sensitive secrets — including provider API keys you store in the vault — are encrypted at rest and are not returned to the browser in plaintext.

2. Key Isolation (BYOK)

Your provider keys are used only to route your own model requests. They are not shared across accounts and are not injected into other customers' runtimes.

3. Access Control

Access to production systems is restricted to authorized personnel on a least-privilege basis. Administrative actions are authenticated and audited.

4. Payments

Payment-card details are collected directly by the Payment Partner identified at checkout; we generally do not receive or store complete card numbers. See the Payment Partner Notice.

5. Person-in-the-Loop & Audit

dPanel.ai is built around execution you control with approval gates and audit trails, so you can review and govern what your AI team does. Approval and guardrail features reduce risk but do not eliminate it — keep permissions least-privilege and review consequential actions.

6. Customer Environments

For self-hosted, local, or connected Boxes, you control the infrastructure: patching, credentials, backups, resource limits, and security remain your responsibility. See Terms of Service §4.

7. Responsible Disclosure

If you discover a vulnerability, please report it privately to [email protected]. We appreciate coordinated disclosure and will work with you to resolve issues promptly.