Thanks 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

"you’re either a developer or a politician🤡 – make up your mind"

'squse me?

Thanks 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

Thanks 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

Yep, that's one way, another is git history at https://github.com/Anarios/return-youtube-dislike/releases

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

Sorry, 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

<3

Thanks 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

You could open the homepage of extension to know my position on russians. By a huge "support Ukraine" banner.

The extension is actually recommended by Mozilla, so they do not consider it harmful or dangerous.

> now asking for permissions the add-on clearly doesnt need in order to function.

a permission to access youtube and returnyoutubedislike are not needed for the extension to work?

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 extension only uses an anonymous, randomly generated ID, and the id of the video that you liked/disliked.

• YouTube access - needed to read the current video ID and show its dislike count.
• RYD API access - needed for API requests and diagnostics.
• Online/activity data - viewing, liking, or disliking videos.
• Personally identifiable information - RYD’s random private user ID used to count votes, not your real identity.
• Website content - mainly the video ID.

The new labels sound scary, but they describe the same data the extension has always used.