TalkToAI ZSEC Browser Community 0.4
Menu

ZSEC Browser · ZSEC Browser Shields Community 0.4

Privacy should be a testable contract.

ZSEC Browser Shields evaluates packaged rules, the optional High-Risk Browsing profile and site-pause choices inside the browser. Community 0.4 has no analytics, advertising, account, crash-upload, cloud-reputation, spyware-verdict or remote-control endpoint.

Effective and last reviewed: . This policy's Community 0.4 statements apply to the website evaluation Manifest V3 extension. The separate ZSEC Browser Community 0.3.0 section documents an unsigned local build that is not included in the extension ZIP and is not offered as a public native download.

Processed locally

What the extension uses

  • Forty packaged declarative ad, tracker and link-cleaning rules.
  • The global protection on/off setting.
  • The user's High-Risk Browsing on/off choice.
  • Domain names the user explicitly pauses during normal protection.
  • Two browser-managed High-Risk request rules when that profile is active.
  • Page-interface signals used for best-effort YouTube cleanup.

These operations happen inside the browser. The current extension sends no report about them to TalkToAI. The High-Risk preference is one local setting; it is not a targeting assessment or infection verdict.

Not collected or transmitted

What we do not receive

  • Browsing history, full URLs, searches or page text.
  • Cookies, form fields, credentials or payment details.
  • Files, downloads or clipboard contents.
  • Advertising identifiers, analytics events or crash reports.
  • Affiliate-attribution replacements or shopping-link rewrites.
  • Which requests High-Risk Browsing blocked.
  • Whether the user enabled High-Risk Browsing.
  • Any inference that the user is being targeted.
  • A malicious, safe, infected or clean verdict for any site or device.

Permissions

Why broad site access exists

A network blocker must be able to evaluate requests across websites, and the interface-cleanup script must run on the sites it supports. That access is not permission to build a browsing profile or transmit page contents. The extension uses Manifest V3 packaged code and rules; it does not download or execute remote code.

High-Risk Browsing uses Chromium Manifest V3's declarativeNetRequest mechanism to apply two fixed local request rules. It does not decrypt TLS, inspect response bodies, upload full URLs, classify a request as spyware or produce a forensic request log. A blocked request means only that it matched one of the disclosed local rules.

The global protection choice, High-Risk Browsing choice and paused domains remain in the browser extension's local storage. Paused domains may remain stored while High-Risk Browsing is active, but the pause control cannot override the stricter rules. Removing the extension removes its local settings through the browser's normal extension lifecycle. Community 0.4 creates no ZSEC server-side account record to delete.

Windows Community client

A separate local profile, with no ZSEC telemetry.

ZSEC Browser Community 0.3.0 stores cookies, history, cache, permissions and other browser state under the user's dedicated LocalAppData\TalkToAI\ZSEC Browser profile. It does not reuse Chrome, Edge or Brave profiles and adds no ZSEC analytics, account, browsing-history upload or remote-control endpoint.

Microsoft runtime boundary

WebView2 and SmartScreen are not ZSEC services.

Microsoft's Evergreen WebView2 runtime supplies the engine and updates. WebView2 diagnostics and SmartScreen may send information to Microsoft under Microsoft's terms and Windows diagnostic settings; see Microsoft's WebView2 data and privacy documentation. The ZSEC developer build adds no ZSEC analytics, account, browsing-history upload or remote-control endpoint. It does not claim that all browser data is encrypted by ZMath or hidden from the engine provider.

Change control

No silent expansion.

Any future URL reputation, indicator feed, blocked-request reporting, diagnostics, content inspection, synchronisation or sample submission would materially change this privacy contract and requires a separately disclosed purpose, data set, destination, retention period and user control.

This policy describes data handling, not security efficacy. Local processing and no telemetry do not prove that a site or device is safe. Material policy changes require a new review date and release notes.

Security issues can be reported through the repository's security policy.

Return to ZSEC Browser