Document processing
Format detection, parsing, formatting, search, conversion, and image inspection happen in the browser. The page URL and document are not sent to the developer or Google Analytics.
Stored locally
Theme, link preference, disabled HTTP(S) origins, analytics choice, and a pseudonymous UUIDv7 Client ID generated and retained regardless of consent are stored locally. A disabled origin contains only its scheme, host, and port. Full URLs and document content are not stored. A session-only one-shot token contains no URL or origin.
Consent-based usage analytics
Only while consent is active, eligible install, update, and feature-use events may be sent. They use a GA4 Client ID deterministically derived from the local UUIDv7 and include the extension version. Feature-use events also include the interface language, a fixed feature category, completed/cancelled/failed result, and a duration range. No usage events are sent while unanswered, declined, or revoked, and earlier events are not queued or sent later.
Performance outlier analytics
When initial formatting or a major action takes at least 500 ms, poor_performance may be sent in every consent state. It contains 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 or another event.
Purpose
Usage events help prioritise product improvements from consented install, update, feature, result, and duration-range counts. Performance outliers identify slow features and file types. Neither dataset is used for advertising, billing, access control, or decisions about individual users.
Never sent
URLs, domains, origins, paths, queries, fragments, referrers, titles, filenames, documents, keys, values, outputs, image content, document or file sizes, node counts, image dimensions, search text, JSON paths, conversion targets, error details, stacks, names, email addresses, accounts, advertising identifiers, and user_id are not sent.
Google processing
Events are sent directly to Google Analytics over HTTPS. Google processes connection data such as the source IP address and browser-provided request headers, and may derive approximate location or device information. This also applies when a performance outlier is sent after usage analytics are declined or revoked. The extension does not set coordinates, user_location, ip_override, or device in the request body. Granular location and device data collection, Google Signals, and advertising personalisation are disabled, and each request denies ad_user_data and ad_personalization consent.
Retention and delivery
Google Analytics user-level and event-level retention is two months; this does not cover standard aggregated reports. The extension does not store an offline queue, send history, or send errors, and it does not automatically retry failed events.
Consent, revocation, and deletion
A saved revocation keeps the persistent Client ID locally and stops future usage events, while isolated performance outliers continue. Previously sent data is not deleted automatically. Settings show the persistent ID in every consent state and link to support for requesting deletion of usage data sent with its derived GA4 ID. Performance-event identifiers are not stored and cannot be identified by the persistent ID. Resetting incompatible settings may remove the local Client ID and prevent an ID-based deletion request. If revocation cannot be saved, usage sending is blocked only for the current service-worker session and the extension asks you to retry.
Third parties
The analytics described above go only to Google Analytics for product improvement. Other third parties do not receive browsing content or analytics, and the data is not sold. Data received through Chrome APIs is used under the Chrome Web Store User Data Policy Limited Use requirements.
Contact
Questions and persistent Client ID deletion requests can be sent through support.