Privacy Policy — uMarker
Version 1.3 — effective 2026-11-15
This policy is published in Arabic and English. The Arabic text prevails if the two differ.
1. Who we are and how to reach us
uMarker is a service for businesses that collects visual feedback on websites and web apps. It is provided by:
- Emran Ali Abdullah Muhammed Saeed (عمران علي عبدالله محمد سعيد), an individual, Jeddah, Kingdom of Saudi Arabia.
- Commercial registration or freelance document: No commercial registration or freelance document has been issued yet. This section will be updated with the number once issued.
- Email for everything, including privacy and rights requests: support@umarker.com
- Privacy contact: Emran Ali Abdullah Muhammed Saeed, at the same address. We have not appointed a data protection officer (DPO).
- We have not appointed an EU representative, because we do not direct our service at individuals in the EU.
This policy covers umarker.com, docs.umarker.com, app.umarker.com (the dashboard), api.umarker.com and the uMarker extension for Chrome.
2. Our role: controller for some data, processor for other data
We are the controller of the data we collect to run our relationship with you: account holders and their team members, billing, support conversations, and visitors to umarker.com and docs.umarker.com.
We are the processor of the data our customers collect through the service: what visitors to customers’ websites send through the widget, what customers’ testers send through the extension, and project content (reports, screenshots, comments, survey answers). Here the customer is the controller. The customer decides to collect this data, chooses its legal basis and informs the people concerned. We process it on the customer’s instructions and under the Data Processing Agreement. See section 15.
3. The data we collect
3.1 Account and team
- At sign-up (required): the company or account name, your name, your email and a password. Without them we cannot create an account.
- Passwords are stored hashed. We cannot read them.
- Optional: profile picture, language, theme and notification preferences, and two-factor authentication. If you leave them out, the service uses its defaults.
- Acceptance record: when you accepted the Terms and this policy, and a link to the version you accepted.
- Invited members: the invitee’s email and the role chosen by the person who invited them (see section 14).
- Sign-in devices: for each session we keep the IP address and browser type. They are listed in your profile so you can end any session.
3.2 Billing
- Plan and billing period, payment requests, the transfer reference, the bank-transfer receipt you upload (which may show your name or bank account details), and invoices.
- The buyer name and address you enter in account settings, which are printed on the invoice.
- Required to pay: the plan and the payment method. Optional: the reference, a note and the receipt. Without proof of transfer, approval of the payment may be delayed or impossible.
- We do not collect card numbers and we never hold your bank login.
3.3 Support
- Support conversations in the dashboard, the images you attach, and the emails you send to support@umarker.com.
3.4 Security and operations
- An audit log of sensitive events in your account: sign-ins, role or plan changes, deletions and support access.
- A log of emails sent: recipient address, subject and time.
- Technical error records, which may include an account or user id and the request path.
- Server logs, which include IP addresses.
3.5 Visitors to umarker.com and docs.umarker.com
- Google Analytics, only with your consent: on these two sites only, and only after you accept the “Analytics” category in the consent banner, we load Google Analytics from Google. It sets two first-party cookies (
_gaand_ga_ZWDPW9E0E1, 2 years by default per Google’s documentation) and collects: the pages you visit, the page you came from, your approximate location derived from your IP address, your device type, browser, operating system and language, and on-page interactions (such as scrolling, clicks on outbound links, site search and file downloads). We use it to learn which pages help visitors and to improve them. We have turned off every Google data-sharing setting, we do not link it to advertising, and we send it no name or email. It does not run in the dashboard, the operator console, the widget or the browser extension. You withdraw consent from “Cookie settings” at the bottom of any page. - Microsoft Clarity, only with your consent: on these two sites only, under the same consent to the “Analytics” category, we load Microsoft Clarity. It records how you interact with the page (clicks, scrolling, mouse movement, the page layout and the pages you visit) and shows it to us as heatmaps and session recordings, and collects your approximate location derived from your IP address and your device type and browser. We hide all page text and everything you type into any field, so it is not sent to Microsoft. It sets two first-party cookies (
_clck, 1 year, and_clsk, 1 day) and one session-storage item (_cltk). We use it to see where visitors get stuck and to improve the pages. Microsoft acts as an independent controller for it, and uses the data for its own purposes under the Microsoft Privacy Statement, which may include advertising; we always tell it that we do not allow advertising storage, but we do not control its use. It does not run in the dashboard, the operator console, the widget, the browser extension or on the 404 page. The details, including Microsoft’s cookies on its own domains that we cannot delete, are in the Cookie Policy. - We use no advertising tools and load no third-party fonts. The sign-in, sign-up and password-recovery pages load Cloudflare Turnstile, a check that the visitor is not a bot. It is a necessary security measure, not tracking or advertising. On the marketing site and the docs site we also count visits with Cloudflare Web Analytics: no cookies, nothing stored in your browser, no cross-site tracking.
- Account requests: when you fill in the “Request your account” form we keep what you type in it (name, work email, company, your website, and team size, use and how you heard about us if you give them), the page language and the page you sent it from, and the IP address it came from to prevent abuse. We use them to answer your request and, if we approve it, to send you a sign-up link.
- Your browser stores your light/dark theme choice and your choice in the consent banner (see the Cookie Policy).
- Requests pass through Cloudflare’s network and our servers, so IP addresses appear in their technical logs.
3.6 Data we process for our customers (we are the processor)
Described in full in section 15 and in the Data Processing Agreement.
We do not sell personal data and we do not use it for advertising.
4. Why we use data, and on what legal basis
| Purpose | Data | Basis under the Saudi PDPL | Basis under the GDPR (where it applies) |
|---|---|---|---|
| Creating the account, running the service, signing in | Account and team | Performing an agreement you are party to (Art 6) | Contract (Art 6(1)(b)) |
| Service emails: email verification, invitations, password reset, the notifications you choose | Name, email, notification content | Performing the agreement | Contract |
| Billing, approving payments, issuing invoices | Billing | Performing the agreement | Contract |
| Keeping payment records and invoices | Invoices and payment records | Obligation under another law (Art 6) | Legal obligation (Art 6(1)(c)) |
| Support and answering your questions | Support | Performing the agreement | Contract |
| Protecting the service, preventing abuse and fraud, audit log, device list | Security and operations | Legitimate interest (Art 6; IR Art 16): security of the service and accounts | Legitimate interests (Art 6(1)(f)) |
| Fixing faults and keeping the service reliable | Error records and server logs | Legitimate interest: a service that works correctly | Legitimate interests |
| Answering an account request and sending the sign-up link | Account-request data in section 3.5 | Steps you asked for before an agreement (Art 6) | Pre-contract steps at your request (Art 6(1)(b)) |
| Inviting a colleague to an account | Invitee’s email and role | Legitimate interest of the inviting account, then the agreement once accepted | Legitimate interests, then contract |
| AI features (section 5) | Report text and support conversation text | Explicit consent of the account admin | Consent (Art 6(1)(a)) |
| Measuring use of umarker.com and docs.umarker.com with Google Analytics | The visit data in section 3.5 | Your consent in the consent banner | Consent (Art 6(1)(a)) |
| Heatmaps and text-masked session recordings of umarker.com and docs.umarker.com with Microsoft Clarity | The interaction data in section 3.5 | Your consent in the consent banner | Consent (Art 6(1)(a)) |
| Marketing emails (we send none today) | Prior consent only | Consent | |
| Defending our rights or answering a lawful request | Only what is needed | Legal obligation or legitimate interest | Legal obligation or legitimate interests |
Our legitimate interest in security and fixing faults involves no sensitive data and stays within what you would expect from a service like this. You may object to it (section 9).
We will not use your data for a new purpose that is inconsistent with these purposes without telling you first.
5. AI features
- Off by default. They run only if an account admin turns them on and gives explicit consent. The admin can withdraw consent at any time in account settings.
- What is sent: report text only: the reporter’s comment, the page address, and console messages if any. Email addresses and phone numbers in the comment are masked before sending. Support conversation text may also be sent, to suggest replies to our support team.
- What is never sent: screenshots, recordings, the reporter’s email, and the data a customer’s page passes about its users. This limit is built into the service’s code.
- Providers today: Groq and Google Gemini (both in the United States); we use the paid Gemini API, under which Google does not use the text to train its models. The sub-processor list names every provider we use. We tell you 30 days before adding a new one.
- We use only provider plans whose terms say they do not train their models on what we send.
- Learning from your team’s corrections: when your team corrects a suggestion, we keep a short excerpt (up to 200 characters) and the decision, inside your account and space only, to improve later suggestions. It is never used for any other account. You can turn it off and delete what is kept on the AI page.
- Withdrawing consent stops sending and deletes stored suggestions and lessons.
6. Who receives data
- Sub-processors: companies that host the service, send email or provide AI features. They process data for us only. The full list, with country and transfer basis, is on the Sub-processors page.
- Integrations a customer connects (such as Jira, GitHub, Linear, Slack, Microsoft Teams, Telegram and webhooks): we send reports to them at the customer’s request. They process them under their own terms with the customer, and are not our sub-processors.
- Microsoft (Clarity): interaction data about visitors to umarker.com and docs.umarker.com who accepted analytics. Microsoft receives it as an independent controller and uses it for its own purposes, including advertising (section 3.5).
- Public authorities: only when a law requires it, and only the minimum needed.
7. Transfers outside the Kingdom
Data is processed and stored outside Saudi Arabia:
- India: the service’s servers and database are on Microsoft Azure (Central India region).
- Western Europe: screenshots and uploaded files are stored in Cloudflare R2.
- United States: backups (Backblaze B2), AI features if turned on (Groq and Google Gemini), some email providers, and data about visitors to umarker.com and docs.umarker.com who accepted analytics (Google Analytics: the United States and other countries, per Google; Microsoft Clarity: the Microsoft Azure cloud in the United States and other countries where Microsoft operates).
- Other countries: Cloudflare’s global network, and email providers in the EU, New Zealand and Australia, as the Sub-processors page shows.
Basis: we transfer data to perform our agreement with you and to provide the service you asked for, and send each provider only what it needs.
Safeguards we rely on today: each provider’s published data processing terms and security commitments. We have not yet signed SDAIA’s Standard Contractual Clauses with these providers. We are not aware of an SDAIA decision that India or the United States offers an adequate level of protection.
The laws of those countries may let their authorities request data. The Data Processing Agreement explains this.
8. How long we keep data
| Data | Period |
|---|---|
| Account, team and settings | While the account exists |
| Reports and their media | While the account exists, or per the retention setting an account admin chooses (7 to 3,650 days, or unlimited) on plans that include it; then deleted automatically with their media |
| Screenshots and files | May be deleted before the report under your plan’s media window; the image is deleted and the report kept |
| Sign-in sessions | Revoked after 90 days without use, on sign-out, and all of them when you reset your password |
| In-app notifications | Read ones after 30 days, unread ones after 90 days |
| Audit log | Compliance and security events for one year, other activity for 30 days |
| Log of emails sent | Delivered messages 90 days, failed ones one year |
| Spent, accepted or cancelled invitations | Deleted after 60 days |
| Account requests that never became an account | One year from sending, then deleted |
| Support conversations and error records | While the account exists |
| Server logs | Rotated by size and overwritten automatically; not kept as an archive |
| Backups | 30 days, then deleted |
| Google Analytics data about visitors to the two sites | Per the data-retention setting of our Google Analytics property (Google’s default: 2 months for detailed data); the _ga and _ga_ZWDPW9E0E1 cookies last 2 years unless you withdraw consent or clear them |
| Microsoft Clarity data about visitors to the two sites | Session recordings 30 days; click and heatmap data, and labelled or favourite sessions, 9 months, then Microsoft deletes them; the _clck cookie lasts 1 year and _clsk 1 day unless you withdraw consent or clear them |
| Invoices and payment records | As required by applicable Saudi law, also after the account is deleted |
When an account is deleted, its data, reports and media are erased at once, and their copies leave the backups within 30 days. An issued invoice (buyer name and address, amount) is kept because the law requires it. Anything already sent to an integration the customer connected (such as Jira or Slack) must be deleted there.
9. Your rights and how to use them
You have these rights:
- To be informed about how your data is processed (this policy).
- To access your data and get a copy in a common electronic format: an account admin exports it from Account settings → Export (a JSON file).
- To correction: edit your data in your profile or account settings, or write to us. You can ask us to restrict processing while the accuracy of the data is disputed.
- To deletion: delete a single report, or delete the whole account yourself in account settings after entering your password.
- To object to processing based on legitimate interest.
- To withdraw consent (section 10).
- To stop non-essential email in your notification settings.
For any request: write to support@umarker.com.
- We check your identity before acting, usually by the request coming from the account’s email.
- We reply within 30 days. We may extend this once by another 30 days, telling you the reason beforehand.
- We may refuse a request that is repetitive, manifestly unfounded or excessive, and tell you why.
- We record every request and how we handled it.
If your data is in a report you sent through one of our customers’ websites, see section 15.
Microsoft Clarity recordings: Microsoft does not offer deletion of one visitor’s data, only of a whole project. So we meet an erasure request by stopping collection from your browser (withdraw consent, or write to us), and the recorded data is deleted when the retention periods in section 8 run out (30 days for recordings, 9 months for click data).
10. Withdrawing consent
Where processing is based on your consent, you can withdraw it at any time, as easily as you gave it:
- AI: an account admin turns it off in account settings.
- Non-essential email: in notification settings.
- Google Analytics on umarker.com and docs.umarker.com: from “Cookie settings” at the bottom of any page; turn “Analytics” off and save, and measurement stops and its cookies are deleted from your browser.
- Microsoft Clarity on umarker.com and docs.umarker.com: the same way; recording stops on the same page and we delete
_clck,_clskand_cltk. We cannot delete Microsoft’s cookies on its own domains (clarity.ms,bing.com): clear them in your browser or use optout.aboutads.info. - Browser signals: we treat a Global Privacy Control or Do Not Track signal as refusing analytics on the two sites.
Whatever depends on the consent stops without undue delay. Withdrawal does not affect what was lawful before it.
11. Complaints
Please write to us first at support@umarker.com, so we can try to resolve it.
You may complain to the Saudi Data & AI Authority (SDAIA) within 90 days of the incident or of becoming aware of it.
If you live in the EU, you may complain to the data protection authority in your country.
12. Automated decisions
- AI features suggest a label, a priority, a duplicate or draft text. A person on the customer’s team reviews each suggestion and accepts or rejects it. They do not make decisions about people.
- We make no solely automated decision that has a legal or similarly significant effect on you.
- Some changes happen automatically under fixed rules in the Terms, not by profiling, for example moving an account to the Free plan when a trial ends or when a renewal is still unpaid after the grace period.
13. Security
- Connections to all our sites are encrypted (HTTPS).
- Passwords are hashed, and integration credentials are encrypted in the database.
- Permissions per role and per action, with protection against raising one’s own permissions.
- Two-factor authentication is available on plans that include it, and mandatory for uMarker staff.
- Every support sign-in to your account is recorded and shown to you under Account settings → Support access, and the session ends after 30 minutes. We sign in to your account only to give support you ask for, to investigate security or abuse, or where a law requires it.
- Customers can turn on masking of sensitive fields and elements before a screenshot is taken.
- In failed-request logs, values of query parameters with sensitive names (such as token or password) are blanked from URLs.
No system is perfectly secure. The service is not designed to collect sensitive data.
14. When someone else gives us your data
If a colleague invites you to a uMarker account, we received from them your email and the role they chose for you, and the account name.
- We use them to send the invitation and to create your membership if you accept.
- The invitation email itself is our notice to you. It reaches you at the time of the invitation and names who invited you, the account and the role. The page where you accept links to this policy.
- If you do not accept, the invitation expires, and we delete it 60 days after it expires or is cancelled.
15. Widget and extension data (we are the processor)
When a customer puts the widget on its website, or its team uses the browser extension, we may process for that customer:
- In every report: the screenshot, the elements the reporter marked and their comment, the page address, and browser details (type, operating system, language, screen size and the previous page).
- If the customer’s website passes them: the reporter’s email and other details the site sends about its user.
- If the customer turns on technical capture for the project: console messages, JavaScript errors, the click trail, the network request log (address, status, timing and size) and page-performance figures. We do not collect headers, cookies or request contents.
- Survey answers, and a random id in the visitor’s browser that prevents duplicate answers.
- Extension testers: the name and email the customer entered for them.
The customer is the controller of this data. If you sent a report through a website, please direct your questions and requests to the owner of that website first. If one reaches us directly, we pass it on and help them carry it out.
Emails a reporter receives about their report are sent by the service on the customer’s behalf, and each has a link to stop them.
16. The uMarker extension for Chrome
- Single purpose: to let a tester report a problem on a page of a website their team owns, with the evidence a developer needs.
- It works only on the websites registered to the tester’s team. It compares each page’s address with that list inside the browser, and sends nothing about any other website.
- It stores locally in the browser: the session token, the tester’s name and email, the team’s account name, and the list of registered websites.
- It sends data only inside a report the tester submits, and only to their team’s uMarker account.
- Before the first connection it shows what is collected, and does not connect until the tester ticks “I understand and agree”.
- No advertising, no analytics, no sale of data, and no use for creditworthiness or lending.
Limited Use disclosure: uMarker’s use and transfer of information received through the uMarker extension adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements. We use or transfer this data only to provide or improve the extension’s single purpose, to comply with the law, or to protect against fraud and abuse. uMarker staff do not read it except with explicit consent, for security purposes, or where a law requires it.
17. Children
The service is for businesses and is not directed to anyone under 18. You must be 18 or older to open an account. If a minor’s data reaches us through a customer’s website, the customer is responsible for it as controller, and we help them delete it.
18. Marketing emails
We do not send marketing emails today. If we start, we will send them only with your prior consent, and every message will carry a free link to stop them. Service emails (invitations, password resets, billing) are not marketing.
19. Cookies and storage
The only optional cookies are those of Google Analytics and Microsoft Clarity on umarker.com and docs.umarker.com, set only with your consent. The full details are in the Cookie Policy.
20. Changes to this policy
We publish every change here with a version number and date. We tell account holders about material changes by email and in the dashboard 30 days before they take effect.