Is TxtAnalyser safe?
TxtAnalyser is low risk.
TxtAnalyser sends the Google Docs document URL, pseudonymized user email, and device metadata to Google Analytics on each interaction.
Each time a user activates the extension or changes a grammar setting, it collects the full Google Docs URL (including document ID), a SHA-256-pseudonymized email address, a persistent random client ID, and device details such as timezone, screen resolution, OS, and browser version. These are POSTed to Google Analytics 4 via a hardcoded Measurement Protocol endpoint using a private API secret. The document URL is sent as an event parameter, linking browsing sessions to specific documents.
Who publishes itEverway A/S - 5 other listings from the same operator, 1 of them carrying a finding
Everway A/S - 5 other listings from the same operator, 1 of them carrying a finding
Same store account
1 other listing published from this account, 400k+ users between them. 1 of them carries a finding.
Same operator - 4 listings
Published under a different store account, but sharing the registered address, contact or declared legal entity this one gave the store.
Shared hosts - 2 hostnames
Hostnames hardcoded in this extension that few other listings call. That can mean one operator behind both, and it can equally mean a small shared vendor, so it is context rather than a conclusion. Hosts that many listings call are left out: they are services, not connections.
TxtAnalyser findings
TxtAnalyser sends the full Google Docs URL and hashed email to Google Analytics
Code analysis shows the extension sends the full address of the Google Docs page you are editing, plus a partly hashed form of your email, to Google Analytics when you use its features.
What actually happens
You open a Google Docs document and use the extension.
This includes activation, grammar language changes, feature use and feedback.
It sends the full document URL and a partly hashed email to Google Analytics.
The event also carries a persistent random client ID and device details.
Fields in the analytics event, from code
- Document addresshttps://docs.google.com/document/d/1AbC...xyz/edit (illustrative)
The full Google Docs URL, which includes the document ID.
- User ID9f86d081...0a08@example.com (illustrative)
Your email with the part before @ hashed and the domain left readable.
- Client ID3f2b8c1e-5a7d-4e90-b1c2-7d4a9e6f0a12 (illustrative)
A random UUID kept in extension storage, stable across events.
- Device details1920x1080, Windows, Chrome 131 (illustrative)
Time zone, screen size, OS, browser version, DPI and monitor count.
The code that does this
GA4 send call in the shipped bundle
What it does
event.params = { feature, website: pageUrl, engagement_time_msec: 1, ga_session_id, session_time, ...extra };await fetch('https://www.google-analytics.com/mp/collect?measurement_id=G-HTCHM7E0L4&api_secret=<redacted>', { method: 'POST', body: JSON.stringify(event) });Where the event goes
- www.google-analytics.com
Google Analytics 4 Measurement Protocol endpoint; receives URL, hashed-email user ID and device details.
Observation
Two dynamic-analysis attempts did not reach this code path. Google Docs blocked the extension's page script, so no request to Google Analytics was observed.
Observation
Static analysis finding. This behaviour was identified by reading the shipped extension code and has not yet been reproduced in a live run. The trigger conditions and the exact data sent are read from the code, not from an observed capture.
What TxtAnalyser can do
Permissions this extension asks for, as declared in version 2.3.1. Asking for a permission is not a finding on its own - it is what the extension can do if it chooses to. The current listed version is 2.3.9, which we have not unpacked yet.
Read and change your data on lingapps.dk
*://*.lingapps.dk/*
Read and change your data on wizkids.dk
*://*.wizkids.dk/*
Read and change your data on wizkids.tech
*://*.wizkids.tech/*
Read and change your data on accounts.google.com
*://*.accounts.google.com/*
Read and change your data on docs.google.com
*://*.docs.google.com/*
Read and change your data on onedrive.live.com
*://onedrive.live.com/*
Read and change your data on sharepoint.com
*://*.sharepoint.com/*
Read and change your data on officeapps.live.com
*://*.officeapps.live.com/*
Read and change your data on sso.emu.dk
*://sso.emu.dk/*
Read and change your data on atlas.uni-login.dk
*://atlas.uni-login.dk/*
Read and change your data on broker.unilogin.dk
*://broker.unilogin.dk/*
Schedule its own background tasks
alarms
See the address and title of every tab you have open
tabs
See every page you navigate to, as you navigate to it
webNavigation
Watch every request your browser makes
webRequest
Block and redirect the requests your browser makes
declarativeNetRequest
Store data in your browser
storage
Run its own code inside the pages you visit
scripting
TxtAnalyser version history
2.3.0
Mar 4, 2026
+1 more
2.3.8
Sep 22, 2026
2.3.7
Sep 22, 2026
2.3.9
Nov 2, 2026
Where TxtAnalyser sends data
- csp.withgoogle.com/csp/docs-tt2 calls
From a script it injects into websites · 2 other extensions
- services.lingapps.dk/textAnalyzer/getTranslations2 calls
From its background script · 1 other extension
- www.google-analytics.comwidely used
Found in its code · 410 other extensions
Chrome Web Store listing
- Versions
- 2.3.9 latest of 5 seen since March 4, 2026
- Store rating
- 2.2 from 62 ratings
- Last updated
- June 8, 2026
- Size
- 714 KiB
- Privacy policy
- www.everway.com
