Data processing agreement
This agreement is made in Arabic. This English text is a translation; where the two differ, the Arabic text governs.
Version 1.0 — 2026-10-09
Legal documents
- Ghaym: AlGhayma Al Rasiya For Software Development LLC, a limited liability company registered in Jordan, based in Amman.
- The Customer: the person or organisation that holds a Ghaym account and puts personal data on the Service.
This agreement is part of Ghaym's Terms of Service. It applies whenever the Customer processes personal data on the Service, whether or not it is signed. A signed copy is available on request at [email protected].
Words not defined here have the meaning given in Jordan's Personal Data Protection Law No. 24 of 2023 (the "Law"). "Personal Data" means the personal data that Ghaym processes for the Customer under this agreement. The "Service" has the meaning given in the Terms of Service.
| Data | Ghaym's role |
|---|---|
| Everything the Customer puts on the Service: its applications, its databases, and its users' personal data | Processor. The Customer decides what is collected and why; Ghaym runs the infrastructure on the Customer's instructions |
| The Customer's own account data: names, email addresses, phone numbers and billing details of the Customer's staff | Controller. Ghaym decides these purposes and means itself, to run the account and meet its own legal duties |
This agreement covers the first row. Ghaym's Privacy Policy covers the second.
Ghaym processes Personal Data only for the purpose it was collected for, so it is exempt from the licences of Article 24(A)(1) of the Law under Article 24(A)(2).
Ghaym processes Personal Data only on the Customer's instructions. Those instructions are this agreement, Schedule 1, and the Customer's own use of the Service's features. Ghaym does not go beyond the purpose and duration the Customer sets (Article 12(B)).
If Ghaym believes an instruction breaks the Law, it tells the Customer and does not have to follow it until the Customer confirms it.
Personal Data is confidential (Article 13). Ghaym gives access to it only to the people who need it to run the Service, and each of them is bound to keep it confidential.
Ghaym does nothing that would let anyone else reach Personal Data or the results of processing it, except the sub-processors in Schedule 3 and where the law requires it (Article 12(D)). Where the law allows such access but does not require it, Ghaym does not allow it without the Customer's written consent.
Ghaym applies the measures in Schedule 2, and takes appropriate measures to detect and track any breach (Articles 8 and 14(E)).
The Customer authorises Ghaym to use the sub-processors named in Schedule 3. Ghaym tells the Customer at least 30 days before it adds or replaces a sub-processor. If the Customer objects for a reasonable data protection reason, it may close its account before the change and receive a refund of fees paid in advance for the period after closing.
Ghaym binds each sub-processor to protection no lower than this agreement, and remains responsible to the Customer for its work.
Ghaym helps the Customer answer data subjects who use their rights under Article 4(B) of the Law, and erase or hide data under Article 10.
If a data subject writes to Ghaym about Personal Data, Ghaym does not answer the request itself. It passes the request to the Customer and tells the data subject it has done so.
If Ghaym finds a breach affecting Personal Data, it contains it and tells the Customer within 24 hours of finding it. The notice states what is known of the cause, the data affected, the measures taken, and a contact for follow-up.
Telling the affected data subjects and the Personal Data Protection Unit is the Customer's duty under Article 20(A) of the Law. Ghaym gives the Customer the information it needs to do so.
Ghaym answers the Customer's reasonable questions about its compliance with this agreement and gives the evidence it holds, so the Customer can meet its own duties under Article 8.
When the Customer deletes data from the Service, or the account ends, Ghaym deletes the Personal Data or returns it, as the Customer chooses (Article 12(C)). Ghaym confirms the deletion in writing on request. Backup copies are not deleted one by one: they expire in the ordinary rotation of the backup set, and until then are used only to restore the Service.
Deleting a service deletes its data. Its runtime logs are kept for as long as the service exists and are deleted with it.
Personal Data is stored and processed in Jordan. The network security provider in Schedule 3 handles traffic to and from the Customer's applications in transit, on a network that runs around the world, so that traffic may be processed outside Jordan.
Before that transfer began, Ghaym verified that provider's level of protection, as Article 15(B) requires. Ghaym transfers Personal Data to no other recipient outside Jordan.
Each party registers in the registry of controllers, processors and data protection officers under Article 18(D) of the Law for the data it is responsible for. Ghaym is registered and keeps its entry up to date. Ghaym's data protection officer can be reached at [email protected].
This agreement lasts for as long as Ghaym processes Personal Data for the Customer. The laws of the Hashemite Kingdom of Jordan govern it, and the courts of Amman decide any dispute about it.
This agreement is made in Arabic, and the Arabic text is the authoritative text. This English text is a translation.
| Subject | Running the Ghaym Cloud platform: hosting, deploying and running the Customer's applications and databases |
| Duration | The life of the Customer's account, plus the time needed to delete or return the data under section 11 |
| Nature and purpose | Storage, hosting, running, transmission and deletion, only to provide the Service |
| Data subjects | Whoever the Customer's applications collect data about. The Customer decides this; Ghaym does not know it |
| Categories of data | Whatever the Customer stores. The Customer decides this; Ghaym does not know it |
| Sensitive data | Ghaym does not know whether the Customer stores sensitive data. If it does, the Customer applies the extra protection the Law requires |
| Location | The country the Customer deploys to, as Schedule 3 lists it for the hosting provider, on virtual machines that provider supplies and whose hypervisor it operates |
| # | Area | What Ghaym does |
|---|---|---|
| 1 | Physical access | Provided by the hosting provider, which supplies the virtual machines and operates the hypervisor beneath them, in its own facility |
| 2 | System access | Administrative access runs over a private network, not the public internet, and is limited to the people who operate the platform. Every administrative login raises an alert |
| 3 | Data access | Only the people who operate the platform can access Personal Data. They can search the runtime logs (row 5) |
| 4 | Encryption | Traffic is encrypted with TLS. Environment variables and secrets are encrypted at rest with AES-256-GCM |
| 5 | Logging | Platform actions are logged on Ghaym's servers. Whatever a Customer's application writes to its output is kept in its runtime log for as long as the service exists. The Customer decides what goes into it, so it can contain personal data |
| 6 | Roles | The split in section 3 |
| 7 | Availability | Backups of the Customer's databases and volumes are taken and held in the same country as the data. The Customer can also export its data at any time |
| 8 | Separation | Each Customer workload runs in its own container |
| Sub-processor | What it does | Location |
|---|---|---|
| Hosting provider | Supplies the virtual machines the Service runs on and operates the hypervisor beneath them, in its own facility | Jordan |
| Network security provider | Sits in front of the Service as a proxy, to deliver traffic and protect it from attacks. It handles traffic to and from the Customer's applications in transit | Global network |
No other party receives Personal Data.
| Ghaym | The Customer | |
|---|---|---|
| Name | AlGhayma Al Rasiya For Software Development LLC | [Customer legal name] |
| Signed by | [Ghaym signatory] | [Customer signature] |
| Date | [Date] | [Date] |