Data Residency & GCC Hosting Policy
Data Residency and GCC Hosting for HYP ERP Customers
This policy explains how HYP ERP approaches data residency in the GCC: where your ERP data is stored and processed is reviewed with you and confirmed in your contract and technical documentation.
Data residency FAQs
Does HYP ERP guarantee GCC-only hosting?
No. HYP ERP does not apply a GCC-only hosting commitment to every customer. A residency commitment exists only when it is set out in the deployment documentation and service agreement for your environment, so state any GCC requirement before contracting.
Are backup locations part of data residency?
Yes. Backup and recovery locations can change where HYP ERP data is stored or processed, so they are reviewed and documented alongside primary hosting, together with retention and disaster recovery responsibilities.
Do integrations affect where ERP data is processed?
Yes. Integrations with payment services, delivery platforms and other third parties can move data outside the HYP ERP environment. Each connection belongs in your data processing assessment before it goes live.
Who identifies the legal requirements for data residency?
The customer identifies the laws, regulator directions and contractual restrictions that apply to its sector and jurisdictions. HYP ERP helps identify relevant requirements and evaluates the hosting arrangement against them with the customer's team.
Related policies and pages
Raise your hosting requirements before you contract
Share your residency and sector requirements with HYP ERP so they can be reviewed and documented for your environment.