Security

Resilis manages the service boundary and supported cloud operations. Customers must protect their source repositories, GitHub connections, accounts, credentials, configuration, authorized users, and agents.

Review deployment, configuration, logs, metrics, and recovery actions before treating a production change as safe. Use the least access needed for each operation.

Resilis supports managed databases and object storage for supported application paths. Backups, snapshots, and restore workflows depend on the resource and its configured protection path. Keep independent copies of data that you cannot replace.

Data locations, retention, recovery objectives, and other commitments depend on the service or order. This page does not promise a region, retention period, recovery time, or uptime.

The public Terms and Privacy Notice do not state a certification or a complete security-control inventory. Request service-specific security information from support before relying on a control, certification, region, subprocessor, or incident-notification time.

Resilis does not promise that the internet or every transmission will be completely secure. Customers must use a secure environment and must not place secrets, private keys, passwords, tokens, or production credentials in support reports.

Email [email protected] with the affected service, the time of the event, and safe details that help investigation. Do not send credentials or exploit material. Any incident-notification duty follows the applicable Terms, DPA, order, and law.