Security and privacy

What never reaches us
cannot be lost

The widget runs on your site, on pages that hold your customers' data. So our first question is not what we could collect. It is what we do not need at all.

This page describes what the code does today, not what is planned.

The layers

One report, and five layers it passes through.

  1. Domains are the identityThe widget only runs on the domains you listed.
  2. Field masking is a switch you turn onWith it on, field values are masked on the page itself before the screenshot. It ships off.
  3. Failed-request URLs are cleaned alwaysThe value goes, not the URL.
  4. The AI features are switched offNothing leaves your account for a model unless you switch consent on and bring your own key.
  5. Screenshot retention — set by your planA nightly job clears the image past your plan's window. The report itself is kept forever.

02

Failed-request URLs are cleaned always, with no switch to find.

A failed request is recorded with its full path, and the values of parameters whose names suggest a secret are blanked at capture. The value goes, not the URL.

Captured /api/session?access_token=abc123&page=2
Stored /api/session?access_token=[redacted]&page=2

page=2 survives because it is frequently why the request failed. The names whose values are blanked: token, key, secret, password, auth, session, otp, email, phone and their neighbours — in camelCase too.

This is the failed-request list and nothing wider. The address of the page the report was filed from is stored as it is, shown on the report, and carried into the ticket.

03

Field masking is a switch you turn on.

With it on for a project, field values and the regions you name are masked on the page itself before the screenshot and restored afterwards. It ships off.

Automatic masking

On for this project

Sensitive regions .card-number .cvv

The default is off, so a project you have not switched it on for sends the screenshot as it is. You turn it on per project, in the widget settings.

04

How long we keep it, and what exactly goes.

Two different windows, and one of them clears the image and keeps the report.

Screenshot retention — set by your plan

A nightly job clears the image, the recording and the attachments past your plan's window. The report itself is kept forever: its title, its text, its pins, its status, its comments and its technical context. What goes is what costs storage.

A retention policy — set by you

You choose a window for your account (7 to 3,650 days), and a second nightly job deletes reports older than it in full, with their media. That one is a plan feature, and it unlocks on Agency.

Export — on every plan

You export your whole account as one JSON document, with no secrets in it: no passwords, no tokens, no integration credentials. Taking your data with you is a right, not a feature we sell.

Erasure — the account, or one report

You delete the whole account with your password, or a single report when a visitor asks for theirs to be erased. That removes the rows, the files, the pins, the comments and the bell notifications that quote it.

05

Who can see what.

Permissions are per action, and support access is written down in front of you.

A permission per action

Two built-in seats, plus custom roles where you set every permission individually and give a different role per project. Custom roles are a plan feature, and unlock on Professional.

Two-factor authentication

Available for your account, as a plan feature that unlocks on Starter. On our own operator console it is required: nobody gets in without it.

Support access is on the record

If someone on our side opens your account for support, you find it under Account management: when it happened, as which member, and when it ends. The session lasts 30 minutes and expires on its own.

Domains are the identity

The widget only runs on the domains you listed. If your public key is copied and pasted onto another site, it does not run and collects nothing.

06

What we do not have yet.

Better said before your procurement review than during it.

Have a specific security requirement you need settled first? Ask us directly and you will get a straight answer.

07

Reporting a vulnerability.

We thank everyone who reports responsibly, and we answer every report.

Where to report

Write to security@umarker.com, or to support@umarker.com if you hear nothing back. Include the URL or page, the steps to reproduce, and the impact as you see it. Both addresses are also published in security.txt.

What we do

We acknowledge your report within 5 business days, tell you what we found and when it will be fixed, and credit you when it is, if you want us to. We ask you not to publish details until it is fixed or 90 days have passed since your report, whichever comes first.

Scope

umarker.com, docs.umarker.com, app.umarker.com, api.umarker.com, the widget and the browser extension. Out of scope: denial of service, social engineering, spam, and third-party integrations a customer connects itself.

Good-faith research

We will not pursue legal action against good-faith research within these limits: use your own account or a trial one, stop at the first access to someone else's data and keep none of it, and do not degrade the service for anyone else.

Step 1 of 2

Request your account

Who are you?