Skip to main content
Privacy

Privacy policy.

What stays on your device, what reaches our systems, and the choices you control.

Last updated August 24, 2026

This policy explains how Safe Screen Share, a company registered in Bangladesh with a contact location in Dhaka ("we", "us", or "our"), handles personal data when you use the Safe Screen Share browser extension, website, licensing service, checkout, support, and related services (together, the "Services").

1. The short version

  • Screen content, detected text, blur rules, profiles, and AI analysis stay in your browser. We do not receive or store them.
  • Extension analytics are off by default. If you opt in, we receive a random analytics ID and a limited set of feature and reliability events, never the page you were viewing or the content you blurred.
  • We receive the data needed to sell, activate, recover, and support a license, and to operate and understand our website.
  • We do not sell personal data or share it for cross-context behavioral advertising.

2. Data that stays on your device

The extension processes the page currently open in your browser so it can apply element, area, text, SmartBlur, AI Redact, profile, Meeting Mode, and tab-title protections. Depending on what you save, local extension storage may contain full page URLs, selectors, element descriptors, selected text, coordinates, profile names, blur rules, settings, and license information. Chrome manages this local storage. We do not sync it to our servers.

AI Redact runs only when you ask it to. The first use downloads roughly 463 MB of model and tokenizer files from Hugging Face. The model is cached and run locally. Page text is not sent to us or Hugging Face. Hugging Face receives ordinary file-download request data, such as your IP address and user agent. You can delete the model from the extension.

Diagnostic reports are generated locally and remove URLs, email addresses, and long token-like values. They leave your device only if you choose to send one to support. Review a report before sharing it.

3. Data sent by the extension

License activation and recovery

Activating a paid license sends the license key and a random browser ID to our licensing API. We store the browser ID and activation date with the license so we can validate entitlements and enforce the active browser limit. The browser ID is not a hardware fingerprint. License recovery sends the email address you enter.

Optional usage analytics

Extension analytics are off until you explicitly enable them. You can disable them at any time in the extension. When enabled, the extension sends:

  • a random analytics-only installation ID, extension version, browser family, operating-system family, and event time;
  • feature events, such as opening the popup, choosing a blur tool, running SmartBlur or AI Redact, changing a profile or Meeting Mode, managing the local AI model, viewing an upgrade prompt, starting checkout, or activating a purchase;
  • coarse values, such as the selected preset, action result, item count, or element category; and
  • allowlisted error codes and the extension context involved.

Analytics do not include URLs, domains, page content, selected text, selectors, blur coordinates, license keys, the license-linked browser ID, raw error messages, or stack traces. The analytics ID is persistent and therefore pseudonymous, but it is separate from licensing IDs and is not designed to identify you directly.

After analytics consent, an install-attribution request may send the analytics ID, extension version, and ordinary request metadata. We use a short-lived hash of IP address and user agent to match a website click to an install. The matching intent expires after 30 minutes. A matched install record includes the analytics ID, timestamp, coarse browser family, IP hash, extension version, campaign data, and CTA location.

4. Website and service data

We may process the following:

  • Website requests: IP address, user agent, request time, requested path, security signals, and server logs handled by our hosting and network providers.
  • Cookie-free analytics: page views, referrer and campaign data, approximate location derived from IP, browser, device, operating system, CTA interactions, scroll depth, installs, and purchases. Our self-hosted Umami tracker respects Do Not Track and excludes URL search parameters. We also use Vercel Web Analytics for aggregate measurement.
  • Attribution: UTM fields, referring hostname, landing path, CTA location, and, after optional tools are allowed, a first-party attribution cookie lasting up to one year. We store a hashed IP address and user-agent match for up to 30 minutes when you click an install CTA.
  • Regional offers: After optional tools are allowed, Evendeals receives the page URL and ordinary request data to determine country-level eligibility and show a regional discount. Its script may use local or session storage for banner dismissal and offer timers.
  • Purchases and redemptions: name, email, customer and order IDs, product, amount, currency, source, campaign data, license key, redemption code, purchase mode, and active browser records. We do not receive full payment-card details.
  • Support: your contact details, messages, attachments, chat metadata, and any diagnostic report you choose to send.

