Privacy Policy — DataBlur

The short version

Blurring happens entirely on your device. The pages you blur, the data you hide, and the blurs themselves never reach us.
The extension contacts exactly two servers, both ours: one for licences, one for product analytics. Nothing else.
We self-host our analytics. No Google, no ad SDKs, no third-party trackers. We previously used PostHog; we no longer do, and no analytics data is shared with any third party.
We never sell your data. Not now, not later.

What stays on your device

Everything that matters lives in your browser's local extension storage and is never transmitted:

Your blurs: which elements, areas, and text you blurred, where they sit on the page, and how strong the blur is. For a text blur, the extension necessarily stores the text you selected, so it can restore the blur when you come back. This is stored locally and is never sent anywhere.
Your profiles: saved snapshots of a blur set
Your settings: blur intensity and style, disabled sites, keyword blurlist, which auto-detect categories are on
Your licence state and install date

Uninstalling DataBlur removes all of it. We keep no copy, because we never had one.

What leaves your device

The extension talks to two servers, and only two. Both are ours.

Our licence service

Contacted only if you buy DataBlur Pro and activate a licence key. It runs on Cloudflare and is operated by us. It receives:

your licence key and its instance ID
a short device fingerprint: a truncated hash of a random install ID, your browser's major version, and your platform. Your full user agent never leaves the extension.
a sanitised device label, so you can tell your devices apart in the extension
your purchase email, only if you use "restore my key" or open the billing portal. Restore codes are emailed via Resend.

Our analytics server

Our own Umami instance, self-hosted on servers in the EU. Details below.

Nothing else is sent, ever. Page content, blurred data, URLs, hostnames, page titles, credentials, your user agent, your location, and cookies are blocked in code: a validator inspects every outgoing event and drops it if any of those appear.

Analytics

DataBlur sends anonymous product-usage events so we can see which features are actually used. It is enabled by default and you can turn it off in one click with the "Help improve DataBlur" toggle in the extension popup. Turning it off stops all events, from every part of the extension.

What we send

Feature usage: which blur tool you used, how many blurs you removed, whether auto-detect or the keyword blurlist is on, which detection categories you enabled (never what was detected)
Lifecycle: install, onboarding steps started, completed, or skipped
Pro funnel: when an upgrade prompt was shown, when checkout started, when a licence was activated, when a trial started or expired
Health: error types only (never messages, never stack traces), plus licence and integrity anomalies
A random ID (a UUID generated on your device) so repeat events can be counted as one user. It is not linked to your name or your email.

What we never send

Page content. Blurred data. The text you blurred. URLs. Hostnames. Page titles. Credentials. Your user agent. Your location. Cookies. This is not a promise on paper: the extension refuses to transmit an event containing any of them.

Turning it off

Open the extension popup, go to Settings, and switch off "Help improve DataBlur". When you do, we also delete the random ID stored on your device. If you turn analytics back on later, a fresh ID is generated, so your new activity is not joined to your old activity. Turning analytics off does not change how DataBlur works.

The website

datablur.app uses the same self-hosted analytics. If you install the extension after visiting the site, the site can pass its random ID to the extension so we can tell that the install came from the site. This only happens on datablur.app and the extension verifies the origin before accepting it.

Analytics events are only transmitted from released builds. Development builds never send anything.

Payments

DataBlur Pro is sold through Creem, which acts as the Merchant of Record. Creem processes your payment, handles tax, and issues your invoice under its own privacy policy. We never see or store your card details. Your purchase email is stored locally in the extension only to prefill the restore and billing forms.

Retention

On-device data (blurs, profiles, settings, licence): kept until you delete it or uninstall the extension
Analytics events: kept for up to 12 months on our own servers, then deleted
Licence records: kept while your licence is active, and for as long as tax and accounting law requires (handled by Creem as Merchant of Record)

Permissions the extension asks for

Storage: to keep your blurs, profiles, and settings on your device
Context menus: the right-click "Blur element" and "Blur text" actions
Tabs: to route keyboard shortcuts to the right page and show the blur count on the toolbar icon
Access to the pages you visit: blurring only works if DataBlur can run on the page you are about to show. It reads the page to blur it, locally. It never sends it anywhere.

Your rights (GDPR / CCPA)

Opt out: switch off "Help improve DataBlur". No account, no form.
Access and portability: email support@datablur.app. Because analytics is tied only to a random ID, include that ID (the extension popup shows it in the support link) so we can find your records.
Deletion: ask us and we delete your analytics records. Uninstalling removes everything stored on your device.
No discrimination: opting out changes nothing about how DataBlur works.
No sale of data. We do not sell personal information and never have.

Store compliance

Single purpose: hiding sensitive content on screen during demos, recordings, and screen sharing
No data sold, ever
Third parties: Creem (payments) and Cloudflare (hosting the licence service). Analytics is self-hosted and shared with nobody.
Everything in transit is encrypted with HTTPS

Changes to this policy

We update this policy as DataBlur changes. The effective date at the top always reflects the current version, and significant changes are noted in the extension release notes.

Contact

Questions, privacy requests, or abuse reports: support@datablur.app