No signed DPA
There is no data-processing agreement ready to countersign, and no contractual subprocessor list with a change-notice commitment. The processor/controller split described above is how the product behaves; the paperwork is not written.
When your team collects feedback through uMarker, you are the data controller and uMarker is the processor. Reports, screenshots, console logs and reporter email addresses belong to your account; uMarker processes them to provide the service and for nothing else. Saudi Arabia’s Personal Data Protection Law (PDPL) is the frame this is written against, and the same mechanics answer the equivalent GDPR questions.
Informing your visitors and obtaining consent where it is required is your job as the controller. uMarker gives you the tools: a notice shown next to the send button before anything is transmitted, your own privacy-policy link in that notice, and everything on this page.
What a report contains depends on the project’s capture mode, set by your team under
Widget → Setup. A Normal report carries the annotated screenshot, per-pin comments, the page
URL, and the device — type, browser and OS, language, screen and window size. A Technical report
adds console log entries, the page’s network requests (failed and slow ones flagged), JavaScript
errors, performance figures, reproduction breadcrumbs (recent clicks and route changes) and
environment details. Either mode can carry the CSS selector of a marked element, and the reporter’s
email address if they give it. If your page called
uMarker.identify(), whatever it passed (typically an email) is attached too, and the notice next to
the send button says so explicitly.
Two safeguards run in the reporter’s browser before anything is sent. Secret-named query-string values are blanked on every project. Masking typed values and marked regions out of the screenshot is a per-project switch, Auto-redact sensitive fields, that a new project ships with off. Either way, no mode ever captures headers, cookies, request or response bodies, or stored values. See PII redaction.
| Control | Where | Notes |
|---|---|---|
| Full data export: one JSON document, every account-scoped table except three named exclusions | Manage account → Account settings | Never includes a secret: no password hashes, 2FA secrets, API key hashes, tracker credentials, webhook secrets or invitation tokens. The three left out are platform pricing configuration, our internal support notes about your account, and our own fault telemetry — each carrying a written reason, and the policy call on the support notes is set out in COMPLIANCE.md |
| Retention window: auto-delete reports older than N days, media included | Manage account → Account settings | 7 to 3650 days, or empty for no limit. Runs nightly. Requires the governance capability (Agency and above) |
| Erase a single report | The report’s own page | For a visitor’s erasure request, or a screenshot that caught something it shouldn’t. Deletes the row, the files, the pins, the comments and the bell notifications that quote it |
| Hard account deletion: every row and every stored file, except the issued invoices named below | Manage account → Account settings | Requires your password. Real deletion, not a soft-delete flag |
| Reporter unsubscribe list | Email suppressions page | Every reporter email carries a signed unsubscribe link; suppressed addresses are listed, with the control to undo it |
| Two-factor authentication | Manage account → Security | Available from Starter upward |
| AI consent | AI page | Off on every account until someone deliberately turns it on |
Two clocks run over your data, and they are not the same thing:
So “keep everything” keeps every report for ever, and old screenshots still go. When your plan includes the retention policy, the account settings page names both numbers next to each other for exactly that reason.
Deletion is real deletion: rows go from the database and files go from storage. Two things outlive it, and both are named rather than discovered later:
Billing is a manual transfer approved by a person — bank, wallet, or whichever rails the operator has defined. There is no card gateway and no card details anywhere in the system: a payment request carries the plan, the amount, and, where the chosen method asks for them, a transfer reference and a receipt image you upload. There is no VAT line and the invoice is not a tax invoice; it is a numbered commercial invoice in Saudi riyals with both parties recorded on it.
This is the part worth reading twice, because everything above is a mechanism and this is not:
No signed DPA
There is no data-processing agreement ready to countersign, and no contractual subprocessor list with a change-notice commitment. The processor/controller split described above is how the product behaves; the paperwork is not written.
No certification or audit letter
No SOC 2, no ISO 27001, no published penetration test.
No announced hosting region
The region is a deployment setting that has not been decided and published. Do not read residency into this documentation, whether in the Kingdom, in the EU, or anywhere else.
No breach-notification runbook yet
PDPL’s notification duty is understood and the audit trail exists to answer it, but the runbook itself is unwritten.
If your review needs any of these, say so. They are owner decisions with a timeline, not things the product will quietly claim in the meantime.