Security & Trust

Dashboard access requires authenticated accounts. Customer data access is scoped through application authorization and database row-level security where configured. Administrative control-plane functions use separate role checks.

Applications run in isolated containers with controlled CPU and memory allocations. Deployment scheduling and worker capacity controls are designed to keep workloads within assigned resources.

Environment secrets are handled separately from ordinary project metadata and are not intended to be displayed back in plaintext after storage. Users should rotate credentials immediately if they believe a secret has been exposed.

Stripe handles payment collection and payment-method management. Deploy Hatch stores billing identifiers and entitlement state needed to operate subscriptions, not full card details.

Deploy Hatch tracks deployment lifecycle state, worker health/capacity, billing webhook processing, notification delivery, and selected operational exceptions. Customer-facing errors are separated from internal diagnostics to reduce unnecessary information exposure.

You remain responsible for your source code, dependencies, application authentication, credentials, data handling, and the behavior of software you deploy. Keep dependencies patched and use least-privilege credentials.

If you discover a potential security issue, use Support. Do not include live secrets in a report.