Corzad Cloud: Data Processing Agreement
Corzad FZ-LLC | Version 1.1 | Effective date: 17 November 2026 | Published at https://www.corzadcloud.com/legal/dpa
This Data Processing Agreement (the "DPA") forms part of the Terms of Service (the "Terms") between Corzad FZ-LLC ("Corzad", "Processor") and the Customer named in the Terms or Order Form ("Customer", "Controller"). It applies when Corzad processes Personal Data on the Customer's behalf in providing Corzad Cloud, and it takes effect when the Customer accepts the Terms. Terms that are not defined here have the meaning given in the Terms.
1. Definitions
1.1 "Applicable Data Protection Law" means the data protection and privacy laws that apply to the processing of Customer Personal Data, which may include: Regulation (EU) 2016/679 (the "GDPR"); the GDPR as it forms part of the law of the United Kingdom and the Data Protection Act 2018 (together, the "UK GDPR"); Federal Decree-Law No. 45 of 2021 on the Protection of Personal Data of the United Arab Emirates (the "UAE PDPL"); the Personal Data Protection Law of the Kingdom of Saudi Arabia issued by Royal Decree M/19, as amended by Royal Decree M/148, and its regulations (the "Saudi PDPL"); and the California Consumer Privacy Act as amended by the California Privacy Rights Act ("CCPA"); in each case as amended or replaced.
1.2 "Customer Personal Data" means Personal Data contained in Customer Data that Corzad processes on behalf of the Customer.
1.3 "Personal Data", "Controller", "Processor", "Data Subject", "Personal Data Breach", "processing" and "supervisory authority" have the meanings given in Applicable Data Protection Law. Where CCPA applies, "service provider" and "personal information" have the CCPA meanings, and references to Controller and Personal Data include them.
1.4 "Subprocessor" means a third party that Corzad engages to process Customer Personal Data. The current list is the Subprocessor List published at https://www.corzadcloud.com/legal/sub-processors, summarised in Annex III.
1.5 "Restricted Transfer" means a transfer of Customer Personal Data that is subject to Applicable Data Protection Law and that is made to a country, territory or recipient not recognised as providing adequate protection under that law.
1.6 "EU SCCs" means the standard contractual clauses annexed to Commission Implementing Decision (EU) 2021/914 of 4 June 2021. "UK Addendum" means the International Data Transfer Addendum to the EU SCCs, version B1.0, issued by the UK Information Commissioner's Office under section 119A of the Data Protection Act 2018, in force from 21 March 2022, as revised under Section 18 of its Mandatory Clauses.
2. Roles and scope
2.1 The Customer is the Controller (or, where the Customer processes Personal Data on behalf of its own customer or group company, a Processor) and Corzad is the Processor (or sub-processor) of Customer Personal Data.
2.2 Annex I describes the subject matter, duration, nature and purpose of the processing, the types of Personal Data and the categories of Data Subjects.
2.3 The Customer is responsible for the lawfulness of its instructions and of the Customer Personal Data, for having a lawful basis for processing, and for giving Data Subjects the notices required by law.
2.4 For personal data that Corzad uses for its own purposes (for example account administration, billing, security and its website), Corzad acts as an independent Controller, as the Privacy Notice explains. This DPA does not apply to that processing.
3. Processing instructions
3.1 Corzad will process Customer Personal Data only on the Customer's documented instructions, which are the Terms, this DPA, the Customer's use and configuration of the Service, and any further written instructions the Customer gives that Corzad accepts. This includes instructions on transfers of Customer Personal Data to a third country or international organisation, unless Applicable Data Protection Law requires otherwise; in that case Corzad will tell the Customer before processing, unless the law forbids it.
3.2 Corzad will tell the Customer without undue delay if, in its opinion, an instruction infringes Applicable Data Protection Law. Corzad may suspend the relevant processing until the Customer confirms or changes the instruction.
3.3 Corzad will not sell Customer Personal Data, will not retain, use or disclose it outside the direct business relationship with the Customer or for any purpose other than the business purposes in the Terms, and will not combine it with other personal information except as the law permits. Corzad certifies that it understands and will comply with these restrictions (CCPA).
4. Confidentiality and personnel
4.1 Corzad ensures that persons it authorises to process Customer Personal Data are bound by confidentiality duties (by contract or by law).
4.2 Access is limited to staff who need it to provide, secure and support the Service.
5. Security
5.1 Corzad implements and maintains the technical and organisational measures described in Annex II, taking into account the state of the art, costs, the nature, scope, context and purposes of processing and the risks to Data Subjects (GDPR Article 32). Corzad may update the measures if the update does not reduce the overall level of protection.
5.2 The Customer is responsible for using the Service securely, including managing user access, enabling two-factor authentication or single sign-on for its workspace, and protecting its credentials.
6. Subprocessors
6.1 The Customer gives Corzad general written authorisation to engage the Subprocessors named in the Subprocessor List.
6.2 Corzad will give the Customer at least 30 days' notice of any intended addition or replacement of a Subprocessor, by e-mail to workspace administrators or by notice in the Service, and will update the Subprocessor List before the change takes effect. The Customer may object on reasonable data protection grounds within that period. If the parties cannot resolve the objection, the Customer may end the affected part of the Service by written notice and receive a refund of prepaid fees for the period after termination.
6.3 Corzad will bind each Subprocessor by a written contract that provides, in substance, the same data protection obligations as this DPA, and Corzad remains responsible to the Customer for each Subprocessor's performance.
6.4 On request, Corzad will give the Customer a copy of its Subprocessor agreements, with commercial terms and confidential information redacted.
7. Assistance
7.1 Taking into account the nature of the processing, Corzad will assist the Customer, by appropriate technical and organisational measures where possible, to respond to requests from Data Subjects to exercise their rights. If Corzad receives such a request directly, it will pass it to the Customer without undue delay and will not respond except to say that the request has been passed on, unless the Customer instructs otherwise. The Service allows the Customer to export and correct records. Where the Service does not let the Customer export everything about one person or erase one person directly, Corzad will carry out these actions on the Customer's written request within 30 days.
7.2 Corzad will give the Customer reasonable assistance with the Customer's obligations on security, breach notification, data protection impact assessments (GDPR Article 35) and prior consultation with a supervisory authority, taking into account the information available to Corzad.
8. Personal Data Breach
8.1 Corzad will notify the Customer without undue delay, and in any event within 48 hours, after becoming aware of a Personal Data Breach affecting Customer Personal Data.
8.2 The notice will, as far as known at the time, describe the nature of the breach, the categories and approximate number of Data Subjects and records concerned, the likely consequences, the measures taken or proposed, and a contact point. Corzad will provide further information as it becomes available.
8.3 Corzad will take reasonable steps to contain and investigate the breach. Corzad's notification is not an admission of fault. The Customer is responsible for deciding whether to notify authorities and Data Subjects. Corzad follows its documented incident response procedure.
9. Audit and information
9.1 Corzad will make available to the Customer the information needed to show compliance with this DPA and Article 28 of the GDPR, and will allow and contribute to audits, including inspections, conducted by the Customer or an auditor the Customer appoints and Corzad accepts (acceptance not to be unreasonably withheld).
9.2 To keep the burden reasonable: the Customer will first ask for Corzad's written answers to security questionnaires and any independent reports Corzad has available; audits will be on at least 30 days' notice, during business hours, no more than once in twelve months (unless a supervisory authority requires more or after a Personal Data Breach), will be confined to what is relevant, will be subject to confidentiality, and will not give access to other customers' data. The Customer bears its own costs and Corzad's reasonable costs.
10. International transfers
10.1 Hosting. Corzad hosts Customer Personal Data in London, United Kingdom. Corzad and its Subprocessors may access it from other countries, including the United Arab Emirates and the United States. The Customer authorises these transfers, subject to this section.
10.2 EU SCCs. To the extent that Customer Personal Data is subject to the GDPR and is the subject of a Restricted Transfer to Corzad, the EU SCCs are incorporated into this DPA by reference and apply as follows:
(a) Module Two (Transfer controller to processor) applies where the Customer is a Controller, and Module Three (Transfer processor to processor) applies where the Customer is a Processor acting on behalf of another Controller;
(b) Clause 7 (docking clause) applies;
(c) Clause 9: Option 2 (general written authorisation) applies, with the notice period in section 6.2;
(d) in Clause 11, the optional independent dispute resolution body wording does not apply;
(e) Clause 17: the law of Ireland governs; and under Clause 18 the courts of Ireland resolve disputes. For the EU SCCs, Clauses 17 and 18 apply instead of the governing law and courts that the Terms choose;
(f) Annex I.A (parties), I.B (description of transfer) and I.C (competent supervisory authority) are completed by Annex I of this DPA and by the details in the Terms or Order Form; for Annex I.C the competent supervisory authority is the authority responsible for the Customer as data exporter under Clause 13, or, if the Customer is not established in the EU and has appointed a representative, the authority of the Member State where the representative is established;
(g) Annex II is Annex II of this DPA, and Annex III is Annex III of this DPA.
10.3 UK Addendum. To the extent that Customer Personal Data is subject to the UK GDPR and is the subject of a Restricted Transfer to Corzad, the UK Addendum applies. It is incorporated by reference and completed as follows: Table 1 (Parties) as in the Terms and Annex I; Table 2 (Selected SCCs, modules and clauses) the EU SCCs as completed in section 10.2; Table 3 (Appendix information) Annexes I, II and III of this DPA; Table 4 (ending the Addendum when the Approved Addendum changes) neither Party; and Part 2: Mandatory Clauses of the Approved Addendum, being the template Addendum B.1.0 issued by the ICO and laid before Parliament in accordance with s119A of the Data Protection Act 2018 on 2 February 2022, as it is revised under Section 18 of those Mandatory Clauses. The UK Addendum follows its own law and forum: as its Mandatory Clauses provide, it is governed by the law of England and Wales and disputes under it are resolved by the courts of England and Wales. This applies to the UK Addendum only and does not change the governing law or courts that the Terms choose for the rest of this DPA.
10.4 Saudi PDPL. If the Customer is subject to the Saudi PDPL and a transfer of Customer Personal Data outside the Kingdom requires specific safeguards, the parties will, at the Customer's reasonable request, enter into the standard contractual clauses published by the Saudi Data and Artificial Intelligence Authority (SDAIA), or other mechanism that the Saudi PDPL and its regulations permit, and will complete any required form.
10.5 UAE PDPL. The parties will cooperate in good faith to put in place any mechanism that the UAE PDPL requires for transfers of Customer Personal Data.
10.6 Other laws. For any other Restricted Transfer, the parties will agree an appropriate mechanism recognised by the law that applies to the transfer.
10.7 If there is a conflict between the EU SCCs or UK Addendum and this DPA or the Terms, the EU SCCs or UK Addendum prevail on the matters that they cover.
10.8 Corzad will notify the Customer if it can no longer meet its obligations under the EU SCCs or UK Addendum, and the Customer may then suspend the transfer and end the affected processing.
11. Return and deletion
11.1 When the Service ends (that is, when the paid Subscription Term ends or the agreement is terminated under the Terms), the Customer may ask Corzad in writing, before Customer Personal Data is deleted, for an export of Customer Data, and Corzad will provide it in a common format within a reasonable time. Corzad will then delete Customer Personal Data from its live systems as section 19 of the Terms provides (30 days after the subscription ends; for a workspace whose free trial ended, 90 days after the trial ends and after a written warning), and Customer Personal Data ages out of the database restore history within 7 days after that, unless the law requires storage. On request, Corzad will confirm deletion in writing.
11.2 Corzad may keep records that the law requires it to keep, and will continue to protect them under this DPA.
12. Liability and general
12.1 The liability of each party under this DPA is subject to the limitations in section 17 of the Terms, including the higher limit that section 17.3 sets for breach of this DPA, except where the law, the EU SCCs or the UK Addendum provide otherwise. These limits do not affect the rights of data subjects under the EU SCCs, the UK Addendum or Applicable Data Protection Law.
12.2 This DPA continues for as long as Corzad processes Customer Personal Data. The governing law and jurisdiction clauses of the Terms (section 23) apply to this DPA, except as section 10 provides for the EU SCCs and the UK Addendum. Nothing in them limits the rights of data subjects or the powers of a supervisory authority.
12.3 If any part of this DPA is invalid, the rest remains in force. Corzad may update this DPA to reflect changes in law, or in the EU SCCs or UK Addendum, by notice to the Customer.
Annex I: Details of processing
A. Parties
Data exporter / Controller: the Customer named in the Terms or Order Form. Contact: the workspace administrator's contact details given at sign-up.
Data importer / Processor: Corzad FZ-LLC, VUNE3183, Compass Building - Al Hulaila, Al Hulaila Industrial Zone-FZ, Ras Al Khaimah, United Arab Emirates (free-zone licence 47038527). Contact: info@corzad.com. Corzad has not appointed a data protection officer or an EU or UK representative at the effective date; the privacy contact handles data protection questions.
B. Description of the processing and transfer
| Item | Details |
|---|---|
| Subject matter | Provision of Corzad Cloud, a field service management platform, and related support |
| Duration | The Subscription Term, plus the export and deletion periods in the Terms and section 11 |
| Nature of processing | Hosting, storing, retrieving, displaying, transmitting by e-mail on the Customer's instructions, backing up, and deleting; support access when the Customer asks for help |
| Purpose | To provide, secure and support the Service for the Customer, as set out in the Terms |
| Frequency of transfer | Continuous, for the duration of the Service |
| Retention | As set out in section 11 and in the Terms (workspace data: deleted 30 days after the subscription ends, or 90 days after the trial ends and after a written warning for a view-only trial workspace; position points recorded during a trip: deleted after 30 days; trip records: deleted 12 months after the trip; address search cache: an entry is deleted 12 months after it was saved) |
| Subprocessors | See Annex III. Transfers to Subprocessors are for hosting, storage, and e-mail delivery |
C. Categories of Data Subjects
- The Customer's employees, technicians and other staff who use the Service or are recorded in it
- The Customer's own customers and prospects (individuals and contact persons of organisations)
- Contact persons at the Customer's customers, sites and suppliers
- Persons who receive links or e-mails from the Service on the Customer's instruction (for example quote approval or survey links)
D. Categories of Personal Data
- Identity and contact: name, job title, e-mail address, phone number, language
- User account data: login e-mail, password (stored as a one-way hash), two-factor secret (stored encrypted) and recovery codes (stored as hashes), role and permissions, sign-in times, IP address and browser details
- Customer and site data: customer and contact names, addresses, site addresses and map coordinates, access notes, equipment records and serial numbers
- Work data: jobs, quotes, orders, invoices, payments, contracts, checklists, reports, notes and attached files
- Technician data: skills, certifications, working hours, time entries, absence records (including the absence type), home-base address or coordinates, location recorded when checking in to a job or signing off a report, location points and trip records while a trip is active (the app records location only while a trip is active and the app is open on the screen), vehicle and stock records
- Signatures (image) and photos attached to jobs and reports
- Customer feedback and survey answers
- E-mail records: recipient addresses, subject and content of messages sent from the Service
- Activity and audit records: who made which change and when
- Free-text content that users type, which may include any other personal data the Customer chooses to enter
E. Special categories and sensitive data
The Service is not designed to process special categories of personal data (GDPR Article 9) or criminal-offence data. The absence type (for example "sick") and free-text fields (notes, job and incident descriptions) may reveal health information about technicians or others. The Customer will not enter special-category data unless it has a lawful basis and a need for it, and will keep it to the minimum. Safety incident records may contain information about injuries. Geolocation of technicians is recorded when they check in to a job or sign off a report, and while a trip is active; the Customer is responsible for informing its technicians and for having a lawful basis.
Annex II: Technical and organisational measures
Corzad applies the following measures.
- Hosting and location. Database hosted by Neon on Amazon Web Services in London (eu-west-2) only, with no replicas in other regions; application servers hosted by Vercel in London.
- Encryption. In transit: the database accepts TLS connections only and the application requires an encrypted (SSL) connection to it. At rest: the database provider states in its public documentation that stored data is encrypted at rest. Uploaded files are stored in the same database. Two-factor secrets and integration credentials are encrypted by the application before storage.
- Tenant separation. Each customer's data is held in its own workspace. Row-level security is enabled on tenant data tables, and the application connects with a database role that is not the owner of those tables.
- Authentication. Passwords stored only as salted one-way hashes; optional two-factor authentication using time-based codes, with single-use recovery codes stored as hashes; single sign-on using SAML or OpenID Connect; sign-in lock-out after repeated failures and rate limits; session revocation when a password changes or is reset; sessions expire after 12 hours.
- Access control. Role-based access within each workspace (administrator, technician); API keys stored only as hashes and limited by scope.
- File storage. Uploaded files are stored in our Neon Postgres database in London. We do not use a separate file store (such as Vercel Blob or S3); if that changes, we will update the Subprocessor List first. Files are served only to signed-in users with permission, or by time-limited links.
- Logging and monitoring. Activity and audit records inside each workspace; application logs that omit secrets, e-mail addresses, phone numbers, IP addresses and signatures.
- Application security. Security headers and content security policy; input validation; payment webhook signature checks.
- Backups and recovery. The database can be restored to any point in the last 7 days (point-in-time restore provided by the database provider). A restore applies to the whole database and not to a single customer's data. Nothing is kept beyond 7 days. Uploaded files are part of the database and are covered by the same restore window.
- Incident response. A documented procedure for detecting, assessing, containing and notifying breaches.
- Subprocessor management. Subprocessors are bound by written terms, as section 6.3 provides.
- Deletion. Deletion of workspaces as section 11 provides.
Annex III: Authorised Subprocessors
The authorised Subprocessors are listed in the Subprocessor List published at https://www.corzadcloud.com/legal/sub-processors. That list is part of this DPA and is the current list: if the summary below differs from it, the published list prevails. Changes are made as section 6.2 provides.
| Subprocessor | Service | Location of processing |
|---|---|---|
| Vercel Inc. | Application hosting and delivery, scheduled jobs and logs | London, United Kingdom (application servers); United States for the provider's own operations |
| Neon, Inc. | Database hosting (PostgreSQL), including uploaded files stored in the database | London, United Kingdom (AWS eu-west-2) |
| Titan Solution Ltd SEZC (Cayman Islands) | E-mail delivery (sending service e-mails, including mail from support@corzad.com) | United States (Amazon Web Services) |
| OpenStreetMap tile servers, operated by the OpenStreetMap Foundation | Map pictures for the work-order map, requested by the Administrator's browser (IP address, browser details and the map area on screen; no names or position points) | Global network of cache servers; other personal data in the United Kingdom and the Netherlands, backups in the European Union (as the foundation states) |
| OpenStreetMap Foundation (address search, Nominatim) | Finding map coordinates for a site address, sent by Corzad's servers (the address text) | As the foundation states: United Kingdom and the Netherlands, backups in the European Union |
No language model provider is engaged as a Subprocessor. Ollie, our in-app assistant, is coming soon and is not switched on in any workspace, so no provider receives Customer Personal Data for it. Before Ollie is switched on, we will add its model provider to the Subprocessor List.
Subprocessors that process data only on the Customer's instruction and choice (for example accounting connections to Xero, QuickBooks or Sage, or a webhook address) are not Corzad's Subprocessors.