Privacy Policy

Introduction

At Blurr.ing (“we”, “our”, or “us”), we are committed to protecting your privacy. This Privacy Policy explains how we collect, use, disclose, and safeguard your information when you use our Blurr.ing Chrome extension (“Extension”) and the blurr.ing website.

Please read this Privacy Policy carefully. By installing, accessing, or using the Extension, you acknowledge that you have read, understood, and agree to be bound by the terms of this Privacy Policy. If you do not agree with our policies and practices, please do not use our Extension.

What Stays on Your Device

Your blurs: when you blur something, the Extension saves the blur’s position, size, intensity, and a small technical snapshot of the blurred element (its selector and a short fragment of its text, so the blur can find its place again after a reload). All of this is stored locally in your browser using Chrome’s storage API (chrome.storage.local) and is never transmitted to our servers or to anyone else, whether you are signed in or not.

The pages you blurred: the list of sites and pages where you placed blurs is likewise stored only on your device and never uploaded or synced.

Housekeeping: blur records from ordinary sessions that you did not choose to keep are cleaned up automatically after about 60 days. Uninstalling the Extension removes all locally stored Blurr.ing data.

Information We Collect

Product events: the Extension contains no third-party analytics, advertising, or tracking SDKs. It reports a short, fixed list of first-party product events to our own server (for example: installed, blur created, paywall viewed, checkout started) together with a random install identifier. These events never include page URLs, page content, or anything you blurred, and they are deleted automatically after 180 days. If you uninstall the Extension, your browser opens a short feedback page that receives the same random identifier.

Account information (optional): an account is only needed for Premium. If you sign in with Google, we receive your Google account’s ID, email address, name, and profile picture through Google’s official sign-in flow, and we use them to create and operate your account. Sign-in tokens are stored locally on your device, and signing out revokes them.

Fraud prevention: when you sign in, the Extension also sends a one-way hash derived from technical characteristics of your browser. We store only the hash and use it solely to prevent abuse of the free plan, such as farming free allowances across many accounts from one browser. The raw characteristics never leave your device.

Payment information: payments are processed by Stripe on Stripe’s own checkout pages, and we never see or store your card number. We keep your plan, subscription status and dates, currency, and Stripe’s customer and transaction identifiers. Stripe shares the name and billing address you enter at checkout so we can email your receipt.

Synced settings (signed in only): so that your setup can be restored when you sign in again, your Auto Blur configuration and your Blur Text rules sync to your account. This includes the keyword patterns you define and the site hostnames or page paths those rules apply to, along with preferences such as theme and Tab Privacy. Your drawn blurs and the list of pages you blurred never sync.

Pricing region: requests for pricing include your browser’s timezone, and our infrastructure derives an approximate country from the network request, only to decide whether to show prices in USD or EUR. We do not collect or store your precise location or your IP address.

How We Use Your Information

We use the information we collect to:

• Provide, maintain, and improve the Extension
• Operate your account and your Premium subscription
• Process payments and send transactional email: a welcome email, payment receipts, payment-failure notices, cancellation confirmations, and a one-time reminder if you start a checkout and do not finish it
• Prevent abuse of the free plan
• Understand, in aggregate, which features are used
• Detect, prevent, and address technical issues

We do not send marketing email, and we never sell or rent your information.

Data Storage and Security

Blur data lives in your browser, as described above. Account, subscription, and synced-settings data is stored in our database on our own server infrastructure and is reached only over encrypted connections.

We implement appropriate technical and organizational measures to protect the security of any information we process. However, no method of transmission over the Internet or electronic storage is 100% secure, and we cannot guarantee absolute security.

Third-Party Services

The Extension includes no third-party analytics or advertising services. We share information only with the service providers that make Blurr.ing work, and only what each one needs:

• Google: the optional sign-in flow
• Stripe: payments, subscriptions, and billing
• Cloudflare: hosting and network for the website and API, and the waitlist database
• DigitalOcean: hosts our backend server
• Namecheap (PrivateEmail): delivers our transactional email

We may also disclose information in these limited circumstances:

• To comply with legal obligations
• To protect and defend our rights and property
• To prevent or investigate possible wrongdoing in connection with the Extension

Chrome Permissions

The Extension asks for the smallest set of Chrome permissions that lets it work everywhere. For a permission-by-permission breakdown of what each one enables and what it does not allow, see security and permissions.

• Access to the sites you visit (including frames): so blurs can be drawn on any page and restored before the page first paints, and so Auto Blur and Blur Text can scan for content to hide. All scanning runs on your device; page content is not sent anywhere.
• Storage: to save your blurs and settings locally. Screenshots are never among them: a capture you take is held in memory only, for as long as its card is open.
• Scripting and Tabs: to apply blurs to the page you are on, and to let Tab Privacy mask tab titles and favicons, which also happens entirely locally
• Identity: only for the optional Google sign-in
• Alarms: to refresh pricing and subscription status periodically in the background

The Extension cannot record your screen and cannot see anything outside the browser. It takes a screenshot only when you ask for one, with the keyboard shortcut, the camera button or the popup row: that image is created in your own browser, is never uploaded to us or anyone else, and is not stored anywhere unless you save or copy it yourself. It writes to your clipboard only on that Copy, and it never reads your clipboard, never reads or sets cookies, and never touches your location.

Data Retention and Deletion

• Product events are deleted automatically after 180 days.
• Local blur data stays on your device until you delete it or uninstall the Extension; stale session blurs are cleaned up after about 60 days.
• Account data is kept while your account is active. To delete your account and the data associated with it, email [email protected] and we will remove your account records within 30 days.
• Waitlist emails are removed on request at any time.

Website Analytics and Cookies

The blurr.ing website (not the Extension) uses two analytics tools to understand how visitors find and use the site:

• Ahrefs Analytics is cookieless. It records aggregate page statistics without storing anything on your device, which is why it runs without asking for consent.
• Google Analytics sets cookies, so it loads only after you choose Accept in the cookie banner. If you reject, or simply never answer, it does not load at all.

You can change your choice at any time via the Cookie settings link in the footer. Withdrawing consent stops Google Analytics and deletes its cookies. The Extension itself loads no third-party analytics; the only product data it sends is the anonymous event list described above.

Waitlist (closed)

Before Blurr.ing was published we ran a launch waitlist. If you joined it, we stored the email address you submitted, together with the page it was submitted from, your country (derived from the request by our hosting provider), your browser’s user-agent string, and a timestamp, in a database hosted by Cloudflare.

The form has been removed and we are no longer collecting addresses. We used this information solely to email you about the Blurr.ing launch, and to understand where signups came from. We never sold or shared the waitlist, and you can have your email removed at any time by writing to [email protected].

Your Choices and Control

You can view, move, and delete any blur or saved rule from the Extension interface, and switch Auto Blur, Blur Text, or Tab Privacy off at any time. You can sign out at any time, which revokes your sign-in tokens. Uninstalling the Extension removes all locally stored data.

To delete your account and its data, or to ask what we hold about you, email [email protected]. On the website, use the Cookie settings link in the footer to change your analytics choice.

Children’s Privacy

Our Extension is not intended for children under 13 years of age. We do not knowingly collect personal information from children under 13. If you are a parent or guardian and believe your child has provided us with personal information, please contact us so that we can delete such information.

Changes to This Privacy Policy

We may update our Privacy Policy from time to time. We will notify you of any changes by posting the new Privacy Policy on this page and updating the “Last Updated” date at the top. You are advised to review this Privacy Policy periodically for any changes.

Contact Us

If you have any questions or concerns about this Privacy Policy or our data practices, please contact us at: