Review and change your choice
- Open the extension popup, select Open settings, and find Usage and performance analytics.
- Review the fields, retention, and Google explanation, then select Allow usage analytics or Decline usage analytics.
- Return later to revoke or grant consent.
Usage events require consent
Only while consent is active, eligible install, update, and feature-use events use the persistent pseudonymous Client ID and extension version. Feature-use events also include interface language, one fixed feature category, completed/cancelled/failed result, and a duration range. Earlier events are not queued or sent later.
Performance outliers in every state
Initial formatting or a major action taking at least 500 ms may send poor_performance with the extension version, fixed feature and file-type categories, duration rounded to 50 ms, and a new identifier for that event. The identifier is not stored, reused, or linked to the persistent Client ID.
Never sent
URL, domain, origin, path, query, fragment, title, filename, document, output, document or file size, search text, JSON path, key, value, error details, stack, name, account, advertising identifier, and user_id are excluded.
Google processes connection data such as the source IP address and browser-provided request headers, and may derive approximate location or device information. The extension does not send coordinates, user_location, ip_override, or device in the request body.
Storage, retention, and revocation
- The persistent Client ID is generated on install, or on update when missing, and retained locally regardless of consent. User-level and event-level retention is two months, excluding standard aggregated reports.
- There is no offline queue or automatic retry for failed sends.
- A saved revocation keeps the local ID and stops future usage events, but isolated performance outliers continue and previously sent data is not deleted automatically.
- Settings show the persistent ID and deletion-request support link in every consent state. Event-specific performance identifiers are not stored and cannot be identified by that persistent ID.
- If revocation cannot be saved, the current service-worker session blocks new usage sends and asks you to retry; that block is not guaranteed after a worker or browser restart.