Reviews for Return YouTube Dislike
Return YouTube Dislike by Dmitry Selivanov
5,146 reviews
- Rated 1 out of 5by Firefox user 20153509, 8 days agoThe developer suddenly updated this app to add a bunch of analytics features that pop open around YouTube videos and beg you to pay the developer money for "premium" features. It now also collects data from your browser.
Developer response
posted 8 days agoSorry the message about new features bothered you. It’s shown only once during the lifetime of the extension, and it’s timed to appear after a browser restart - hopefully the least disruptive moment.
The extension is actually recommended by Mozilla, so they do not consider it harmful or dangerous.
Handling YouTube-scale traffic and storing dozens of terabytes of like/dislike data on a school-lunch budget ain’t that easy. The funding from these features is what keeps RYD’s servers running.
And as for the permissions:
RYD hasn’t changed how it handles your data. What changed is how Mozilla labels these permissions - not what the extension does with your data.
Ajay, the author of SponsorBlock and DeArrow, has also raised this issue with Mozilla. He explains how the new wording can make an existing extension look like it suddenly started collecting new data, without making clear which websites it can access. You can read his post on Mozilla’s forum here: https://discourse.mozilla.org/t/the-new-data-transmission-permissions-seem-to-be-misleading-to-users/149410
The extension only uses the data it needs to show dislikes and count votes.
Its site permissions cover YouTube and its own API at returnyoutubedislikeapi.com. RYD doesn’t read other websites, and these site permissions cannot be used to access them.
Personally identifiable information - RYD’s randomly generated, anonymous user ID, used to count votes. This isn’t your Google or YouTube account.
Browsing activity - opening the next YouTube video, so the extension can send its video ID and fetch the new dislike count.
Website content - things like the visible like count, which helps calculate dislike estimates.
Website activity - clicking Like or Dislike.
Again, this is about YouTube activity. The extension isn’t watching everything you do across the internet - it simply can’t do that with these site permissions.
The new labels sound scary, but they don’t give the extension access to more websites.
RYD is open source, so you can see how it works: https://github.com/Anarios/return-youtube-dislike - Rated 5 out of 5by Firefox user 18145796, 8 days ago
- Rated 5 out of 5by styzwr, 8 days agoLeaving a 5 star review, check the goddamn github before leaving a one star review the extension is open source.
Developer response
posted 8 days agoThanks for taking the time to leave a review.
RYD hasn’t changed how it handles your data. What changed is how Mozilla labels these permissions - not what the extension does with your data.
Ajay, the author of SponsorBlock and DeArrow, has also raised this issue with Mozilla. He explains how the new wording can make an existing extension look like it suddenly started collecting new data, without making clear which websites it can access. You can read his post on Mozilla’s forum here: https://discourse.mozilla.org/t/the-new-data-transmission-permissions-seem-to-be-misleading-to-users/149410
The extension only uses the data it needs to show dislikes and count votes.
Its site permissions cover YouTube and its own API at returnyoutubedislikeapi.com. RYD doesn’t read other websites, and these site permissions cannot be used to access them.
Personally identifiable information - RYD’s randomly generated, anonymous user ID, used to count votes. This isn’t your Google or YouTube account.
Browsing activity - opening the next YouTube video, so the extension can send its video ID and fetch the new dislike count.
Website content - things like the visible like count, which helps calculate dislike estimates.
Website activity - clicking Like or Dislike.
Again, this is about YouTube activity. The extension isn’t watching everything you do across the internet - it simply can’t do that with these site permissions.
The new labels sound scary, but they don’t give the extension access to more websites.
RYD is open source, so you can see how it works: https://github.com/Anarios/return-youtube-dislike Developer response
posted 9 days agoThanks for the feedback.
The extension is actually recommended by Mozilla, so they do not consider it harmful or dangerous.
RYD hasn’t changed how it handles your data. What changed is how Mozilla labels these permissions - not what the extension does with your data.
Ajay, the author of SponsorBlock and DeArrow, has also raised this issue with Mozilla. He explains how the new wording can make an existing extension look like it suddenly started collecting new data, without making clear which websites it can access. You can read his post on Mozilla’s forum here: https://discourse.mozilla.org/t/the-new-data-transmission-permissions-seem-to-be-misleading-to-users/149410
The extension only uses the data it needs to show dislikes and count votes.
Its site permissions cover YouTube and its own API at returnyoutubedislikeapi.com. RYD doesn’t read other websites, and these site permissions cannot be used to access them.
Let me explain what those permissions mean.
Personally identifiable information - RYD’s randomly generated, anonymous user ID, used to count votes. This isn’t your Google or YouTube account.
Browsing activity - opening the next YouTube video, so the extension can send its video ID and fetch the new dislike count.
Website content - things like the visible like count, which helps calculate dislike estimates.
Website activity - clicking Like or Dislike.
Again, this is about YouTube activity. The extension isn’t watching everything you do across the internet - it simply can’t do that with these site permissions.
The new labels sound scary, but they don’t give the extension access to more websites.
RYD is open source, so you can see how it works: https://github.com/Anarios/return-youtube-dislike- Rated 5 out of 5by cannon9009, 9 days agoWorks as intended.
At the time of writing the extension is being bombarded by negative reviews. Let me copy and paste the explanation as to why the extension requires what APPEARS to the user to be personally identifying info:
RYD hasn’t changed how it handles your data. What changed is how Mozilla labels these permissions - not what the extension does with your data.
The extension only uses the data it needs to show dislikes and count votes.
Its site permissions cover YouTube and its own API at returnyoutubedislikeapi.com. RYD doesn’t read other websites, and these site permissions cannot be used to access them.
Personally identifiable information - RYD’s randomly generated, persistent user ID, used to count votes. This isn’t your Google or YouTube account. Our server also sees your IP address when you connect.
Browsing activity - opening the next YouTube video, so the extension can send its video ID and fetch the new dislike count.
Website content - things like the visible like count, which helps calculate dislike estimates.
Website activity - clicking Like or Dislike.
Again, this is about YouTube activity. The extension isn’t watching everything you do across the internet - it simply can’t do that with these site permissions.
The new labels sound scary, but they don’t give the extension access to more websites.
RYD is open source, so you can see how it works: https(://)github(.)com(/)Anarios(/)return-youtube-dislike
End transmission.Developer response
posted 9 days agoThanks for taking the time to leave a review.
RYD hasn’t changed how it handles your data. What changed is how Mozilla labels these permissions - not what the extension does with your data.
Ajay, the author of SponsorBlock and DeArrow, has also raised this issue with Mozilla. He explains how the new wording can make an existing extension look like it suddenly started collecting new data, without making clear which websites it can access. You can read his post on Mozilla’s forum here: https://discourse.mozilla.org/t/the-new-data-transmission-permissions-seem-to-be-misleading-to-users/149410
The extension only uses the data it needs to show dislikes and count votes.
Its site permissions cover YouTube and its own API at returnyoutubedislikeapi.com. RYD doesn’t read other websites, and these site permissions cannot be used to access them.
Personally identifiable information - RYD’s randomly generated, anonymous user ID, used to count votes. This isn’t your Google or YouTube account.
Browsing activity - opening the next YouTube video, so the extension can send its video ID and fetch the new dislike count.
Website content - things like the visible like count, which helps calculate dislike estimates.
Website activity - clicking Like or Dislike.
Again, this is about YouTube activity. The extension isn’t watching everything you do across the internet - it simply can’t do that with these site permissions.
The new labels sound scary, but they don’t give the extension access to more websites.
RYD is open source, so you can see how it works: https://github.com/Anarios/return-youtube-dislike - Rated 1 out of 5by Mat, 9 days agoSolicita Actividad de navegación e Información de identificación personal, elementos que previamente no solicitaba. Quiere vender tu información.
Developer response
posted 9 days agoThanks for the feedback.
The extension is actually recommended by Mozilla, so they do not consider it harmful or dangerous.
RYD hasn’t changed how it handles your data. What changed is how Mozilla labels these permissions - not what the extension does with your data.
Ajay, the author of SponsorBlock and DeArrow, has also raised this issue with Mozilla. He explains how the new wording can make an existing extension look like it suddenly started collecting new data, without making clear which websites it can access. You can read his post on Mozilla’s forum here: https://discourse.mozilla.org/t/the-new-data-transmission-permissions-seem-to-be-misleading-to-users/149410
The extension only uses the data it needs to show dislikes and count votes.
Its site permissions cover YouTube and its own API at returnyoutubedislikeapi.com. RYD doesn’t read other websites, and these site permissions cannot be used to access them.
Let me explain what those permissions mean.
Personally identifiable information - RYD’s randomly generated, anonymous user ID, used to count votes. This isn’t your Google or YouTube account.
Browsing activity - opening the next YouTube video, so the extension can send its video ID and fetch the new dislike count.
Website content - things like the visible like count, which helps calculate dislike estimates.
Website activity - clicking Like or Dislike.
Again, this is about YouTube activity. The extension isn’t watching everything you do across the internet - it simply can’t do that with these site permissions.
The new labels sound scary, but they don’t give the extension access to more websites.
RYD is open source, so you can see how it works: https://github.com/Anarios/return-youtube-dislike - Rated 1 out of 5by MrDrLiviu, 9 days agoYou do not need any "IDENTIFIABLE" information.
You do not need any "BROWSING HISTORY".
Why tf would you need all that to show dislikes.
Worked fine until now and now it need to harvest your data to function. F .... UDeveloper response
posted 9 days agoThanks for the feedback.
The extension is actually recommended by Mozilla, so they do not consider it harmful or dangerous.
RYD hasn’t changed how it handles your data. What changed is how Mozilla labels these permissions - not what the extension does with your data.
Ajay, the author of SponsorBlock and DeArrow, has also raised this issue with Mozilla. He explains how the new wording can make an existing extension look like it suddenly started collecting new data, without making clear which websites it can access. You can read his post on Mozilla’s forum here: https://discourse.mozilla.org/t/the-new-data-transmission-permissions-seem-to-be-misleading-to-users/149410
The extension only uses the data it needs to show dislikes and count votes.
Its site permissions cover YouTube and its own API at returnyoutubedislikeapi.com. RYD doesn’t read other websites, and these site permissions cannot be used to access them.
Let me explain what those permissions mean.
Personally identifiable information - RYD’s randomly generated, anonymous user ID, used to count votes. This isn’t your Google or YouTube account.
Browsing activity - opening the next YouTube video, so the extension can send its video ID and fetch the new dislike count.
Website content - things like the visible like count, which helps calculate dislike estimates.
Website activity - clicking Like or Dislike.
Again, this is about YouTube activity. The extension isn’t watching everything you do across the internet - it simply can’t do that with these site permissions.
The new labels sound scary, but they don’t give the extension access to more websites.
RYD is open source, so you can see how it works: https://github.com/Anarios/return-youtube-dislike - Rated 3 out of 5by IronEleven, 9 days ago
Developer response
posted 9 days agoThanks for the feedback.
The extension is actually recommended by Mozilla, so they do not consider it harmful or dangerous.
RYD hasn’t changed how it handles your data. What changed is how Mozilla labels these permissions - not what the extension does with your data.
Ajay, the author of SponsorBlock and DeArrow, has also raised this issue with Mozilla. He explains how the new wording can make an existing extension look like it suddenly started collecting new data, without making clear which websites it can access. You can read his post on Mozilla’s forum here: https://discourse.mozilla.org/t/the-new-data-transmission-permissions-seem-to-be-misleading-to-users/149410
The extension only uses the data it needs to show dislikes and count votes.
Its site permissions cover YouTube and its own API at returnyoutubedislikeapi.com. RYD doesn’t read other websites, and these site permissions cannot be used to access them.
Let me explain what those permissions mean.
Personally identifiable information - RYD’s randomly generated, anonymous user ID, used to count votes. This isn’t your Google or YouTube account.
Browsing activity - opening the next YouTube video, so the extension can send its video ID and fetch the new dislike count.
Website content - things like the visible like count, which helps calculate dislike estimates.
Website activity - clicking Like or Dislike.
Again, this is about YouTube activity. The extension isn’t watching everything you do across the internet - it simply can’t do that with these site permissions.
The new labels sound scary, but they don’t give the extension access to more websites.
RYD is open source, so you can see how it works: https://github.com/Anarios/return-youtube-dislike- Rated 3 out of 5by saint23thomas, 9 days ago
- Rated 5 out of 5by Firefox user 20153128, 9 days agoWorks as intended. As for the "This requires new permissions". After taking a look all its doing is hashing your user name (so you cant dislike bomb as a single user) and grabs what page your viewing (so it knows how many dislikes there are). Otherwise this app can't function as intended. For those quickly disliking this is a firefox thing. Its good to be skeptical in these times but please use due diligence :)
Developer response
posted 9 days agoThanks!.
Tiny correction - it's not even hashing username - it's randomly generated
Regarding the situation with permissions:
The extension only collects data that it requires to function.
The extension can only access these permissions on two sites - YouTube and it's own returnyoutubedislike - on all other sites it's not even allowed to "turn on".
Personally identifiable information - RYD’s randomly generated private user ID used to count votes, not your real identity.
Browsing activity - i.e. navigating to the next video, so that the next dislikes can be shown
Website content - i.e. the like\dislike container element
Website activithy - i.e. clicking like or dislike button.
As I already said - only on YouTube. Not everywhere.
Nothing in the extension changed - it’s open-source, so you can verify that yourself. What changed is how Mozilla labels privacy-related permissions.
Ajay, the author of SponsorBlock and DeArrow, has also raised this issue with Mozilla. He explains how the new wording can make an existing extension look like it suddenly started collecting new data, without making clear which websites it can access. You can read his post on Mozilla’s forum here: https://discourse.mozilla.org/t/the-new-data-transmission-permissions-seem-to-be-misleading-to-users/149410
The new labels sound scary, but they describe the same data the extension has always used. - Rated 5 out of 5by g1zm02k, 9 days agoOh no, an extension requires information to do its job properly; everyone panic and start hoarding toilet rolls and bottled water!
2020's lunacy at its finest🤦🏻♂️
Nice update Dmitry, it's looking mighty fine. Sorry you have to suffer the deranged rantings of the masses, it's not like they got off their arses and made a similar extension themselves; ungrateful buggers.
Thanks man, much appreciated!Developer response
posted 9 days agoThanks!
And default copypasta to be seen on top.
Regarding the situation with permissions:
The extension only collects data that it requires to function.
The extension can only access these permissions on two sites - YouTube and it's own returnyoutubedislike - on all other sites it's not even allowed to "turn on".
Personally identifiable information - RYD’s randomly generated private user ID used to count votes, not your real identity.
Browsing activity - i.e. navigating to the next video, so that the next dislikes can be shown
Website content - i.e. the like\dislike container element
Website activithy - i.e. clicking like or dislike button.
As I already said - only on YouTube. Not everywhere.
Nothing in the extension changed - it’s open-source, so you can verify that yourself. What changed is how Mozilla labels privacy-related permissions.
Ajay, the author of SponsorBlock and DeArrow, has also raised this issue with Mozilla. He explains how the new wording can make an existing extension look like it suddenly started collecting new data, without making clear which websites it can access. You can read his post on Mozilla’s forum here: https://discourse.mozilla.org/t/the-new-data-transmission-permissions-seem-to-be-misleading-to-users/149410
The new labels sound scary, but they describe the same data the extension has always used. - Rated 1 out of 5by asmness, 9 days agoVery dissapointed about the data collection. It's completely unnecessary.
Developer response
posted 9 days agoThe extension is actually recommended by Mozilla, so they do not consider it harmful or dangerous.
The extension only collects data that it requires to function.
The extension can only access these permissions on two sites - YouTube and it's own returnyoutubedislike - on all other sites it's not even allowed to "turn on".
Personally identifiable information - RYD’s randomly generated private user ID used to count votes, not your real identity.
Browsing activity - i.e. navigating to the next video, so that the next dislikes can be shown
Website content - i.e. the like\dislike container element
Website activithy - i.e. clicking like or dislike button.
As I already said - only on YouTube. Not everywhere.
Nothing in the extension changed - it’s open-source, so you can verify that yourself. What changed is how Mozilla labels privacy-related permissions.
Ajay, the author of SponsorBlock and DeArrow, has also raised this issue with Mozilla. He explains how the new wording can make an existing extension look like it suddenly started collecting new data, without making clear which websites it can access. You can read his post on Mozilla’s forum here: https://discourse.mozilla.org/t/the-new-data-transmission-permissions-seem-to-be-misleading-to-users/149410
The new labels sound scary, but they describe the same data the extension has always used. - Rated 1 out of 5by nosane, 9 days ago
- Rated 5 out of 5by Suspect, 9 days agoDo we finally have an update? And it hasn’t even been three years...
- Rated 5 out of 5by Firefox user 20152964, 9 days agoalright I was initially frightened by the personal data consent request in the 4.0.6 update just like others have stated in recent reviews. i am NOT good at reading code, but even still i can view every single commit made for this update on the github. i completely understand why people are worried about this update, but reacting based on emotions isn't going to find the truth. check the github, read the code, check the security faq, and be willing to learn.
i do also want to say to the developer that your response to people's reviews has been, in my eyes, very unprofessional. even though i personally believe that you're in the right, it's still important to treat customers with respect. the security FAQ that explains this whole situation is only on the github. i believe it should be front and center in this extension page's about section. there might be less uninformed outcry if it were that much more visible.
aside from that though, the new features are excellent and i look forward to using it more. thanks again for both your effort and the github contributorsDeveloper response
posted 9 days agoSorry, my previous reply was unnecessarily rude.
RYD hasn’t changed how it handles your data. What changed is how Mozilla labels these permissions - not what the extension does with your data.
Ajay, the author of SponsorBlock and DeArrow, has also raised this issue with Mozilla. He explains how the new wording can make an existing extension look like it suddenly started collecting new data, without making clear which websites it can access. You can read his post on Mozilla’s forum here: https://discourse.mozilla.org/t/the-new-data-transmission-permissions-seem-to-be-misleading-to-users/149410
The extension only uses the data it needs to show dislikes and count votes.
Its site permissions cover YouTube and its own API at returnyoutubedislikeapi.com. RYD doesn’t read other websites, and these site permissions cannot be used to access them.
Personally identifiable information - RYD’s randomly generated, anonymous user ID, used to count votes. This isn’t your Google or YouTube account.
Browsing activity - opening the next YouTube video, so the extension can send its video ID and fetch the new dislike count.
Website content - things like the visible like count, which helps calculate dislike estimates.
Website activity - clicking Like or Dislike.
Again, this is about YouTube activity. The extension isn’t watching everything you do across the internet - it simply can’t do that with these site permissions.
The new labels sound scary, but they don’t give the extension access to more websites.
RYD is open source, so you can see how it works: https://github.com/Anarios/return-youtube-dislike - Rated 5 out of 5by Kuri, 9 days ago
- Rated 5 out of 5by Firefox user 18821540, 9 days agoThank god my data isn't getting stolen. I was scared there for a second before reading the recent reviews and the developer response
Developer response
posted 9 days agoThanks. Yep - this new system gives a very scary impression.
Ajay, the author of SponsorBlock and DeArrow, has also raised this issue with Mozilla. He explains how the new wording can make an existing extension look like it suddenly started collecting new data, without making clear which websites it can access. You can read his post on Mozilla’s forum here: https://discourse.mozilla.org/t/the-new-data-transmission-permissions-seem-to-be-misleading-to-users/149410
But in reality - the extension can only access these permissions on two sites - YouTube and it's own returnyoutubedislike - on all other sites it's not even allowed to "turn on".
Personally identifiable information - RYD’s randomly generated private user ID used to count votes, not your real identity.
Browsing activity - i.e. navigating to the next video, so that the next dislikes can be shown
Website content - i.e. the like\dislike container element
Website activithy - i.e. clicking like or dislike button.
As I already said - only on YouTube. Not everywhere. - Rated 5 out of 5by ddknight, 9 days ago
- Rated 5 out of 5by ilikethisbrowser1164, 9 days agoi, like many others, was confused about the new permissions and came here. then i took a look at the dev's replies and it all makes sense now
to other concerned folks: please read the dev's response to other reviews, and if you're still skeptical, the code is open-source, feel free to look yourselfDeveloper response
posted 9 days agoThanks for taking the time to leave a review.
RYD hasn’t changed how it handles your data. What changed is how Mozilla labels these permissions - not what the extension does with your data.
Ajay, the author of SponsorBlock and DeArrow, has also raised this issue with Mozilla. He explains how the new wording can make an existing extension look like it suddenly started collecting new data, without making clear which websites it can access. You can read his post on Mozilla’s forum here: https://discourse.mozilla.org/t/the-new-data-transmission-permissions-seem-to-be-misleading-to-users/149410
The extension only uses the data it needs to show dislikes and count votes.
Its site permissions cover YouTube and its own API at returnyoutubedislikeapi.com. RYD doesn’t read other websites, and these site permissions cannot be used to access them.
Personally identifiable information - RYD’s randomly generated, anonymous user ID, used to count votes. This isn’t your Google or YouTube account.
Browsing activity - opening the next YouTube video, so the extension can send its video ID and fetch the new dislike count.
Website content - things like the visible like count, which helps calculate dislike estimates.
Website activity - clicking Like or Dislike.
Again, this is about YouTube activity. The extension isn’t watching everything you do across the internet - it simply can’t do that with these site permissions.
The new labels sound scary, but they don’t give the extension access to more websites.
RYD is open source, so you can see how it works: https://github.com/Anarios/return-youtube-dislike - Rated 5 out of 5by JBoot8, 9 days agoI was concerned about the new permissions required, but scrolled down and saw a reply from the developer explaining what was going on. Everything collected is only related to YouTube and is anonymized, the same as what previous versions were doing. The only thing that changed was how Mozilla classifies permissions.
Thank you to the dev for the explanation!Developer response
posted 9 days agoThanks for taking your time read. I agree, this new system gives a very scary impression.
Ajay, the author of SponsorBlock and DeArrow, has also raised this issue with Mozilla. He explains how the new wording can make an existing extension look like it suddenly started collecting new data, without making clear which websites it can access. You can read his post on Mozilla’s forum here: https://discourse.mozilla.org/t/the-new-data-transmission-permissions-seem-to-be-misleading-to-users/149410
But in reality - the extension can only access these permissions on two sites - YouTube and it's own returnyoutubedislike - on all other sites it's not even allowed to "turn on".
Personally identifiable information - RYD’s randomly generated private user ID used to count votes, not your real identity.
Browsing activity - i.e. navigating to the next video, so that the next dislikes can be shown
Website content - i.e. the like\dislike container element
Website activithy - i.e. clicking like or dislike button.
As I already said - only on YouTube. Not everywhere. - Rated 5 out of 5by Firefox user 19583727, 9 days ago
- Rated 5 out of 5by charizardcharz, 9 days ago
- Rated 5 out of 5by Dream, 9 days agostop review bombing, it’s open-source. if you have a problem with the code, just show it.
Developer response
posted 9 days agoThanks for taking the time to leave a review.
RYD hasn’t changed how it handles your data. What changed is how Mozilla labels these permissions - not what the extension does with your data.
Ajay, the author of SponsorBlock and DeArrow, has also raised this issue with Mozilla. He explains how the new wording can make an existing extension look like it suddenly started collecting new data, without making clear which websites it can access. You can read his post on Mozilla’s forum here: https://discourse.mozilla.org/t/the-new-data-transmission-permissions-seem-to-be-misleading-to-users/149410
The extension only uses the data it needs to show dislikes and count votes.
Its site permissions cover YouTube and its own API at returnyoutubedislikeapi.com. RYD doesn’t read other websites, and these site permissions cannot be used to access them.
Personally identifiable information - RYD’s randomly generated, anonymous user ID, used to count votes. This isn’t your Google or YouTube account.
Browsing activity - opening the next YouTube video, so the extension can send its video ID and fetch the new dislike count.
Website content - things like the visible like count, which helps calculate dislike estimates.
Website activity - clicking Like or Dislike.
Again, this is about YouTube activity. The extension isn’t watching everything you do across the internet - it simply can’t do that with these site permissions.
The new labels sound scary, but they don’t give the extension access to more websites.
RYD is open source, so you can see how it works: https://github.com/Anarios/return-youtube-dislike - Rated 5 out of 5by Koomongous, 9 days agoI was concerned for a moment, but taking a look:
"From November 3, 2025, all new extensions must adopt the Firefox built-in data collection consent system. Extensions must state if and what data they collect or transmit. New versions and updates for add-ons created before November 3 don’t need to use this feature, but will have to at a later date."
This appears to apply in this case :)Developer response
posted 9 days agoThanks for taking the time to leave a review.
RYD hasn’t changed how it handles your data. What changed is how Mozilla labels these permissions - not what the extension does with your data.
Ajay, the author of SponsorBlock and DeArrow, has also raised this issue with Mozilla. He explains how the new wording can make an existing extension look like it suddenly started collecting new data, without making clear which websites it can access. You can read his post on Mozilla’s forum here: https://discourse.mozilla.org/t/the-new-data-transmission-permissions-seem-to-be-misleading-to-users/149410
The extension only uses the data it needs to show dislikes and count votes.
Its site permissions cover YouTube and its own API at returnyoutubedislikeapi.com. RYD doesn’t read other websites, and these site permissions cannot be used to access them.
Personally identifiable information - RYD’s randomly generated, anonymous user ID, used to count votes. This isn’t your Google or YouTube account.
Browsing activity - opening the next YouTube video, so the extension can send its video ID and fetch the new dislike count.
Website content - things like the visible like count, which helps calculate dislike estimates.
Website activity - clicking Like or Dislike.
Again, this is about YouTube activity. The extension isn’t watching everything you do across the internet - it simply can’t do that with these site permissions.
The new labels sound scary, but they don’t give the extension access to more websites.
RYD is open source, so you can see how it works: https://github.com/Anarios/return-youtube-dislike