Chrome extension privacy.

1. Scope

SeriousPixel, LLC operates Obsecurea. This notice covers the Obsecurea Chrome extension and its connection to your Obsecurea account. The main Privacy Notice covers the public website and account platform and also applies to extension users. The extension works within the Chrome profile where it is installed; its popup shows whether Image Shield is active.

2. Checks on your device

When Image Filtering is on in a build with Image Shield, the extension reads supported images in web pages and runs bundled detection models in the browser. It may fetch an image from the website or image host to decode it. Those requests go to the image host as ordinary network requests; Obsecurea does not receive or keep the image bytes. The extension does not send each image URL or visited site to our platform for a verdict.

When Hide explicit language is on, the extension checks visible page text locally and masks matching words. It does not send that page text to Obsecurea. When Block ads is on, Chrome applies a bundled list of network blocking rules locally. The extension does not send ad requests to Obsecurea. Google Images filtering may add a SafeSearch parameter to supported search URLs while image results are checked.

3. Account and exceptions

Connecting the extension sends authorization and device-registration information to app.obsecurea.com so we can verify your account, license, and available device seats. The platform stores your account information, license, registered installation, and revocable app session. It stores a public installation key and token hashes rather than your private installation key or plain refresh token.

If you deliberately choose “Always allow this image,” the platform stores the page origin and exact image URL you approved. “Allow all images on this site” stores that site origin and mode. These saved exceptions sync to your connected clients as a versioned policy. We do not turn ordinary browsing into an account activity history. PIN checks are sent over HTTPS for protected actions; we store a salted PIN verifier and failed-attempt/lockout state, not the PIN itself.

4. Browser storage and retention

The extension keeps its connection credentials, signed license status, saved policy snapshot, and switch preferences in extension-controlled browser storage. Its private installation signing key is kept in the browser's IndexedDB as a non-exportable key. The local image-scoring cache does not store raw pixels. Signing out clears the extension session and local policy; uninstalling the extension removes its browser storage. Saved account exceptions remain until you remove them or the account is permanently deleted.

The platform keeps account and license records while your account exists, including inactive accounts during their recovery period. Its account deletion and recovery process is explained in account help. Browser and hosting providers may process technical requests needed to deliver pages and APIs under their own policies.

5. Service providers and sharing

We use hosting and database services to operate the account platform and Resend to send account, license, and support email. We do not sell browsing activity or checked images. We disclose information to service providers only as needed to run these services, or when required by law. Websites and image hosts still see requests your browser makes to load their content.

Obsecurea's use and transfer of information received from Google APIs complies with the Chrome Web Store User Data Policy, including its Limited Use requirements. We use extension data only to provide or improve Obsecurea's visible protection and account features. We do not use it for personalized advertising, credit decisions, or sale to data brokers, and people do not read page content processed by the extension.

6. Your choices

The extension's Image Filtering, Block ads, and Hide explicit language switches are on by default. Changing them requires a connected account and adult PIN. You can review and remove saved image exceptions and Site filtering rules in your account, sign out a device session, or request account deactivation. A Chrome administrator may also control whether an extension can be installed or removed in a managed browser.

7. Changes and contact

We will update this notice if the extension's data handling changes and revise the effective date above. For privacy questions, email [email protected].