Corzad Cloud: Privacy Notice
Corzad FZ-LLC | Version 1.1 | Effective date: 17 November 2026 | Published at https://www.corzadcloud.com/privacy
This notice explains how Corzad FZ-LLC ("Corzad", "we", "us") collects and uses personal data when you visit https://www.corzadcloud.com, ask us about Corzad Cloud, sign up, or use Corzad Cloud, and what rights you have. It is written for readers anywhere in the world. Where the law of your country gives you extra rights, section 11 explains them.
1. Who we are and how to contact us
Corzad FZ-LLC is a company licensed in the United Arab Emirates (free-zone licence number 47038527). Registered address: VUNE3183, Compass Building - Al Hulaila, Al Hulaila Industrial Zone-FZ, Ras Al Khaimah, United Arab Emirates.
Privacy contact: info@corzad.com. Use it for any question about this notice and to use your rights.
We have not appointed a data protection officer. We have not appointed representatives under Article 27 of the UK GDPR or the GDPR. If we appoint either, we will name them here.
2. Two roles: controller and processor
Corzad Cloud is a tool that businesses use to run field service work. This means we act in two different roles.
Corzad as controller. We decide why and how we use personal data about: visitors to our website; people who ask for a demo or contact us; people who sign up for a trial or subscribe; the administrators and users of customer workspaces (login, security, billing and support data); and people we deal with in running our business. This notice mainly covers these situations.
Corzad as processor. When a business customer ("Customer") puts data about its own staff, technicians, customers, contacts and sites into Corzad Cloud ("Customer Data"), the Customer decides why and how that data is used and Corzad is its processor. We use that data only on the Customer's instructions, under our Data Processing Agreement. If you are a customer or contact of one of our Customers, or a technician employed by one of them, please contact that organisation first about your data. We will help the Customer to respond to your request. Corzad does not use Customer Data for its own purposes.
3. The personal data we use
| Group | What we hold | Where it comes from |
|---|---|---|
| Visitors and enquiries | Name, work e-mail, company, country, team size and message you send in the demo or contact form; the pages and technical data your browser sends when it connects (such as IP address and browser type) | You; your browser |
| Sign-up and account | Name, work e-mail, company name, country, currency, time zone, language, password (stored only as a one-way hash), sign-up request and the IP address it came from, which Plan you chose | You |
| Sign-in and security | E-mail used to sign in, method (password, single sign-on, link), result (success, failure, locked), IP address, browser and device details, time of each sign-in attempt; two-factor settings (the secret is stored encrypted and recovery codes are stored as hashes); password reset requests; session records | You; your device; our systems |
| Billing | Billing name and address, business tax number, quotes and Order Forms, invoice numbers, bank-transfer payment references and payment status. We do not collect card details | You; Corzad |
| Support and feedback | Messages you send, and information needed to solve the problem | You |
| Communications | E-mail messages sent from the Service (recipient, subject and content) are logged so that you and we can see what was sent | The Service |
| Use of the Service | Actions in the workspace recorded in activity and audit logs (who did what and when), and technical logs with limited identifiers | Our systems |
Data that Customers put into Corzad Cloud, for which Corzad is a processor, can include: names, job titles, e-mail addresses and phone numbers of the Customer's own customers and contacts; site addresses and map coordinates; equipment records; job, quote, order and invoice records; files, photos and signatures attached to jobs and reports; technicians' names, contact details, skills, certifications, time entries, absences, home-base location, the location recorded when a technician checks in to a job; the position points recorded while a trip the technician started to a job is active, including when the screen is off or the app is in the background (latitude, longitude, accuracy and time), the record of each trip, and the technician's consent to share location; and customer feedback and survey answers. See the Data Processing Agreement, Annex I.
We do not ask you to provide special categories of personal data (for example data about health, religion or trade-union membership). The Service records the type of a technician's absence (for example leave, training or sick leave). Customers should not type health details into free-text fields.
4. Why we use personal data, and our legal bases
| Purpose | Examples | Legal basis (GDPR and UK GDPR) |
|---|---|---|
| Provide the Service and our contract with you | Create and manage accounts and workspaces, authenticate users, run the Service, send transactional e-mails (verification, password reset, notices), process payments and issue invoices | Performance of a contract (Article 6(1)(b)), or steps you ask us to take before a contract |
| Keep the Service secure | Sign-in monitoring, lock-out after repeated failures, rate limits, fraud and abuse prevention, audit logs, incident response | Our legitimate interests in protecting the Service and our customers (Article 6(1)(f)); legal obligation where it applies |
| Support | Answer questions and fix problems | Contract; legitimate interests |
| Respond to enquiries and demos | Reply to the demo form and follow up once | Legitimate interests in responding to business enquiries; your consent where the law requires it |
| Keep business and tax records | Invoices, accounts, audits, sanctions and export control checks | Legal obligation (Article 6(1)(c)); legitimate interests |
| Improve and develop the Service | Fix errors and measure capacity using technical logs; we do not use analytics or advertising trackers | Legitimate interests |
| Marketing messages | Product news to business contacts, if you receive it | Legitimate interests or your consent, depending on your country; you can opt out at any time |
| Legal claims and compliance | Enforce our terms, respond to authorities | Legal obligation; legitimate interests |
Under the laws of the United Arab Emirates and the Kingdom of Saudi Arabia, we rely on the corresponding grounds in those laws, such as your consent, performance of a contract, a legal obligation, or our legitimate interests where the law permits.
We do not make decisions about you that have a legal or similarly significant effect by purely automated means. Ollie, our in-app assistant, is coming soon (see section 8).
5. Who we share personal data with
- Our subprocessors and service providers, who process data for us under data processing terms: Vercel (application hosting and delivery, and scheduled jobs), Neon (database hosting, including uploaded files) and Titan (e-mail delivery). The current list, with the data each one receives and where it is processed, is in our Subprocessor List at https://www.corzadcloud.com/legal/sub-processors. We also use GitHub to store our source code; no Customer Data is stored there.
- Map services. The work-order map shows map pictures from the OpenStreetMap tile servers, operated by the OpenStreetMap Foundation. When an administrator opens the map, the administrator's browser requests the pictures, so the OpenStreetMap Foundation receives the administrator's IP address, browser and device details, the address of our web application, the time and the map area on the screen. It does not receive names or position points, but at high zoom the map area can show where a technician is. When an administrator selects "Find on map" for a site, our servers send the address text to the foundation's address search (Nominatim), which receives that address text and the address of our server; a site address can identify a person. The foundation decides how it uses this data under its own privacy policy (https://osmfoundation.org/wiki/Privacy_Policy). We also keep the answers (address text, coordinates and a place name) in a cache. A link to Google Maps opens only when a user selects it.
- Services you ask us to connect. If a workspace administrator switches on an accounting connection (Xero, QuickBooks or Sage) or a webhook, we send data to that service at the administrator's instruction.
- Professional advisers, auditors and insurers, under confidentiality duties.
- Authorities and courts, when the law requires, and to protect rights, safety and security.
- A buyer or successor in a merger, acquisition or sale of our business, who must continue to protect your data in line with this notice.
We do not sell personal data. We do not "share" personal data for cross-context behavioural advertising.
6. International transfers
Corzad is based in the United Arab Emirates. Customer Data and account data are hosted in London, United Kingdom: the database is on Neon in the Amazon Web Services region eu-west-2, and application servers run on Vercel in London. Uploaded files (documents, photos and signatures) 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. Vercel states in its data processing terms that its primary processing facilities are in the United States and that it may process data wherever it or its subprocessors operate. Our team in the United Arab Emirates and other countries may access data from there, and some subprocessors operate in other countries, including the United States. Map pictures come from a global network of servers chosen by the OpenStreetMap Foundation's content delivery network at the time of the request, so those requests can be served from outside the United Kingdom, the European Economic Area and the United Arab Emirates. We have no contract with the foundation for these requests; its own privacy policy applies.
When personal data from the European Economic Area, the United Kingdom, Saudi Arabia or another place with transfer rules is transferred to a country that does not have an adequacy decision or an equivalent recognition, we use a lawful transfer mechanism, such as:
- the standard contractual clauses adopted by the European Commission (Implementing Decision (EU) 2021/914 of 4 June 2021) and the UK International Data Transfer Addendum issued by the Information Commissioner's Office (version B1.0), which are incorporated into our Data Processing Agreement;
- for subprocessors that are certified, the EU-US Data Privacy Framework and its UK and Swiss extensions (Vercel states that it is certified); and
- for the Kingdom of Saudi Arabia, the transfer rules of the Saudi Personal Data Protection Law and the standard contractual clauses published by SDAIA where they apply.
You can ask us for a copy of the safeguards (section 12).
7. How long we keep personal data
The table shows how long we keep each kind of data.
| Data | How long we keep it |
|---|---|
| Workspace data (Customer Data) | While the subscription is active |
| Workspace after a free trial ends without a paid subscription | The workspace is view-only: its data can be viewed but not changed. Its data is kept for 90 days after the trial ends, and you can ask us in writing for an export of the data in a common format during that period. After that we will delete it, after a written warning. You can ask us to delete it sooner |
| Workspace after the end of a paid subscription term | If you do not renew, you keep access until the end of the paid term. From the end date the workspace is view-only, so the data can be viewed but not changed. You can ask us in writing for an export of the data in a common format before it is deleted. After a written warning, we will delete the workspace and its Customer Data, no earlier than 30 days after the end date |
| Earlier states of the database that we hold for point-in-time restore | 7 days, then they age out. Deleted data is gone from them within 7 days |
| Sign-up requests that were never completed | 7 days |
| Password reset tokens | Deleted 30 days after they expire |
| Sessions | Up to 12 hours; revoked when the password changes |
| Sign-in records | 12 months |
| Demo and enquiry records | 12 months after the last contact |
| Telegram support chats with @Corzad_app (messages, ticket number, Telegram name and chat id) and their transcripts | Telegram also holds the chat under its own terms. We keep a copy in our support records for up to 50 months, then delete it |
| Trip position points | 30 days, then deleted. Earlier deletion is available on request (see section 9) |
| Trip records (start, end, destination, distance, reason the trip ended) | 12 months after the trip |
| Consent records for location sharing | Kept with the workspace, and deleted with the technician or the workspace |
| Check-in and sign-off positions | With the job and its report, for as long as the workspace exists |
| Address-search cache (address text, coordinates and place name, shared by all workspaces) | An entry is deleted 12 months after it was saved. The cache is not tied to a workspace |
| Activity and audit logs | For as long as the workspace exists |
| Invoices and tax records | For the period the law requires |
A legal hold, an investigation, a dispute or a legal duty can require us to keep data longer. We then keep only what is needed and protect it.
8. Ollie, our in-app assistant (coming soon)
Ollie is coming soon. It is not available yet and it is not switched on in any workspace, so no language model provider receives data from Corzad Cloud. Before we switch it on, we will publish its full disclosure, add its provider to our Subprocessor List, and update this notice.
9. Technician location on trips
This section applies where a company uses the Corzad Field app for Android to follow a technician's trip to a job. The company is the controller of this data and Corzad is its processor; the company or business that engages the technician gives the technician the full notice for their country.
- What is collected. While a trip is active, the app records the phone's location points with their accuracy and time. If the technician allows it, the app also records a position once when they check in to a job.
- When. Only during a trip to a job that the technician starts by tapping On my way while the app is open. Once a trip has started, recording continues while it is active, including when the screen is off or the technician is using another app. The phone shows a notification for as long as recording is on, and the technician can pause recording from that notification or with Pause sharing in the app. Recording stops when the technician taps Arrived, check in, or checks in at the job by QR code or PIN. Signing out also stops recording on the phone. A trip closes on its own after 2 hours without a location update or after 6 hours in total. Apart from the single check-in position, nothing is recorded while the technician works on the job or outside a trip.
- Consent. Before the first trip, the app explains this and asks the technician to agree, before Android asks for location permission. Without agreement the app does not start a trip or record location. The technician can pause sharing at any time. Job work and check-in by QR code or PIN still work.
- Who can see it. Only the company's administrators who can assign jobs, on the map of the job the trip belongs to. No customer-facing view exists.
- How long. Trip location points are kept for 30 days and then deleted. You can ask for earlier deletion from your company's administrators or by contacting the privacy contact in section 1. A short record of each trip (times, distance, reason it ended) is deleted 12 months after the trip. The technician's answer stays in the company's account for as long as the workspace exists. A check-in position stays with the job record.
- Maps. Administrators see trips on a map built with OpenStreetMap pictures (see section 5).
10. Security
We protect personal data with measures that include encrypted connections to our database, encryption of stored data (our database provider states in its public documentation that stored data is encrypted at rest), encrypted connections between your browser and the Service, separation of each workspace's data, hashed passwords, optional two-factor authentication and single sign-on, sign-in lock-out and rate limits, access controls for our staff, and logging. Annex II of the Data Processing Agreement lists our measures. No system is completely secure. If a personal data breach affects you, we will tell you or the relevant Customer as the law requires (see our Security Incident and Breach Notification Procedure).
11. Your rights
11.1 If you are in the European Economic Area or the United Kingdom (GDPR and UK GDPR)
You have the right to: be informed; access your data; have it corrected; have it erased; restrict its use; object to uses based on legitimate interests (and to direct marketing at any time); receive your data in a portable format where the processing is based on contract or consent and is automated; withdraw consent at any time; and not be subject to certain automated decisions. You may complain to your supervisory authority, for example the Information Commissioner's Office in the United Kingdom, or the authority in the EEA country where you live or work.
11.2 If you are in the United Arab Emirates (Federal Decree-Law No. 45 of 2021 on the Protection of Personal Data)
The law gives individuals rights that include access to information about the processing of their data, requesting correction or erasure, restricting or stopping processing, objecting to certain processing, and data portability, subject to the conditions and exceptions in the law. You may also complain to the UAE Data Office.
11.3 If you are in the Kingdom of Saudi Arabia (Personal Data Protection Law, Royal Decree M/19, as amended by Royal Decree M/148)
The law gives individuals rights that include being informed about the collection and purpose of processing, access to their personal data, obtaining a copy, requesting correction or completion, and requesting destruction of data that is no longer needed, subject to the conditions in the law and its regulations. The competent authority is the Saudi Data and Artificial Intelligence Authority (SDAIA).
11.4 If you are in California, United States (CCPA as amended by the CPRA)
If the California Consumer Privacy Act as amended by the California Privacy Rights Act applies to us, you have the right to know what personal information we collect, use, disclose and keep; to request deletion; to correct inaccurate information; to opt out of the sale or sharing of personal information (we do not sell or share personal information); to limit the use of sensitive personal information; and not to be treated unfairly for using your rights. In the last 12 months we collected the categories of information listed in section 3 for the business purposes in section 4, and disclosed them to the service providers in section 5. For Customer Data, we act as a service provider to our Customers.
11.5 Everyone else
We will respect the rights you have under the law where you live. Contact us at the privacy contact in section 1.
11.6 How to use your rights
Send your request to the privacy contact in section 1. We may ask you to prove your identity. We will answer within the time the law sets (usually one month under GDPR and UK GDPR, which may be extended where the law permits). If your data is in a Customer's workspace, we will pass the request to the Customer or tell you to contact them. There is usually no fee. We may refuse a request that is manifestly unfounded or excessive, or where the law allows. There is no self-service tool for these requests at present: we handle them by e-mail.
12. Safeguards and copies
If you would like a copy of the transfer safeguards we use, or more information about the subprocessors we use, contact us at the privacy contact in section 1.
13. Cookies and similar technologies
We use only essential and functional cookies and browser storage, to sign you in, remember your workspace and language, and remember display settings. We do not use advertising or analytics cookies. Our Cookie Notice has the details.
14. Children
Corzad Cloud is for business use and is not directed at children. We do not knowingly collect personal data from children under 16. If you think a child has given us personal data, contact us and we will delete it.
15. Changes to this notice
We may update this notice. We will post the new version with its effective date and, for material changes, tell workspace administrators by e-mail or in the Service.
16. Contact and complaints
Contact us first at the privacy contact in section 1 and we will try to resolve your concern. You also have the right to complain to a supervisory authority as described in section 11.