Browser extension
privacy policy.

1. Who we are and what this policy covers

The Zero AI browser extension is provided by Endgate System Technologies ("Zero AI," "we," "us," or "our"). This policy covers the extension version identified above and support inquiries about that extension.

The Zero AI workspace uses third-party technology, including HighLevel/LeadConnector, to provide business tools. The extension is a separate interface layer. Workspace records, account registration, subscription billing, payment processing, website hosting, and services you connect to your workspace have their own data flows and applicable privacy notices. This policy does not represent that those services operate without collecting or storing data.

Installing the extension does not change your underlying account permissions or disable third-party server-side services.

2. Information processed by the extension

Local processing means information is accessed or used on your device, even if it is not saved or sent to us. The extension performs the following processing to provide its interface functionality:

Temporary diagnostic markers on the page can expose extension version, installation, scan, theme, or guard status to that page's scripts. Certain local diagnostic reports contain technical counts, color values, or error types. The extension does not include scanned customer text in those reports or send them automatically to us.

3. Data minimization and sensitive information

The extension is not designed to collect customer records, financial records, medical information, or communications as datasets. V13 limits incidental processing in these ways:

• The generic AI scanner does not read form values through input-value properties or the value and data-value attributes.
• Generic text scanning skips input controls, tables and grids, editable regions, and identified editor, email-content, and chat-content containers, including those found inside a scanned parent element.
• Calendar AI detection uses known component selectors instead of reading the full page text.
• AI JavaScript scans are excluded from the identified Billing, My Profile, and Company settings routes across subaccounts, including the Payments and Wallet Transactions billing tabs. Route checks include the main tab and requesting frame; unverified routes are not authorized for scanning.

These are processing limits, not a guarantee that every personal or sensitive string can be recognized and excluded. Selected labels, links, metadata, sidebar entries, or an unrecognized component can contain names, identifiers, customer-entered text, or other personal information. If encountered, that information may be processed transiently as part of matching an interface rule. It is not used to build customer profiles or uploaded by the extension.

Styling, selector-only CSS rules, and the sidebar guard remain separate from the settings-page AI scan exclusions. Those features can still inspect interface structure, styles, or sidebar labels. The extension's browser permissions are not revoked when scanning is excluded.

Passwords, payment fields, and location

The extension does not ask you to provide passwords, payment-card numbers, security codes, medical details, or precise location. Its generic scanner excludes password inputs and other input controls, and it does not use browser cookie or geolocation APIs. Its installation handshake is not an account-login mechanism.

The extension does not inject into Stripe's js.stripe.com payment frames under its current permissions. Payment processors and the workspace handle payment entry separately. This does not imply that all financial information displayed elsewhere in a workspace is inaccessible to interface code.

The extension has no IP-address collection or location-tracking feature. Websites, your browser, extension-distribution services, and payment services may independently process connection information when you use them.

4. Why website access is needed

The extension's configured website access covers app.zeroaiworkspace.com, LeadConnector subdomains used for embedded business modules, and the businesswithoutai.com/workspace-login onboarding route. Some LeadConnector permissions cover a family of subdomains, not just one module.

This access allows the extension to apply interface rules inside separate module frames, maintain appearance, detect unexpected agency navigation, and verify installation. The local background component evaluates route information supplied by Chrome and returns an allowed-or-blocked result to the scanner; page text is not included in that request.

Permissions describe technical capability. The processing limits described in this policy describe how the current extension uses that capability.

5. Sharing, transmission, and limited use

The extension does not send scanned page content, customer records, or browsing-history logs to Endgate System Technologies, an analytics provider, an advertising network, or an AI service. It includes no remote analytics or customer-content upload feature. Installation status and version are communicated locally to the Zero AI onboarding page as described above; that page's own hosting and scripts are separate from the extension.

Our use of information obtained through the extension is limited to providing and maintaining its stated interface functionality. We adhere to the Chrome Web Store User Data Policy, including its Limited Use requirements.

• We do not sell extension user data or transfer it outside the uses permitted by that policy.
• We do not use or transfer extension user data for purposes unrelated to the extension's single purpose.
• We do not use or transfer extension user data to determine creditworthiness or for lending purposes.
• We do not use scanned interface information for advertising, cross-site profiling, or AI-model training.

Google and your browser provider operate extension installation, updates, and their own platform services under their respective policies. We may see aggregate installation or usage statistics provided by the Chrome Web Store developer dashboard. Those platform statistics are distinct from a customer-content upload feature in our extension.

6. Storage, retention, and your controls

V13 does not persist scanned page content in extension storage, local storage, cookies, or a developer database. It keeps working state in memory and applies temporary changes and markers to the page. This includes references to interface elements, theme settings for the current page, original styles, and technical diagnostics. The browser manages memory cleanup; we do not claim secure memory erasure.

You can disable or uninstall the extension through your browser's extension settings and manage website access where your browser allows it. After disabling or uninstalling, close or reload previously open workspace pages to clear injected page behavior and temporary state. Restricting access may prevent blocking, styling, or onboarding verification from working.

Disabling or uninstalling the extension does not delete your workspace account, records, subscription, or information held by third-party services. There is no extension-created archive of scanned customer content for us to retrieve or export.

7. Information you choose to send to support

If you email us, we receive your email address, message, and any attachments you choose to send. This is a separate, voluntary communication, not automatic collection by the extension. Please redact customer records, passwords, payment details, and other sensitive information before sharing screenshots or diagnostic material.

Support correspondence is handled by us and the email or support providers used to deliver and manage it, for responding to your request and maintaining appropriate support records. We retain it only as reasonably needed for those purposes or applicable legal obligations. Contact us to request access, correction, or deletion, subject to applicable law and necessary record retention.

8. Security and policy changes

The extension uses packaged executable code, validates its extension messages, and restricts scanning through route and content checks. These safeguards reduce risk but do not guarantee immunity from vulnerabilities, compromised devices, or unauthorized activity within an already-authorized session.

We do not claim that transient page text is encrypted by the extension. The extension does not create a stored repository of that text. Workspace transport security, payment processing, and server-side account authorization remain responsibilities of the relevant service providers.

We will update this policy when extension behavior or our handling practices change. Material changes will be communicated through appropriate product, listing, or website notices, and we will obtain consent where required. New data processing is not authorized merely by a general statement about possible future functionality.

9. Contact and privacy requests

Depending on your location and the circumstances, you may have rights to access, correct, delete, restrict, or object to processing of personal information, or to complain to a privacy regulator. Contact us to discuss a request. We cannot retrieve page content that the extension never transmitted to us.