Download

Privacy Policy

Effective Date: 2025-11-05 | Version: 2.2.2 | Last Updated: 2026-01-26

Overview

DataBlur Pro is committed to protecting your privacy. This policy explains how we collect, use, and protect your data.

Key Principle: We collect the minimum data necessary to improve DataBlur. All data collection is optional and user-controlled.

What We Collect

Always Collected (No User Control)

  • Nothing – DataBlur stores all blur data locally on your device

Optionally Collected (User Controlled)

  • Analytics data (if enabled) – See below

Analytics (Optional Feature)

DataBlur includes optional analytics to help us understand how users interact with the extension.

By default, analytics is ENABLED. You can disable it anytime using the toggle switch.

How to Enable/Disable Analytics

  1. Click the DataBlur extension icon
  2. Look for “Help improve DataBlur” toggle switch
  3. Toggle ON to enable analytics (or OFF to disable)
  4. Your choice is saved and persists across sessions

What’s Collected When Analytics Enabled

Collected

  • Feature usage: Which blur tools you use (element, area, text, auto-detect)
  • Feature adoption: Whether you enable auto-detection
  • Auto-detection preferences: Which PII categories you enable/disable (e.g., “email”, “phone”) – NOT what was detected
  • Error tracking: Technical errors (not user data), for stability improvements
  • Performance metrics: How long it takes to create blurs, auto-detect results
  • Session metrics: “Aha moment” – when you first realize the extension is useful

NOT Collected

  • No website URLs or hostnames – We don’t know which sites you visit
  • No page titles – We don’t know what you’re reading
  • No blur content – What you blur is private (we don’t collect it)
  • No passwords, emails, or credentials – Sensitive data never leaves your device
  • No personal information – Age, device ID, IP address
  • No browsing history – We only see blur-related events
  • No session recordings – We don’t record your screen or activity

Example: What We See vs. What We Don’t

Example 1: Manual Blur

You: Visit your bank at https://mybank.com/checking-account and manually blur your account number

What we see: “User created blur (type: element, source: manual)”

 

What we don’t see:

  • The URL https://mybank.com
  • Your account number
  • Your balance
  • The page title
  • Anything about your account

Example 2: Auto-Detection Preferences

You: Enable email detection, disable phone detection in auto-detection settings

What we see: “User toggled category: email, state: enabled” and “User toggled category: phone, state: disabled”

 

What we don’t see:

  • Which emails were detected
  • Your actual email address
  • Which page you were on
  • What content was blurred
  • Any detected phone numbers

How We Protect Your Data

1. Multiple Validation Layers

All analytics events go through 4 layers of validation before leaving your device:

  1. Coordinator Layer – Verifies user consent AND feature enabled
  2. Service Layer – Strips automatic context properties
  3. Validator Layer – Checks against whitelist of allowed properties
  4. PostHog SDK – Final sanitization before network transmission

2. Privacy-First Defaults

Consent: ON by default (user can opt-out anytime)
Collection: Only explicit data (no auto-context)
Validation: Whitelist model (deny-by-default)
Network: HTTPS encrypted (to PostHog)

3. No PII in Error Tracking

If an error occurs:

  • Yes: We track the error TYPE (e.g., “storage_quota_exceeded”)
  • No: We DON’T track error messages (could contain sensitive data)
  • No: We DON’T track stack traces (could reveal system info)

4. User ID is Stable but Pseudonymous

  • We generate a unique ID to recognize returning users (e.g., ext_user_1699123456_abc123)
  • This ID is stored locally on your device
  • It’s NOT linked to your identity
  • You can’t be identified from this ID alone

Who Processes Your Data

PostHog (Analytics Provider)

