Browser Extension Privacy Policy
BringLive Guard processes browser-protection information locally on the user's device. This release does not transmit page content, browsing activity, personal communications or downloaded files to BringLive Digital.
1. Scope
This policy applies to the BringLive Guard Chrome/Chromium browser extension. It does not describe separate Windows, Android, website, support or future cloud services.
2. Information processed
BringLive Guard processes only information needed to provide its browser-protection features:
- Web browsing activity: the current page URL and domain, link and form destination URLs, pop-up target URLs and download source/final URLs. Guard does not create a complete general browsing-history profile; URLs are retained only when needed for settings or limited protection-event records.
- Website content: visible page text, action labels, overlay and advertisement markers, form field types/names/autocomplete hints, form destinations and page address patterns. This supports local ad, pop-up, subscription and credential-destination warnings.
- Personal communications: because protection can run on ordinary HTTP/HTTPS pages, Guard may encounter visible text on webmail or chat pages. It does not intentionally store raw email, chat or message content and does not use communications for an unrelated purpose.
- Limited user activity: recent pointer/click, form-submission, Enter or Space gestures and intended target URLs are processed briefly to distinguish user-initiated navigation from unwanted pop-ups and to warn before supported risky actions. Guard does not log typed text, pointer coordinates or general keystroke history.
- Download metadata: Chrome-provided filename, URL, state and danger classification. Guard may pause a supported high-risk download for review, but it does not read or upload downloaded file contents.
- Local preferences and records: feature settings, trusted and blocked domains, counters, a notification inbox and limited protection-event records.
3. Sensitive fields
Credential Shield checks whether a form contains password, payment or one-time-code field types and checks the page protocol and form destination. It does not read, store or transmit the values entered into password, card-number, PIN, CVV, security-code or OTP fields.
4. Purposes
The information above is used only to block supported advertising, tracking and intrusive page behavior; identify supported suspicious pop-ups or redirects; warn about supported subscription, credential-destination and download risks; remember user choices; display local counters and activity; and allow users to review or clear protection events.
5. Local storage and retention
Settings and records are stored in chrome.storage.local on the user's device. Raw page text, raw message content, entered field values and downloaded file contents are not stored. The extension keeps up to 300 limited activity records and up to 120 notification-centre entries. Recent gesture information is temporary and is cleared when the related tab closes or the extension background process restarts. Other local settings remain until the user changes or clears them or uninstalls the extension.
6. Transmission, sharing and sale
Version 2.6.3 contains no analytics SDK, advertising SDK, cloud page scanner or remotely hosted executable code. BringLive Digital does not receive extension browsing data in this release. It does not sell extension user data, use it for personalized advertising, or transfer it to data brokers or lenders.
Information may be provided to BringLive Digital only when a user deliberately sends information in a support request. Any disclosure required by law or necessary to investigate a security incident will be limited to what is legally and operationally necessary.
7. User controls
Users can pause protection, turn individual protection layers on or off, trust or block sites, clear local activity and notification entries, reset counters, remove site access in Chrome, or uninstall the extension. Uninstalling removes extension storage according to Chrome's behavior.
8. Security and limitations
BringLive Guard uses packaged Manifest V3 code and local browser APIs. No browser-protection product can guarantee detection of every advertisement, scam, malware file, unwanted pop-up or charge. Chrome, the operating system, the network operator and payment provider remain authoritative.
9. Changes
This policy will be updated before any material change such as analytics, account syncing, cloud scanning, remote threat feeds or new data transfers. The effective date and covered version will be revised when the policy changes.
10. Contact
BringLive Digital (Pty) Ltd
Pretoria, South Africa
Email: info@bringlivedigital.com
Website: https://www.bringlivedigital.com