Privacy policy

1. Information processed in your browser

AgentGuard uses browser APIs and limited on-page sensors to assess automation signals, explain detection coverage, maintain local reports, and apply the tab controls and policies you or your administrator select. Activity timing and counts provide context; they do not independently establish automation or identify a person.

Depending on the enabled features, local information can include:

• Domains and local identifiers: canonical hostnames, tab IDs, debugger target IDs and types, and local session or record identifiers.
• Observations: fixed evidence labels and descriptions, framework-like markers, heuristic scores, coverage states, timestamps, bounded interaction counts, and session timelines.
• Settings and control outcomes: sensitive-domain lists, configuration, delegation and pause state, alert mutes, quarantine or release results, and aggregate monitoring statistics.
• Optional traffic and download metadata: hostnames, timestamps, local request or download identifiers, fixed HTTP methods, response status codes, and observation or cancellation outcomes. These observations are tab-wide or browser-wide as described in the controls, not proof that an agent caused a request.

AgentGuard stores data in extension-local or browser-session storage and memory. It does not use Chrome sync storage to synchronize these records. No AgentGuard account is required for core features.

Information AgentGuard does not record

AgentGuard does not collect page text or HTML, page screenshots, form values, passwords, authentication tokens, cookies, request or response headers or bodies, key values, selectors, or pointer coordinates. It does not persist complete URLs, URL paths, queries or fragments, tab titles, or favicons.

Chrome APIs may supply URLs and other metadata while an operation is being handled. AgentGuard reduces these to the allowed fields, such as a hostname, instead of saving the full URL. The optional site-declaration check described below retrieves a specific public declaration file, not the contents of the page you are viewing.

2. Optional external services

External integrations are disabled by default. There is no built-in public collection endpoint or bundled remote analytics service. The following requests require explicit enablement and a user action; some also require a configured HTTPS service:

• Framework lookup: sends a fixed framework label, such as playwright, puppeteer, selenium, or webdriver, to the approved service configured by you or your administrator. It does not send domains, URLs, or raw detection evidence.
• Site declarations: fetches /.well-known/ai-safety.txt from the selected current HTTPS site's origin. Only three fixed boolean claims are retained in memory. The destination site receives a request from your network; its declaration is self-asserted, not a safety certification.
• Aggregate contribution: after you enable and configure this feature and confirm each submission, sends bounded counts of observed sessions, confirmed containments, and fixed framework categories. The payload contains no hostnames, full URLs, tab, session or installation identifiers, timestamps, inputs, credentials, or raw evidence.

These requests omit cookies, authentication headers, and referrers, reject redirects, and use HTTPS with response-size and timeout limits. Receiving services can still see your IP address and ordinary connection metadata; contributions are not guaranteed anonymous. Those services handle received information under their own policies. AgentGuard does not control their retention or deletion practices.

Installing the extension, ordinary monitoring, and opening its settings do not automatically send integration requests. Core monitoring does not depend on using these services.

3. Retention, exports and deletion

Local records are bounded. The default settings for version 1.0.0 are:

Audit and session retention can be changed within bounded limits, unless managed by your organization. Pruning occurs while the extension operates; expiry is not a promise of deletion at an exact clock time when Chrome or the extension is not running. Preferences and cumulative summary statistics are not automatically erased by audit or session-history expiry.

You can use the settings controls to clear the audit log, ended session history, and optional traffic or download records. Clearing ended history does not stop current monitoring or erase every other record. Continued monitoring can create new records. You can disable monitoring and optional features, manage Chrome site access and optional permissions, or uninstall the extension to remove its extension-managed local storage, subject to managed-browser restrictions.

Audit and session exports require an explicit user action. Exported files are outside the extension's retention controls. You are responsible for storing, sharing, and deleting those copies, including copies in backups or third-party systems.

4. How information is used and shared

Information is used to deliver AgentGuard's disclosed browser-monitoring, explanation, reporting, policy, and control features. Orenthic does not automatically receive your local observation records. Sharing occurs only through the optional requests or exports described above, or when you choose to contact us and provide information.

We do not sell or transfer user data except for uses permitted by the Chrome Web Store policies, use or transfer it for purposes unrelated to AgentGuard's single purpose, or use it to determine creditworthiness or for lending. We do not use extension data for advertising or advertising profiles.

AgentGuard's use of information received from Google APIs follows the Chrome Web Store User Data Policy, including its Limited Use requirements.

If you email us, we receive your email address, message, and any information you choose to include. We use it to handle your request and retain correspondence as reasonably needed for that purpose and applicable obligations. Please do not send credentials, page contents, or sensitive exported logs unless necessary and agreed.

5. Organization-managed browsers

Individual and organization-managed installations use the same extension. Your administrator can apply managed settings, set local retention, restrict controls, or configure approved optional services. Managed policy can override your local choices. Any separately deployed organizational backend, exported records, or administrator access to your browser profile is governed by your organization's arrangements and privacy policies. Contact your administrator about those practices.

6. Visiting this privacy-policy website

This static page is hosted using Google Firebase Hosting. It has no analytics scripts, tracking pixels, advertising, forms, embedded Firebase SDK, or application cookies. Hosting this page does not upload your extension observations to Firebase.

Firebase receives network information when serving the page. Google states that Firebase Hosting processes incoming IP addresses for abuse prevention and usage analysis and retains IP data for a few months. See Privacy and Security in Firebase and Google's Privacy Policy for provider information. Following an external link or sending an email is subject to the destination provider's practices.

7. Security and policy changes

AgentGuard minimizes stored fields, bounds records, restricts privileged extension messages, and uses HTTPS for optional external requests. Local records are not cryptographically tamper-evident, and no method of storage or transmission is completely secure. People or software with access to your browser profile may be able to access local records. A detection score, green icon, or quarantine action is not a guarantee of safety or controller identity.

We may update this policy when the extension or its data practices change. The current version will be available at this URL with an updated effective date. This policy describes version 1.0.0; an organization's additional practices remain subject to its own disclosures.