Residency model
Cloudryption data residency is governed by the customer agreement, selected deployment model, subprocessors, and hosting region. For enterprise deployments, residency expectations should be confirmed during procurement and onboarding.
Data locations
Cloudryption stores and processes customer-authorized cloud metadata in the agreed service environment. Some operational metadata, support communications, email delivery, backups, or security logs may be processed by approved subprocessors listed in the subprocessor page.
International transfers
Where personal data is transferred across borders, Cloudryption uses contractual and organizational safeguards appropriate to the processing relationship, including DPA terms and subprocessor review.
Backups and logs
Backups and operational logs may be retained in protected infrastructure for reliability, security, and incident response. Retention periods and deletion behavior are documented in the data-retention policy and backup/DR summary.
Customer actions during evaluation
- Confirm required hosting or residency constraints.
- Review subprocessors and objection rights.
- Agree retention and deletion requirements.
- Define whether pilot data may be kept, exported, or deleted at pilot close.
Need this in your enterprise security review?
Cloudryption can provide a security packet, technical walkthrough, and pilot evidence pack for your evaluation process.