Cookie and Storage 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. What these are
- Cookies: small text files a website saves in your browser, which the browser sends back with later requests.
- Local storage (localStorage): space in your browser where a website keeps values until they are cleared.
- Session storage (sessionStorage): the same, but cleared when the tab closes.
Here we call them all “storage items”.
2. Summary
- Two optional tools, in two places only: on the marketing site (umarker.com) and the docs site (docs.umarker.com) we use Google Analytics and Microsoft Clarity, and neither runs until you accept the “Analytics” category in the consent banner. Before you accept, no Google or Microsoft script is loaded and no cookie of theirs is set. Details in section 3.
- Neither Google Analytics nor Microsoft Clarity runs in the dashboard (app.umarker.com), the operator console, the widget on our customers’ websites, the browser extension, or the pages on api.umarker.com. None of those surfaces uses any optional tool.
- We show no advertising and use no advertising tool. We have turned off every Google data-sharing setting in our Google Analytics account, and we tell Microsoft Clarity that we do not allow advertising storage. But Microsoft acts as an independent controller for Clarity, and may use the data it collects for its own purposes, including advertising (section 3).
- Apart from that, 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.
- Everything other than Google Analytics and Microsoft Clarity is either necessary for the service you asked for, or a preference you chose yourself (such as language or theme), so it needs no consent.
- That is why the consent banner appears on umarker.com and docs.umarker.com only, with “Reject all” as easy as “Accept all”. If your browser sends a Global Privacy Control (GPC) or Do Not Track signal, we treat it as a refusal: no banner, and nothing optional runs (section 10).
3. umarker.com and docs.umarker.com
| Name | Type | Purpose | Lifetime | Category |
|---|---|---|---|---|
md-theme |
Local storage | Your theme choice: light, dark or auto | Until you clear it | Preference |
um_reg_open |
Local storage | Whether sign-up is open right now, so the account buttons (“Request access” or “Create account”) show the right one without flicker | Until you clear it | Necessary |
um_signed_in |
Cookie set by the dashboard (see section 4), only read here | If you are signed in to the dashboard, the site shows “Dashboard” instead of “Sign in” | 30 days; deleted on sign-out | Necessary |
sl-sidebar-state (docs.umarker.com only) |
Session storage | Open groups and scroll position in the sidebar | Until the tab closes | Necessary |
md_consent |
Local storage | Your choice in the consent banner, when you made it, and a random id for it | 180 days, then we ask again | Necessary |
_ga |
First-party cookie set by Google Analytics, for this site only (not shared with our other domains) | Distinguishing visitors | 2 years (the default, per Google’s documentation; some browsers, such as Chrome, cap it at 400 days) | Analytics — only with your consent |
_ga_ZWDPW9E0E1 |
First-party cookie set by Google Analytics, for this site only | Keeping session state | 2 years (the default, per Google’s documentation; some browsers, such as Chrome, cap it at 400 days) | Analytics — only with your consent |
_clck |
First-party cookie set by Microsoft Clarity, for this site only | A pseudonymous visitor id and Clarity’s settings, linking your visits to this site | 1 year (365 days) | Analytics — only with your consent |
_clsk |
First-party cookie set by Microsoft Clarity, for this site only | Joining the pages you visit into one session recording | 1 day | Analytics — only with your consent |
_cltk |
Session storage, set by Microsoft Clarity | Telling the current tab apart within the session | Until the tab closes | Analytics — only with your consent |
Google Analytics on these two sites:
- When it runs: only after you choose “Accept all”, or allow the “Analytics” category under “Settings”. Before that, its script is not loaded from
www.googletagmanager.com, nothing is sent to Google, and the_gaand_ga_ZWDPW9E0E1cookies do not exist. - What it collects: the pages you visit, the page you came from, your approximate location (country and city, which Google derives from your IP address), your device type, browser, operating system, language and screen size, and the interactions it measures automatically (scrolling, clicks on outbound links, site search, form and embedded-video interactions, and file downloads).
- Who: Google LLC (United States), or Google Ireland Limited where Google’s terms provide for it. Data is processed in the United States and other countries, per Google. See the Sub-processors page.
- What we do not do: we do not link it to Google Ads, we do not turn on Google Signals, and we have turned off every Google data-sharing setting in the account. We send it no name, no email, and no data from the dashboard.
- Each site asks for itself: umarker.com and docs.umarker.com each keep these two cookies on their own host only, so neither is sent to the other site, to the dashboard or to the API. That is why each site asks you separately, and accepting on one does not apply on the other.
- Withdrawing consent: open “Cookie settings” at the bottom of any page on either site, turn “Analytics” off, and save. Measurement stops at once, and we delete
_gaand_ga_ZWDPW9E0E1from your browser. We ask again after 180 days.
Microsoft Clarity on these two sites:
- When it runs: only after you choose “Accept all”, or allow the “Analytics” category under “Settings”, on the site you are on. Before that, its script is not loaded from
www.clarity.ms, nothing is sent to Microsoft, and_clck,_clskand_cltkdo not exist. - What it records: how you interact with the page: clicks, scrolling, mouse movement, the page layout, the pages you visit and the page you came from. We see these as heatmaps and session recordings (a replay of what happened on the page). We hide all page text and everything you type into any field, so it is not sent to Microsoft and shows as placeholder symbols in a recording. It also collects your approximate location derived from your IP address, and your device type, browser, operating system and screen size.
- Why: to see where visitors get stuck on the two sites and improve the pages.
- Who, and in what role: Microsoft Corporation (United States), or Microsoft Ireland Operations Limited where Microsoft’s terms provide for it. Microsoft acts as an independent controller of the Clarity data: it uses the data for its own purposes under the Microsoft Privacy Statement, which may include building profiles for purposes that include advertising. We always tell Clarity that we do not allow advertising storage (
ad_Storage: denied), and we do not link it to any advertising account, but we do not control what Microsoft does with the data it receives. - Microsoft’s cookies on its own domains: Microsoft may also set third-party cookies on its own domains (
clarity.msandbing.com), includingCLID,MUID,ANONCHK,MRandSM. According to Microsoft,MUIDidentifies browsers visiting Microsoft sites and is used for advertising, site analytics and other operational purposes. Microsoft sets their lifetimes. They are not on our domain, so we cannot delete them, and many browsers block them by default. - Where: in the Microsoft Azure cloud, in the United States and other countries where Microsoft operates.
- How long Microsoft keeps it: session recordings 30 days. Click and heatmap data, and sessions we label or mark as favourites, 9 months (Microsoft says a random sample of recordings may also be kept for up to 9 months). Microsoft then deletes it, including backups.
- Each site asks for itself: we keep
_clckand_clskon the host that set them only, so each site asks you separately, as with Google Analytics. - Withdrawing consent: from “Cookie settings”, turn “Analytics” off and save. We tell Clarity you withdrew and stop it on the same page, so it sends nothing more, and we delete
_clck,_clskand_cltkfrom your browser. Clear Microsoft’s cookies on its own domains in your browser settings, or use the opt-out page Microsoft points to: optout.aboutads.info. - Deleting what was recorded: Microsoft does not offer deletion of one visitor’s data, only of a whole project. If you ask us to delete it, we stop collection from your browser, and the recorded data is deleted when the periods above run out.
- Where it never runs: the dashboard, the operator console, the widget on our customers’ websites, the browser extension, the pages on api.umarker.com, and the “page not found” (404) page on either site, because its address may carry text you pasted.
4. The dashboard (app.umarker.com)
| Name | Type | Purpose | Lifetime | Category |
|---|---|---|---|---|
__Host-um_s |
Cookie (HttpOnly) | Your sign-in session; no script on the page can read it | Until sign-out or the browser closes; the server ends it after 3 hours idle and 12 hours at most (7 days with “remember me”) | Necessary |
__Host-um_imp_… |
Cookie (HttpOnly) | A uMarker support session in your account, in one tab | 30 minutes at most | Necessary |
md_session |
Local storage | A “signed in on this browser” flag, holding no secret | Until sign-out | Necessary |
um_signed_in |
Cookie on umarker.com and its subdomains | A “signed in on this browser” flag our site and docs read to show a “Dashboard” button; its value is just 1 — no secret, no identifier, no personal data, and it grants no access |
30 days; deleted on sign-out | Necessary |
md_imp |
Session storage | The id of this tab’s support session (not a secret) | Until the tab closes | Necessary |
md_active_workspace |
Local storage (session storage during support access) | The space you are working in | Until sign-out | Necessary |
md_theme |
Local storage | Theme | Until you clear it | Preference |
md_locale |
Local storage | Language | Until you clear it | Preference |
md_rail |
Local storage | Sidebar state | Until you clear it | Preference |
md_chunk_reload |
Session storage | One reload after an app update | Until the tab closes | Necessary |
The dashboard’s two session cookies (__Host-um_s, __Host-um_imp_…) live on app.umarker.com alone — no shared domain, no tracking. They are personal data, because they link the browser to an account. The third, um_signed_in, is shared with our own site and docs on purpose and carries nothing but 1.
5. Pages on api.umarker.com
api.umarker.com shows only a few pages: the public changelog page, the signed screenshot link, the reporter unsubscribe/resubscribe page, and the email change/verification page. On these pages only:
| Name | Type | Purpose | Lifetime | Category |
|---|---|---|---|---|
umarker_session |
Cookie (HttpOnly, Secure, SameSite=Lax) | Session id that protects the unsubscribe form against forged requests (CSRF). Session data stays on the server | 120 minutes | Necessary |
XSRF-TOKEN |
Cookie (Secure, SameSite=Lax) | Token protecting against forged requests | 120 minutes | Necessary |
The API itself (/api/*) sets no cookies.
6. Operator console (admin.umarker.com)
For uMarker staff only. It stores the sign-in token and the reload marker (necessary), and display preferences such as theme, language and dashboard layout (preferences). No optional cookies.
7. For customers: what the widget stores on your website
When you put the uMarker widget on your website, it stores items in your visitors’ browsers, on your website’s domain. You are the controller of this storage. You should list it in your own cookie or privacy policy, and decide whether it needs consent under the laws that apply to you.
- The widget sets no cookies, and sends all its requests without cookies (
credentials: 'omit'). - All items are in local storage.
<key>is your project’s public key, and<id>is a survey or announcement id.
| Name | Purpose | Lifetime | Personal data |
|---|---|---|---|
md_draft_<key> |
A report not sent because of a connection failure, kept to resend: comment, marks, screenshot if it fits, and page address. The email and technical details are not kept | Until sent; dropped after 72 hours | Yes |
umarker:draft:<key>:<url> |
Marks and notes the visitor drew but has not sent yet | Until sent or discarded; ignored after 7 days | Possibly (free text) |
md_vid |
Random id created on the first survey answer, to prevent duplicate answers | Until cleared | Pseudonymous id |
md_freq_<key> |
Display frequency rule: times shown and last use | Until cleared | No |
md_mode_<key> |
Capture mode (normal or technical) | Until cleared | No |
md_survey_<id> |
The visitor answered the survey | Until cleared | No |
md_survey_seen_<id> |
The survey was shown | Until cleared | No |
md_survey_dismiss_<id> |
The visitor closed the survey (honoured for 24 hours) | Until cleared | No |
md_ann_seen_<id> |
The announcement was shown | Until cleared | No |
md_ann_beacon_<id> |
The announcement view was counted | Until cleared | No |
md_ann_click_<id> |
The visitor clicked the announcement | Until cleared | No |
md_cl_seen |
The last “What’s new” entry the visitor saw | Until cleared | No |
In technical capture mode only: the widget reads the names (not the values) of up to 50 of your site’s own storage keys and adds them to the report.
The dashboard shows this same table under Project → Widget → Snippet.
8. The browser extension
The extension keeps its data in chrome.storage.local, which is private to the extension and out of reach of web pages:
token: the session token.widgetUser: the tester’s id, name and email.account: the team’s account name.hostsandhostsAt: the registered website list and when it was fetched (refreshed at most every 5 minutes).deepBlocked: whether a browser policy blocked technical capture last time.apiBase: an alternative API address, if set.- The widget items in section 7, per website, prefixed
ext_<host>. In the extension,md_vidis one id across all websites.
On registered pages the tester visits only: md_mode_ext in session storage (capture mode only).
This data stays until the extension is removed from the browser.
9. How to control storage
- Google Analytics and Microsoft Clarity cookies on umarker.com and docs.umarker.com: from the “Cookie settings” link at the bottom of every page, at any time (section 3). Microsoft’s cookies on its own domains (
clarity.ms,bing.com) are cleared in your browser settings. - In your browser: you can clear or block cookies and storage for any site in your browser settings. Clearing app.umarker.com’s cookies signs you out of the dashboard. Blocking storage may stop the dashboard from working.
- The extension: remove it from the browser to clear all its data.
- For customers: you can turn the widget off for a project, and limit where surveys and announcements appear, in the project settings.
10. How we ask for consent
The optional tools today are Google Analytics and Microsoft Clarity on umarker.com and docs.umarker.com (section 3). They, and any optional tool we add later, follow the same rules:
- A “Cookie settings” link at the bottom of every page on both sites.
- Every optional category is off by default; nothing from it is loaded or stored before you consent.
- Rejecting is as easy as accepting, on the first screen.
- You can withdraw consent at any time from the same link.
- We record your choice and when you made it, with nothing that identifies you.
- We update this policy with each tool, its purpose and its lifetime before turning it on, and we ask you again when we add one.
- We honour browser signals as a refusal: if your browser sends a Global Privacy Control or Do Not Track signal, we treat it as refusing every optional category: no banner, neither Google Analytics nor Microsoft Clarity runs, and nothing is stored or recorded. If you still want to allow analytics on a site, turn it on yourself in “Cookie settings”; we treat that as your explicit choice and keep it.