Data Processing Agreement — uMarker
Version 1.0 — effective 2026-11-10
This agreement is published in Arabic and English. The Arabic text prevails if the two differ.
1. Parties and scope
- Controller: the customer that holds the uMarker account.
- Processor: Emran Ali Abdullah Muhammed Saeed, provider of the uMarker service, Jeddah, Kingdom of Saudi Arabia, support@umarker.com (“we”).
- This agreement forms part of the Terms of Service, and applies for as long as we process personal data for the customer.
- It covers the data the customer collects through the service: widget and extension reports, project content, survey answers and tester details. It does not cover data we control (account, billing and support), which the Privacy Policy governs.
- Processing details are in Annex 1, security measures in Annex 2, and sub-processors in Annex 3.
- If the customer is itself a processor for another organisation, we are its sub-processor and this agreement applies in the same way.
2. Processing only on instructions
- We process the data only on the customer’s documented instructions, including on transfers outside the Kingdom.
- The customer’s instructions are: this agreement, the Terms of Service, the settings the customer chooses in the dashboard (such as retention, masking, capture mode, integrations and AI), and any written instructions both parties agree.
- If a law requires us to process differently, we tell the customer first, unless that law forbids it.
- We tell the customer in writing if we believe an instruction breaks the Personal Data Protection Law or another law, or goes beyond this agreement.
- Mandatory disclosure: if Saudi law requires us to disclose data, we disclose the minimum needed without consent, and notify the customer, unless the law forbids it.
- If we breach the customer’s instructions and process the data for our own purposes, we are treated as a controller for that processing and are directly liable for it.
3. The customer’s obligations
- To have lawful bases for the processing and to inform the people concerned.
- To give instructions that comply with the law.
- To turn on masking on sensitive pages, and not to use the service to collect sensitive data, as the Terms of Service require.
- To carry out impact assessments and transfer risk assessments where the law requires them. We provide the information we have for this on request.
4. Confidentiality
- Access to the data is limited to the people who run uMarker and need it to provide the service.
- Everyone authorised to access it is bound by confidentiality, in writing or by a legal duty.
- We sign in to the customer’s account only to give support the customer asks for, to investigate security or abuse, or where a law requires it. Every sign-in is recorded and shown to the customer under Account settings → Support access.
5. Security
We apply the technical and organisational measures in Annex 2, and review and update them. We may improve them, and will not lower the overall level of protection.
6. Sub-processors
- The customer gives us general authorisation to use the sub-processors listed in Annex 3.
- We bind each sub-processor to data protection obligations that give substantially the same protection as this agreement, and choose it for its ability to protect the data.
- We tell the customer 30 days before adding or replacing a sub-processor, by email to the account owner and by updating the Sub-processors page.
- The customer may object in writing to support@umarker.com within that period, on reasonable data protection grounds. We discuss the objection in good faith and look for an alternative. If we find none, the customer may end the contract before the new sub-processor starts.
- We remain responsible to the customer for our sub-processors’ performance of their obligations.
- Integrations the customer connects itself (such as Jira or Slack) are not our sub-processors. We send data to them on the customer’s instructions, under their own terms with the customer.
7. Exposure to other countries’ laws
Some of our sub-processors are subject to other countries’ laws, which may let authorities request or access data:
- India: the servers and database are hosted in India (Microsoft Azure); screenshots and uploaded files are stored in Western Europe (Cloudflare R2). The data hosted in India is subject to Indian law, including laws that give government bodies powers to access or request data.
- United States: US companies, including Microsoft, Cloudflare, Backblaze, Groq, Google and some email providers, may be subject to US laws that require them to produce data under their control, even if it is stored outside the US (such as the CLOUD Act and FISA).
- Other countries: email providers in the EU, New Zealand and Australia are subject to their laws.
Effect: a sub-processor could be required to hand over data without the customer knowing. If such a request reaches us, we tell the customer unless the law forbids it, and provide only the minimum we are compelled to. We limit what we send each sub-processor to what it needs.
8. Transfers outside the Kingdom
- We transfer data to provide the service the customer asked for, and only the minimum needed. Processing locations are in Annex 3.
- Safeguards we rely on today: each sub-processor’s data processing terms and security commitments. We have not yet signed SDAIA’s Standard Contractual Clauses with our sub-processors. We are not aware of an SDAIA decision that India or the United States offers an adequate level of protection.
- For customers in the EU and EEA: where the customer transfers personal data subject to the GDPR to us, the EU Standard Contractual Clauses (Commission Implementing Decision (EU) 2021/914) are incorporated into this agreement by reference:
- Module 2 (controller to processor) where the customer is a controller, and Module 3 (processor to processor) where the customer is a processor.
- The customer is the data exporter, and we are the data importer.
- Clause 7 (docking): does not apply.
- Clause 9: Option 2, general authorisation of sub-processors with 30 days’ prior notice.
- Clause 11: the optional wording does not apply.
- Clause 13: the competent supervisory authority as determined under Clause 13 itself.
- Clause 17: the law of Ireland. Clause 18: the courts of Ireland.
- Annex I of the Clauses = Annex 1 here; Annex II = Annex 2; Annex III = Annex 3.
- In a conflict, the EU Standard Contractual Clauses prevail for that data.
9. Assisting the customer
- Data subject requests: the dashboard lets the customer find, export and correct reports, and delete a single report. If a data subject writes to us directly, we pass the request to the customer and do not answer it ourselves unless the customer instructs us to. We help the customer answer within the legal deadline (30 days).
- Security, breaches, impact assessments and consultation with authorities: we provide the reasonable information we have.
- Requests from SDAIA or any supervisory authority about the customer’s data: we cooperate with it and with the customer.
10. Breach notification
- We notify the customer without undue delay, and in any case within 48 hours of confirming an incident affecting its personal data.
- The notice includes what we know at the time: what happened, the approximate data and people affected, the likely consequences, what we have done and what we recommend, and a contact. We add information as it becomes available.
- We take the steps needed to contain the incident and limit its effects without delay.
- Notifying SDAIA and the people affected is the customer’s responsibility as controller. We help with it.
- We keep a record of incidents and the steps we took.
11. Duration, deletion and return
- This agreement runs for the customer’s subscription and until we delete its data.
- During the subscription: the customer can export its data at any time (a JSON file) and delete what it wants.
- When the contract ends, the customer chooses:
- Return: export the data itself, or have us provide it on request, within 30 days of the end.
- Deletion: we delete it after that period, or at once if the customer deletes its account itself.
- Copies leave the backups within 30 days of deletion.
- We keep no copies except what a law requires, such as invoices (which are our data, not the customer’s). Anything kept stays subject to this agreement.
- Data the customer sent to its integrations must be deleted there.
12. Demonstrating compliance and audits
- We make available to the customer the information needed to demonstrate that we meet this agreement: a written description of the processing and security, the sub-processor list, and answers to reasonable security questionnaires. We start with this documentation.
- If it is not enough, or a supervisory authority requires it, the customer may audit, itself or through an independent auditor bound by confidentiality:
- with at least 30 days’ written notice, unless an incident or an authority requires less;
- no more than once a year, unless there has been an incident;
- during business hours, without access to other customers’ data;
- at the customer’s cost.
- Audits do not extend to our sub-processors’ facilities; instead we provide the reports or certifications they publish.
13. Records of processing
We keep a record of the processing activities we carry out for customers.
14. Liability
The limitation of liability in the Terms of Service applies to this agreement, unless a law prevents it.
15. Conflicts
In a conflict, this agreement prevails over the Terms of Service for personal data, and the EU Standard Contractual Clauses prevail where they apply.
Annex 1 — Processing details
Subject matter: providing the uMarker service to the customer: receiving, storing, showing and distributing visual feedback.
Duration: the subscription, then until deletion under section 11.
Nature and purpose:
- Receiving reports and survey answers from the widget, the extension and the API, storing them and showing them to the customer’s team.
- Sending notifications, and delivering reports to the integrations the customer connects.
- Showing announcements, surveys and the changelog to the customer’s visitors.
- If the customer turns them on: AI features on report text only, and learning from its team’s corrections within its account.
- Backups, security and support.
Categories of personal data:
- Reports: the screenshot (which may show anything on the page), marked elements, comments, page address, browser type, operating system, language, screen size and previous page.
- What the customer’s website passes: the reporter’s email, and any other details the site sends about its user.
- Technical capture (if turned on): console messages, JavaScript errors, click trail, network request log (address, status, timing and size), performance figures, and the names (not the values) of the site’s storage keys.
- Surveys: answers, and a random visitor id.
- Testers: name and email.
- The customer’s team’s comments on reports.
Sensitive data: not intended to be processed; the customer undertakes not to collect it (section 3).
Categories of data subjects: visitors to and users of the customer’s websites and apps; the customer’s testers; members of the customer’s team as far as they appear in the content.
Annex 2 — Technical and organisational measures
- Encryption in transit: HTTPS on all our sites. Requests reach our servers through Cloudflare Tunnel; the servers have no public IP address.
- Encryption at rest: backups in Backblaze B2 use encryption managed by Backblaze. Screenshots and uploaded files in Cloudflare R2 are encrypted at rest, according to Cloudflare. Azure managed disks are encrypted by default, according to Microsoft. Integration credentials are encrypted in the database.
- Network: the database is on a private address and accepts connections only from the application server.
- Administrative access: through a private network and SSH keys, not over the open internet.
- Authentication: hashed passwords; two-factor authentication available to customers on plans that include it, and mandatory for uMarker staff; sessions revoked after 90 days without use, and all of them on password reset.
- Permissions: per role and per action, with protection against raising one’s own permissions; each account’s and space’s data is isolated.
- Support access: a 30-minute session, recorded and visible to the customer.
- Audit log of sensitive events.
- Data minimisation at capture: optional masking of sensitive fields and elements; technical capture off unless the customer turns it on; no headers, cookies or request contents; values of sensitively named query parameters blanked from URLs in failed-request logs.
- AI: off by default; text only is sent, screenshots never, enforced in code; emails and phone numbers masked in the comment.
- Extension: works only on the customer’s registered websites, with matching done in the browser.
- Protection of outgoing requests to customer-supplied URLs from reaching internal addresses.
- Rate limits on sensitive and public endpoints.
- Backups: daily, kept 30 days, with restore tested.
- Retention: automatic deletion under the customer’s settings and plan limits.
Annex 3 — Sub-processors
The current list is on the Sub-processors page, which forms part of this agreement.