Terms Agent

Privacy & Support

Effective August 24, 2026 · Policy version 0.8.2

Plain-language summary: policy analysis and initial receipt saving remain local. Development build 0.8.2 sends receipt data only when the user separately presses Sync signed receipt for the registered test provider.

What Terms Agent does

Terms Agent helps people assess Terms of Service, privacy policies, cookie notices, and related agreements before recording their own decision.

Information the extension handles

When the user clicks the extension, Terms Agent temporarily reads website content and the page address in that active tab so it can identify potentially important clauses, link findings to their source text, and locate related policies. This processing occurs locally on the user’s device; Terms Agent does not persistently access every website.

When a user records a decision, Terms Agent stores a local Trust Receipt using Chrome’s local extension storage. A receipt may contain the website domain and policy address, policy title and effective date, the user’s Agree or Disagree decision, detected threat categories, source excerpts, a hash of the assessed policy text, the analyzer version, and the time of the decision. The extension also stores local appearance preferences, per-domain Terms and Privacy preferences, provider-declared purpose choices, and the time and app version when the user completes the onboarding guide.

How information is used

The information is used only to provide the extension’s policy-assessment, source-linking, theme, and Trust Receipt features. Terms Agent does not use browsing activity or website content for advertising, profiling, creditworthiness, or unrelated purposes.

Optional signed receipt sync

Policy analysis and the initial Trust Receipt save remain local. Development build 0.8.2 offers a separate, optional Sync signed receipt action only for a registered test provider. Nothing is transmitted merely because the user records Agree or Disagree.

A signed receipt sync sends the selected decision, registered manifest ID, and receipt evidence to the Terms Agent staging API only after the user presses Sync signed receipt. Receipt evidence may contain the policy-text hash, analyzer version, detected threat categories, and source excerpts already shown in the local receipt. The staging API uses the user’s Clerk account token to authenticate the request, derives a provider-specific pseudonymous subject, stores and signs the receipt, and returns receipt and verification identifiers. Clerk processes authentication data and Cloudflare operates the staging API and storage. Terms Agent does not sell this data or use it for advertising, profiling, creditworthiness, or unrelated purposes.

Storage and deletion

Information is stored in Chrome’s local extension storage on the user’s device. Users can delete individual local Trust Receipts from the Trust Receipts page or delete all local receipts from Settings. Removing the extension through Chrome also removes local extension storage according to Chrome’s behavior. Local deletion does not alter a synced staging receipt.

Settings provides separate authenticated controls to count synced receipts, withdraw an individual synced receipt recorded on this device, or permanently erase this account’s receipts for the registered staging provider. These requests send the registered provider ID or receipt ID and, for erasure, a settings-request reason to the staging API. Withdrawal preserves a server record in withdrawn state; erasure permanently deletes the matching staging receipts. These actions do not delete local records unless the user separately uses a local deletion control.

Permissions

Terms Agent uses activeTab and scripting to temporarily assess the current page and highlight exact source passages only after the user clicks the extension. It uses storage for local preferences and Trust Receipts and identity to open the user-initiated Clerk login flow. It does not request persistent access to every website or access to payment information, contacts, or files.

Security

Terms Agent minimizes stored information, keeps policy analysis local, uses encrypted HTTPS transport for explicit sync, and keeps authentication tokens in browser session storage. No security method can guarantee absolute protection.

Changes

If a future release introduces external data transmission or materially different data practices, this policy and the Chrome Web Store disclosures will be updated before that functionality is released, and any required user notice or consent will be provided.

Support

Questions, bug reports, and privacy requests may be sent through the support contact provided on the Terms Agent Chrome Web Store listing.

Chrome Web Store Limited Use

The use of information received from Chrome APIs adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements.