Thanks for sharing your feedback.

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.

Here’s the same problem discussed by Ajay, the author of SponsorBlock and DeArrow:
https://discourse.mozilla.org/t/the-new-data-transmission-permissions-seem-to-be-misleading-to-users/149410

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

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.

Here’s 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

Thanks for raising your concern about 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.

Here’s the same problem discussed by Ajay, the author of SponsorBlock and DeArrow:
https://discourse.mozilla.org/t/the-new-data-transmission-permissions-seem-to-be-misleading-to-users/149410

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

RYD uses only the data needed to display 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.

Here’s 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 wording can sound alarming, but it doesn’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

I understand why those permission labels raised concerns.

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.

Here’s the same problem discussed by Ajay, the author of SponsorBlock and DeArrow:
https://discourse.mozilla.org/t/the-new-data-transmission-permissions-seem-to-be-misleading-to-users/149410

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

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.

Here’s 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

Thanks for sharing your concerns about the update.

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.

Here’s the same problem discussed by Ajay, the author of SponsorBlock and DeArrow:
https://discourse.mozilla.org/t/the-new-data-transmission-permissions-seem-to-be-misleading-to-users/149410

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

RYD 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.

Here’s 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 can sound worrying, 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

I’m sorry the changes have been frustrating.

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.

Here’s the same problem discussed by Ajay, the author of SponsorBlock and DeArrow:
https://discourse.mozilla.org/t/the-new-data-transmission-permissions-seem-to-be-misleading-to-users/149410

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

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.

Here’s 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

the extenion didn't change - Mozillas processes changed.

Here's the same problem discussed by Sponsorblock's author:
https://discourse.mozilla.org/t/the-new-data-transmission-permissions-seem-to-be-misleading-to-users/149410

"Personal data" mentioned - is the random user id used to count likes and dislikes
"Browsing activity" = detecting that you navigated to the next video to show you the dislikes for the next video
"Website activity" - clicking likes and dislikes.

This is how the extension worked from the day one - but now Mozilla requires explicit user consent for this. And they do it on update release - which makes users think that something in the extension changed.

Aggreates are, by definition, not personal.

the extenion didn't change - Mozillas processes changed.

Here's the same problem discussed by Sponsorblock's author:
https://discourse.mozilla.org/t/the-new-data-transmission-permissions-seem-to-be-misleading-to-users/149410

"Personal data" mentioned - is the random user id used to count likes and dislikes
"Browsing activity" = detecting that you navigated to the next video to show you the dislikes for the next video
"Website activity" - clicking likes and dislikes.

This is how the extension worked from the day one - but now Mozilla requires explicit user consent for this. And they do it on update release - which makes users think that something in the extension changed.

As I've replied to many - the extenion didn't change - Mozillas processes changed.

Here's the same problem discussed by Sponsorblock's author:
https://discourse.mozilla.org/t/the-new-data-transmission-permissions-seem-to-be-misleading-to-users/149410

"Personal data" mentioned - is the random user id used to count likes and dislikes
"Browsing activity" = detecting that you navigated to the next video to show you the dislikes for the next video
"Website activity" - clicking likes and dislikes.

This is how the extension worked from the day one - but now Mozilla requires explicit user consent for this. And they do it on update release - which makes users think that something in the extension changed.

the extenion didn't change - Mozillas processes changed.

Here's the same problem discussed by Sponsorblock's author:
https://discourse.mozilla.org/t/the-new-data-transmission-permissions-seem-to-be-misleading-to-users/149410

"Personal data" mentioned - is the random user id used to count likes and dislikes
"Browsing activity" = detecting that you navigated to the next video to show you the dislikes for the next video
"Website activity" - clicking likes and dislikes.

This is how the extension worked from the day one - but now Mozilla requires explicit user consent for this. And they do it on update release - which makes users think that something in the extension changed.

" saying that mozilla forcing you guys to do this is bs" - that is exactly what is happening. Every extension will go through this with the next updates.

Here's the same problem discussed by Sponsorblock's author:
https://discourse.mozilla.org/t/the-new-data-transmission-permissions-seem-to-be-misleading-to-users/149410

As I've replied to many - the extenion didn't change - Mozillas processes changed.

"Personal data" mentioned - is the random user id used to count likes and dislikes
"Browsing activity" = detecting that you navigated to the next video to show you the dislikes for the next video
"Website activity" - clicking likes and dislikes.

This is how the extension worked from the day one - but now Mozilla requires explicit user consent for this. And they do it on update release - which makes users think that something in the extension changed.

As I've replied to many - the extenion didn't change - Mozillas processes changed.

"Personal data" mentioned - is the random user id used to count likes and dislikes
"Browsing activity" = detecting that you navigated to the next video to show you the dislikes for the next video
"Website activity" - clicking likes and dislikes.

This is how the extension worked from the day one - but now Mozilla requires explicit user consent for this. And they do it on update release - which makes users think that something in the extension changed.

As I've replied to many - the extenion didn't change - Mozillas processes changed.

"Personal data" mentioned - is the random user id used to count likes and dislikes
"Browsing activity" = detecting that you navigated to the next video to show you the dislikes for the next video
"Website activity" - clicking likes and dislikes.

This is how the extension worked from the day one - but now Mozilla requires explicit user consent for this. And they do it on update release - which makes users think that something in the extension changed.