Crisp chat and YouTube embeds load only after optional tools are allowed. The Better Stack status badge loads on website pages and may receive IP address, device, and request data. YouTube and Crisp receive request or session data when they are enabled or used.

5. Why we use data

We use data to:

  • provide, secure, troubleshoot, and maintain the Services;
  • fulfill purchases, issue licenses, and manage active browsers;
  • respond to support, privacy, and refund requests;
  • measure acquisition, feature use, reliability, and conversion;
  • prevent abuse, fraud, duplicate redemptions, and security incidents;
  • comply with tax, accounting, legal, and contractual duties; and
  • establish, exercise, or defend legal claims.

Where applicable law requires a legal basis, we rely on performance of a contract for purchases and licensing; consent for optional extension analytics and any non-essential storage that requires it; legitimate interests in operating, securing, supporting, and improving the Services; and legal obligations for required records and disclosures.

6. When we disclose data

We disclose data to providers that host, secure, measure, support, and deliver the Services; to payment and marketplace partners that fulfill your purchase; when you direct us to; when required by law; or when reasonably necessary to protect rights, safety, and service integrity. We may transfer data in a merger, financing, acquisition, reorganization, or sale of assets, subject to applicable law.

Our current providers and their roles are listed on the Service Providers and Subprocessors page. Some providers act as our processors. Others, including checkout providers and marketplaces, may act as independent controllers under their own privacy notices.

7. International transfers

We operate from Bangladesh and use providers in the European Union, United States, and other countries. Your data may therefore be processed outside your country. Where required, we rely on contractual safeguards, adequacy decisions, or other lawful transfer mechanisms offered by our providers.

8. Retention

  • Local extension data remains until you clear it or uninstall.
  • Install-matching intents expire after 30 minutes.
  • Pending extension purchase links expire after 24 hours.
  • The first-party attribution cookie expires after up to one year.
  • Purchase, license, activation, redemption, support, and analytics data is retained while needed to provide the Services, maintain records, prevent fraud, resolve disputes, and meet legal obligations.

When data is no longer needed, we delete or anonymize it where reasonably practicable. Backups and provider logs may remain for a limited period before deletion cycles complete.

9. Security

We use safeguards appropriate to the data we handle, including HTTPS, access controls, limited analytics fields, hashing for short-lived matching, and provider security controls. No system is completely secure. Keep your license key private and do not send card details or secrets to support.

10. Your choices and rights

You can:

  • decline or disable optional extension analytics;
  • enable Do Not Track for the website analytics tracker;
  • clear local extension data or delete the local AI model;
  • remove active browsers through license management;
  • delete first-party cookies or site storage in your browser;
  • uninstall the extension; and
  • request access, correction, deletion, restriction, portability, or an objection where your law provides those rights.

You may withdraw consent without affecting earlier lawful processing. You may also complain to your local data-protection authority. We may verify your identity and retain data where an exception applies, such as tax records, fraud prevention, or legal claims. We do not use personal data for automated decisions that produce legal or similarly significant effects.

11. Chrome Web Store data

Our use of information received from Chrome APIs follows the Chrome Web Store User Data Policy, including its Limited Use requirements. We use extension data only to provide or improve the extension's disclosed, user-facing screen-privacy purpose and related reliability and security.

12. Children

The Services are not directed to children under 13, and we do not knowingly collect their personal data. A minor who can use the Services only with parental consent under local law must have a parent or guardian approve the use and any purchase. Contact us if you believe a child has provided personal data without required consent.

13. Changes and contact

We may update this policy as the product, providers, or law changes. We will post the new version here and update the date above. If a change materially affects how we use data already collected, we will provide additional notice when required.

Safe Screen Share
Dhaka, Bangladesh
[email protected]