BREACHGUARD
privacy policy
Last updated · October 2, 2026 · Effective October 2, 2026
Privacy Policy
Product: BreachGuard browser extension (Manifest V3). This page describes limited technical install and environment data used for bot resistance and verification of real installations.
1. Overview
BreachGuard is a browser extension. To keep the product reliable and to reduce abuse, we collect a limited set of technical install and environment data so we can tell automated or fake clients apart from genuine browser installs.
That is the purpose of the collection described in this policy: bot and abuse resistance, and verification of real installations.
We do not sell this data for advertising and we do not use it to build marketing profiles.
2. Who we are
BreachGuard is provided by the BreachGuard developers (“we,” “us”). For privacy questions, use the contact details in Section 8.
3. Data we collect
3.1 Why
We process technical signals so that:
- Traffic and registrations that look like bots, scripted clients, or forged environments can be filtered or deprioritized
- Legitimate extension installs in real browsers can be recognized and treated accordingly
- The service can apply basic abuse controls (for example rate limits and anomaly handling)
3.2 What we send
The extension transmits to BreachGuard-operated servers over HTTPS, as a JSON body, roughly:
| Field | Description |
|---|---|
Install identifier (subject) |
An opaque, per-install identifier created on the device and stored in extension storage (IndexedDB). It is not the client’s name, email, or Google account ID. |
| Client timestamp | Time on the device when the body was built (Unix time). |
| Environment fingerprint | A flat map of technical attributes listed below. |
3.3 Environment fingerprint
Attributes are read on-device from the extension runtime and standard browser APIs. If an API is unavailable, that field is omitted.
Runtime
| Key | Meaning |
|---|---|
platform | OS family reported by the extension runtime |
arch | CPU architecture reported by the runtime |
go_version | Runtime/toolchain version string of the shipped component |
timestamp | Unix time in seconds |
ts_milli | Unix time in milliseconds |
version | Protocol/schema version label of this component |
Browser
| Key | Meaning |
|---|---|
user_agent | Browser user-agent string |
navigator_platform | Platform string from the browser |
language | Primary language |
languages | Preferred language list |
Locale and display
| Key | Meaning |
|---|---|
timezone | IANA time zone from the browser |
screen_width / screen_height | Screen size in CSS pixels |
color_depth | Screen color depth |
device_pixel_ratio | Display density ratio |
Extension identity
| Key | Meaning |
|---|---|
extension_id | Chrome extension ID for this install |
install_id | Random per-install value (from the browser CSPRNG), stored locally so the same install can be recognized after the background worker restarts |
3.4 What servers also see
- IP address of the request
- Ordinary TLS/HTTP metadata (for example time of request)
We may store install identifier, IP, fingerprint, and first/last seen times as needed for bot filtering and install verification.
3.5 Data kept on the device
Related local values (install identifier, install_id, and minimal state needed for continuity)
may remain in extension storage until you clear extension data or uninstall.
5. Retention
- On the device: until you clear BreachGuard’s extension storage or uninstall.
- On our systems: install identifier, IP, fingerprint, and related registration metadata are retained for 3 days, then deleted.
6. Security
- Transmission uses HTTPS.
- Install identifiers we generate are opaque (random or non-human-readable).
- Collection is limited to the technical fields described above.
7. Your choices
- Uninstall BreachGuard to stop this collection from that browser profile and to remove local extension storage (as the browser implements).
- Clear extension data for BreachGuard in browser settings to remove local identifiers (a new install identifier may be created if you install again).
8. Contact
- Privacy questions: [email protected]
- Security reports: [email protected]
9. Changes
If the fingerprint fields, purposes, or retention for this collection change, we will update this policy and the “Last updated” date.