Close Menu

    Subscribe to Updates

    Get the latest creative news from FooBar about art, design and business.

    What's Hot

    Best VPN for Kazakhstan: Access Global Content in 2024

    February 15, 2024

    Best VPN for Egypt 2024: Get Egyptian IP for Free

    January 19, 2024

    A Comprehensive Guide to Setting Up VPN on Huawei Devices

    January 19, 2024
    Facebook X (Twitter) Instagram
    The Cyber Jury
    • VPN
      • VPN Comparison
      • VPN Reviews
    • Hosting
      • Hosting Reviews
    • Password Manager
      • Password Manager Reviews
    • Lab
      • Researches
      • Vulnerabilities
    • Tools
      • IP Look UP
      • Password Generator
      • Personal Data Breach
    • Updates
    Facebook X (Twitter) Instagram
    The Cyber Jury
    Home » Privacy Policy – BrowserSentry

    Privacy Policy – BrowserSentry

    This Privacy Policy explains how the BrowserSentry – Web Security & Protection Chrome extension (“BrowserSentry”, “the extension”, “we”, “us”, or “our”) handles information when you install and use it. BrowserSentry blocks dangerous websites, scans downloads, reviews installed extensions, protects your search provider, blocks ads and trackers, warns you about scam pages, and lets you check whether an email address appears in known data breaches.

    1. Information Processed Locally on Your Device

    To protect you, BrowserSentry needs to see certain information as you browse. This information is processed in your browser and stored in your local Chrome profile. It is not sent to us.

    • Web addresses (URLs) of pages you open: checked against threat lists, your custom blocklist and keyword rules, and the optional adult-content filter before the page loads. Also used to keep searches on your chosen search engine. Blocked sites and search corrections are logged locally in your Threat Activity history.
    • Page title and visible text: scanned for scam and scareware language (for example, “your computer is infected”) so a warning banner can be shown. This is read in memory only and is never stored or transmitted.
    • Download details (file name, type, source URL): used to decide whether a download should be scanned, paused, or allowed. Scan results are kept in your local download history.
    • List of installed extensions (names, IDs, permissions): compared against lists of known malicious extensions. Stored locally.
    • Your settings and custom rules: your preferred search engine, blocked domains, keyword rules, custom scam phrases, trusted extensions, and feature toggles. Stored locally.
    • Security activity and statistics: a history of blocked sites, download verdicts, search corrections, breach scans, and extension actions, plus the daily counts shown on your dashboard. Capped at 500 events. Daily statistics are kept for 62 days. Live counters reset when the browser restarts.
    • In-extension usage records: which BrowserSentry screens you open and which buttons you click inside the extension, with a random device ID and session ID (plus your account ID and email if you are signed in). Stored locally and capped at 2,000 records. See Section 3.
    • API keys you enter (VirusTotal, LeakCheck): stored only in your local Chrome profile and used to call those services for you. They are never sent to us.

    2. Information Shared with Third-Party Services

    Some features need to contact an outside service. Here is every external service the extension connects to, what is sent, and when.

    • VirusTotal: the URL of a download and, for files up to 32 MB, a SHA-256 hash (a digital fingerprint) of the file. If VirusTotal does not recognize the hash, the file itself may be uploaded for analysis. VirusTotal may share uploaded files with its security community under its own terms. When: only if you add your own VirusTotal API key and the download is in a file category you chose to scan.
    • LeakCheck: the email address you type into the Identity & Dark Web panel, plus your LeakCheck API key if you added one. When: only when you start a breach scan. Passwords, password hashes, and IP addresses in LeakCheck’s results are removed before anything is shown or saved.
    • Google Firebase Authentication: your email address and password (email sign-in) or your Google account identity (Google sign-in). Firebase creates an account ID and a sign-in session. When: only if you create an account or sign in. Signing in is optional, and all protection features work without an account.
    • Google Sign-In: a request for a Google sign-in token, which shares your basic Google profile (name and email) with Firebase. When: only if you choose “Sign in with Google”.
    • Chrome Web Store: the ID of an installed extension, used to fetch public details such as developer, version, and install count. No cookies are sent. When: during extension review.
    • The Block List Project, Malicious Extension Sentry, and ExtSentry (hosted on GitHub): a standard download request for public lists of threats, ads, trackers, adult content, and malicious extensions. No personal data or browsing data is included. When: automatically every 6 hours for site, ad, and tracker lists, every 24 hours for extension lists, or whenever you tap “Sync now”.

    Like any web request, these connections reveal your IP address and basic browser details to the service you contact. Each service handles that data under its own privacy policy:

    • VirusTotal: https://docs.virustotal.com/docs/privacy-policy
    • LeakCheck: https://leakcheck.io/privacy
    • Google / Firebase: https://policies.google.com/privacy
    • GitHub: https://docs.github.com/site-policy/privacy-policies/github-general-privacy-statement

    3. Usage Records and Diagnostics

    BrowserSentry keeps a local record of how its own screens are used (for example, “opened the Downloads panel” or “clicked Sync now”), along with copies of security events. This feature does not record your activity on other websites.

    These records are stored on your device. The extension includes a diagnostics connector that can send them to an analytics server address set in Settings. By default, that address points to your own computer (localhost), so the records do not leave your device unless you change the address yourself. We do not collect these records.

    4. What We Do Not Do

    • We do not sell, rent, or trade your data.
    • We do not use or transfer your data for advertising, personalized ads, or credit decisions.
    • We do not send your browsing history, page content, or downloaded files to our own servers.
    • We do not read or store the passwords you type on websites.
    • No person reads your data, unless you ask us to (for example, for support), it is needed for security, or the law requires it.

    5. Chrome Web Store Limited Use Disclosure

    BrowserSentry’s use of information received from Chrome APIs follows the Chrome Web Store User Data Policy, including the Limited Use requirements. We use data only to provide and improve the extension’s single purpose, which is protecting your browser against security and privacy threats. We do not transfer it for any other purpose.

    6. Browser Permissions and Why They Are Needed

    • Access to all websites (<all_urls>): check pages for threats and scam language, block pop-ups, and fetch threat lists and download URLs for scanning.
    • webNavigation, tabs: stop dangerous pages before they load, show the warning page, and correct search redirects.
    • declarativeNetRequest, declarativeNetRequestFeedback: block ad and tracker requests at the network level and count how many were blocked.
    • downloads: pause, scan, resume, or cancel downloads.
    • management: list installed extensions and let you disable or remove harmful ones.
    • privacy: turn third-party cookie blocking and “Do Not Track” on or off when you ask.
    • scripting: run the YouTube ad blocker on YouTube pages.
    • storage, unlimitedStorage: save settings, threat lists, and history on your device.
    • alarms: schedule threat-list updates and extension rescans.
    • notifications: alert you about blocked downloads and security events.
    • identity: support optional Google sign-in.

    7. Data Retention and Deletion

    • Local data stays on your device until you delete it. You can remove custom rules, trusted extensions, and API keys from the dashboard at any time.
    • Security history is capped at 500 events, daily statistics at 62 days, and usage records at 2,000 entries. Older entries are removed automatically.
    • Uninstalling BrowserSentry removes all of its locally stored data from your Chrome profile.
    • Your account: to delete an account created through sign-in, email us at [contact email] and we will delete it.
    • Third-party data: anything sent to VirusTotal or LeakCheck is kept under their own retention policies. Contact those services directly to request deletion.

    8. Security

    BrowserSentry runs under Chrome’s Manifest V3 security model, loads no remote code, and connects only to the services listed in this policy, over encrypted connections (HTTPS). Account sign-in is handled by Google Firebase. No method of storage or transmission is fully secure, but we work to protect your information and keep the amount of data we handle as small as possible.

    9. Your Rights

    Depending on where you live, including under the EU/UK GDPR and California privacy laws (CCPA/CPRA), you may have the right to access, correct, delete, or move your personal data, to object to or limit how it is used, and to withdraw consent. Because most BrowserSentry data never leaves your device, you control it directly. For account data or any other request, contact us at the email below. We will not treat you differently for using these rights.

    Where the GDPR applies, we rely on your consent for optional features (sign-in, VirusTotal scanning, and breach checks) and on our legitimate interest in providing the security features you installed the extension for.

    10. Children’s Privacy

    BrowserSentry is not directed at children under 13, or under the minimum age required in your country. We do not knowingly collect personal information from children. If you believe a child has created an account, contact us and we will delete it.

    11. Open-Source Data Sources

    Threat intelligence comes from open-source projects, including The Block List Project (github.com/blocklistproject/Lists), Malicious Extension Sentry (github.com/toborrm9/malicious_extension_sentry), and ExtSentry. These are one-way downloads, and BrowserSentry sends no information about you to these projects.

    12. Changes to This Policy

    We may update this policy when the extension changes. When we do, we will update the “Last updated” date above. For significant changes, we will tell you through the extension or its Chrome Web Store listing before the change takes effect.

    13. Contact Us

    If you have questions about this Privacy Policy or want to make a privacy request, email us at:

    info@thecyberjury.com

    Editors Picks

    Best VPN for Kazakhstan: Access Global Content in 2024

    February 15, 2024

    Best VPN for Egypt 2024: Get Egyptian IP for Free

    January 19, 2024

    A Comprehensive Guide to Setting Up VPN on Huawei Devices

    January 19, 2024

    Detailed setup Guide for Samsung VPN

    January 18, 2024
    Advertisement
    THE CYBERJURY
    Building lightweight, privacy-first Chrome extensions designed to enhance productivity, clarity, and control while browsing.
    Products
    • Unbiased News
    • PopDocs
    • LingoTranslate
    • Commit
    • Where to Watch
    • OpenClaw Relay
    Company
    • About Us
    • Contact
    • Support
    • Privacy Policy
    • Terms of Service
    Resources
    • Blog
    • Chrome Web Store
    • Documentation
    • Release Notes
    © 2026 The Cyber Jury Labs. All rights reserved.

    Type above and press Enter to search. Press Esc to cancel.