Provider: PostHog Inc Service: PostHog Cloud (https://posthog.com)

 

What PostHog receives:

  • Analytics events (described above)
  • Your pseudonymous user ID
  • Session/usage metrics
  • Error frequency and types

 

What PostHog does NOT receive:

  • Personal information (name, email, location)
  • Website URLs or page titles
  • Sensitive data (blur content, passwords, credentials)
  • Device fingerprinting data

 

PostHog’s Privacy: https://posthog.com/privacy

Data Retention

Local Data

  • Blur data: Stored on your device until you manually delete
  • Consent setting: Stored until you change it
  • User ID: Stored for extension lifetime (until uninstall)

Analytics Data

  • On PostHog servers: Retained for 90 days (PostHog default)
  • Aggregated reports: Kept for product improvement

Your Rights (GDPR/CCPA)

Right to Opt-Out (Easiest)

Simply disable the “Help improve DataBlur” toggle in the extension popup. No data will be collected going forward.

Right to Access

PostHog stores events under your pseudonymous user ID. To access:

  1. Contact us at support@datablur.app
  2. Provide your user ID (if you know it)
  3. PostHog will export all events associated with your ID

Right to Delete

  1. Disable analytics in extension popup
  2. Uninstall the extension (deletes local data)
  3. Contact support@datablur.app to request deletion from PostHog

 

Note: Even with analytics disabled, blur data remains stored locally until you delete it manually.

Right to Data Portability

Contact support@datablur.app with your user ID. We can export your analytics history in a standard format.

Chrome Web Store Compliance

DataBlur complies with Chrome Web Store privacy practices:

Single Purpose: Extension’s stated purpose is screen recording protection

Transparency: This policy discloses all data collection

User Control: Analytics toggle gives users full control

No Selling: We never sell user data

No Third-Party Sharing: Only PostHog receives events

Security: HTTPS encryption in transit, validation before transmission

California Resident Privacy (CCPA)

If you’re a California resident, you have additional rights:

  • Right to Know: What data we collect
  • Right to Delete: Request deletion of your data
  • Right to Opt-Out: Disable analytics (turn off toggle)
  • Right to Non-Discrimination: Opting out doesn’t affect extension functionality

 

To exercise these rights, contact: support@datablur.app

Changes to This Policy

We may update this policy as the extension evolves. We’ll notify you of major changes:

  • In this document (dated above)
  • In extension release notes
  • Via email (if we add email collection)

Contact Us

Questions about privacy? Email: support@datablur.app

Report privacy issue? Email: support@datablur.app

Report abuse? Email: support@datablur.app

FAQ

Q: How can I verify DataBlur doesn’t collect my blur data?

A: DataBlur’s validation layers ensure NO blur content, URLs, or sensitive data ever leaves your device. We use:

  1. Coordinator Layer – Verifies user consent AND feature enabled
  2. Service Layer – Strips automatic context properties
  3. Validator Layer – Checks against whitelist of allowed properties
  4. PostHog SDK – Final sanitization before network transmission

For detailed information about our validation approach, contact: support@datablur.app

Q: What if I don’t trust PostHog?

A: You can:

  1. Disable analytics in extension popup (immediate, no data sent)
  2. Run without analytics (configure build with empty PostHog API key)
  3. Use alternative extension if you prefer complete opt-out

The extension works perfectly fine with analytics disabled.

Q: Can you read my blurs?

A: No. DataBlur:

  • Stores blur data only on your device (not uploaded)
  • Never sends blur content to any server
  • Never has access to your screen
  • Only tracks that a blur was created, not what was blurred

Q: How do I delete my analytics history?

A: Do the following:

  1. Disable analytics in extension popup (stops new collection)
  2. Request deletion from PostHog: support@datablur.app
  3. Uninstall extension (deletes local data)

Your analytics history will be deleted within 90 days (PostHog retention period).

Q: Is my data encrypted in transit?

A: Yes. All communication with PostHog uses HTTPS encryption.

Q: Can you identify me from my user ID?

A: No. Your user ID is:

  • Generated randomly
  • Stored only on your device
  • Not linked to your email, name, or browser account
  • Unique to this extension installation

Q: What if I change browsers or devices?

A: You’ll get a new user ID on each device/browser. Analytics treats them as separate users (which you are, from a product perspective). We have no way to link them together.

Q: Do you track what PII categories I enable/disable?

A: Yes, but only the category names (e.g., “email”, “phone”), not the actual content. We track:

  • Yes: Which category you toggled (e.g., “email”)
  • Yes: Whether you enabled or disabled it

We DO NOT track:

  • No: Which emails/phones were detected
  • No: Your actual email address or phone number
  • No: What page you were on
  • No: What content was blurred

This helps us understand which detection types are most useful so we can improve them.

Q: Do you use my data for advertising?

A: No. DataBlur:

  • Never sells data to advertisers
  • Never uses data for targeted advertising
  • Only uses data to improve the extension
  • Has no business model based on data monetization

Summary

What’s collected?

Feature usage metrics (if analytics is enabled) – which blur tools you use, auto-detection adoption, PII category preferences (which detection types you enable/disable), and error tracking for stability.

 

Is it opt-in?

Analytics is enabled by default, but you can disable it anytime using the toggle switch in the extension popup.


Can I turn it off?

Yes. Simply click the DataBlur extension icon and toggle “Help improve DataBlur” OFF. Your choice is saved immediately.

 

Is my blur data collected?

No, never. We only track that a blur was created, not what you blurred. Your blur content stays private on your device.

 

Can I be identified?

No. You’re identified only by a pseudonymous user ID generated locally on your device. We cannot link this ID to your real identity.

 

Is data encrypted?

Yes. All communication with PostHog uses HTTPS encryption in transit.

 

Who sees my data?

Only PostHog (if analytics is enabled). We never share your data with third parties.

 

How long is data kept?

Analytics events are retained for 90 days maximum (PostHog’s default). After that, data is automatically deleted.

 

Can I request deletion?

Yes. Contact support@datablur.app with your user ID, and we can request deletion of your analytics history from PostHog.


Do you sell my data?

No, never. DataBlur has no business model based on selling user data. We only use analytics to improve the extension.

 

Your privacy matters to us.

If you have any questions, please contact support@datablur.app