Is YouTube Anti Translate - Official Port safe?
YouTube Anti Translate uses YouTube cookies to authorize first-party YouTube API requests.
On YouTube pages, the extension reads the SAPISID cookie and derives a SAPISIDHASH authorization header for YouTube's own API. It uses that request to restore original video titles, descriptions, and channel branding, and the available claim does not show the raw cookie being sent to a third party.
Who publishes itnamakeingo - no other listings under this identity, 1 shared hostname
namakeingo - no other listings under this identity, 1 shared hostname
What this publisher told the store about itself, and the other listings that told it the same thing.
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.
What it can do
Permissions this extension asks for, as declared in version 1.20.4.4. Asking for a permission is not a finding on its own - it is what the extension can do if it chooses to.
Read and change your data on youtube.com
*://*.youtube.com/*
Read and change your data on youtube-nocookie.com
*://*.youtube-nocookie.com/*
Store data in your browser
storage
Where it sends data
Destinations our analysis observed YouTube Anti Translate - Official Port 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.
- www.youtube.com
YouTube Anti Translate - Official Port sends data to www.youtube.com. 18 other extensions we have analysed send data here.