Is TTS Reader safe?
TTS Reader sends page text for speech playback and widget analytics with page URLs to external services.
When you use text-to-speech, TTS Reader collects visible page text and sends each sentence with voice settings and a stable client ID to its speech service. Its injected widget also sends analytics events for opens, closes, and playback actions that include the current page URL and the same kind of persistent identifier.
Who publishes itFreshcode LTD - 1 other listing from the same operator, none carrying a finding
Freshcode LTD - 1 other listing from the same operator, none carrying a finding
What this publisher told the store about itself, and the other listings that told it the same thing.
Same operator - 1 listing
Published under a different store account, but sharing the registered address, contact or declared legal entity this one gave the store.
Shared hosts - 1 hostname
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.
AI-generated. Findings may contain errors. Those marked Verified have been manually reviewed.
Publishers can request a review.
Where it sends data
Destinations our analysis observed TTS Reader contacting. Sending data somewhere is not a finding on its own - an extension that syncs your settings has to talk to its own server - but it is where your data can go, and who else it goes to.
- api.eu.amplitude.com
TTS Reader sends data to api.eu.amplitude.com. 7 other extensions we have analysed send data here.
- ttsreader.up.railway.app
TTS Reader sends data to ttsreader.up.railway.app. No other extension we have analysed sends data here.