Is TimeTags for YouTube safe?
TimeTags for YouTube sends the current YouTube video ID to its API proxy endpoints when activated.
When you click the extension on a YouTube video page, it injects its interface and requests video details and comment threads for that video. Those requests include the current video ID and go to developer-operated API proxy endpoints used to load the extension's comments and chapters panels.
Who publishes itChih-Hsuan Fan - no other listings under this identity
Chih-Hsuan Fan - no other listings under this identity
What this publisher told the store about itself, and the other listings that told it the same thing.
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.6.3. 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 www.youtube.com
https://www.youtube.com/
Read and change your data on youtu.be
https://youtu.be/
Store data in your browser
storage
Run its own code inside the pages you visit
scripting
Store an unlimited amount of data in your browser
unlimitedStorage
Where it sends data
Destinations our analysis observed TimeTags for YouTube 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.
- cloud.pymaster.tw
TimeTags for YouTube sends data to cloud.pymaster.tw. No other extension we have analysed sends data here.
- us-central1-yt-timetag.cloudfunctions.net
TimeTags for YouTube sends data to us-central1-yt-timetag.cloudfunctions.net. No other extension we have analysed sends data here.