mirror of
https://github.com/Anarios/return-youtube-dislike.git
synced 2026-10-27 23:31:06 +01:00
Clarify IP data handling in privacy documentation
This commit is contained in:
Anarios
@@ -41,7 +41,7 @@ If the basic checks didn't resolve anything
|
||||
|
||||
- If you **don't see something like** this, then the **API is down** and **everything is fine on your side**.
|
||||
`{"id":"QOFEgexls14","dateCreated":"2021-12-28T02:53:20.995329Z","likes":2968,"dislikes":204,"rating":4.725047080979285,"viewCount":29157,"deleted":false}`
|
||||
- If you see some responses but not in the above format (with likes and dislikes) then probably you are being rate-limited. It is done to prevent bot attacks and database vandalization. It depends on IP (its hash - which is never stored in non-volatile storage) for its countermeasures. If many people are accessing the server from the same IP (as in the case of public/institutional Wi-Fi) then it's possible that the IP is being rate-limited. If that's the case, there's no way for us to differentiate you from a bot/attacker.
|
||||
- If you see some responses but not in the above format (with likes and dislikes) then probably you are being rate-limited. It is done to prevent bot attacks and database vandalization. Raw IP addresses stay in RAM and hashes are stored to help prevent abuse. If many people are accessing the server from the same IP (as in the case of public/institutional Wi-Fi) then it's possible that the IP is being rate-limited. If that's the case, there's no way for us to differentiate you from a bot/attacker.
|
||||
|
||||
**If you see "Certificate error" and [if you are on Windows 7 (or earlier) read this](#install-certificates)**
|
||||
|
||||
|
||||
@@ -41,7 +41,7 @@ If the basic checks didn't resolve anything
|
||||
|
||||
- If you **don't see something like** this, then the **API is down** and **everything is fine on your side**.
|
||||
`{"id":"QOFEgexls14","dateCreated":"2021-12-28T02:53:20.995329Z","likes":2968,"dislikes":204,"rating":4.725047080979285,"viewCount":29157,"deleted":false}`
|
||||
- If you see some responses but not in the above format (with likes and dislikes) then probably you are being rate-limited. It is done to prevent bot attacks and database vandalization. It depends on IP (its hash - which is never stored in non-volatile storage) for its countermeasures. If many people are accessing the server from the same IP (as in the case of public/institutional Wi-Fi) then it's possible that the IP is being rate-limited. If that's the case, there's no way for us to differentiate you from a bot/attacker.
|
||||
- If you see some responses but not in the above format (with likes and dislikes) then probably you are being rate-limited. It is done to prevent bot attacks and database vandalization. Raw IP addresses stay in RAM and hashes are stored to help prevent abuse. If many people are accessing the server from the same IP (as in the case of public/institutional Wi-Fi) then it's possible that the IP is being rate-limited. If that's the case, there's no way for us to differentiate you from a bot/attacker.
|
||||
|
||||
**If you see "Certificate error" and [if you are on Windows 7 (or earlier) read this](#install-certificates)**
|
||||
|
||||
|
||||
+4
-3
@@ -1,6 +1,6 @@
|
||||
# Return YouTube Dislike Privacy Policy
|
||||
|
||||
Last updated: September 5, 2026
|
||||
Last updated: September 10, 2026
|
||||
|
||||
This policy describes version 4.0.5 and its matching backend release.
|
||||
|
||||
@@ -46,8 +46,9 @@ user's Patreon or GitHub password.
|
||||
|
||||
The identifier, settings, and optional account session use browser extension sync storage, which may be synchronized
|
||||
through the browser's sync service when the user enables it. The random installation identifier remains in extension storage until the extension data is cleared, registration is
|
||||
reset, or the extension is removed. Confirmed vote records contain the identifier, video ID, vote, timestamp, and the
|
||||
network address used for abuse controls. Registration and vote records are retained by the service while they are
|
||||
reset, or the extension is removed. Confirmed vote records contain the identifier, video ID, vote, timestamp, and an
|
||||
IP-address hash used for abuse controls. Raw IP addresses stay in RAM and hashes are stored.
|
||||
Registration and vote records are retained by the service while they are
|
||||
needed to calculate results, maintain vote integrity, and prevent abuse; no shorter automatic deletion period is
|
||||
promised.
|
||||
|
||||
|
||||
@@ -19,15 +19,16 @@ associate submitted votes with the same extension installation.
|
||||
### What information do you have, exactly?
|
||||
|
||||
For dislike-count requests: the current video ID and, when available, the visible like count. For registration and vote
|
||||
submission: the random extension user ID, video ID, selected vote, timestamp, and network address used for abuse
|
||||
controls. Optional premium features use the account ID, name, email address, profile image, membership information, and
|
||||
service session token returned by a Patreon or GitHub sign-in initiated by the user. For version 4.0.5 and its matching
|
||||
submission: the random extension user ID, video ID, selected vote, and timestamp. The API also receives your IP address.
|
||||
Raw addresses stay in RAM and hashes are stored for abuse controls. Optional premium features use the account ID, name,
|
||||
email address, profile image, membership information, and service session token returned by a Patreon or GitHub sign-in
|
||||
initiated by the user. For version 4.0.5 and its matching
|
||||
backend release, Patreon access is determined from currently entitled tier IDs rather than financial information.
|
||||
|
||||
### How is my IP stored?
|
||||
|
||||
The API receives your network address with each request. Confirmed vote records retain the network address used for
|
||||
abuse prevention and aggregate analytics. It is not sold or used for advertising.
|
||||
Raw IP addresses stay in RAM and hashes are stored. This information is used for abuse prevention and aggregate
|
||||
analytics. It is not sold or used for advertising.
|
||||
|
||||
### I heard some discussion over OAuth, and access to my YouTube account!
|
||||
|
||||
|
||||
@@ -16,7 +16,7 @@ Sadəcə video identifikatoru. Şərhləriniz, istifadəçi adınız, videonu ki
|
||||
|
||||
### Mənim IP ünvanım necə saxlanılır?
|
||||
|
||||
Backend yalnız müvəqqəti yaddaşda (RAM) haşiyələnməmiş IP ünvanlarını saxlayır. Bu ünvanlar sabit diskdə saxlanmır və buna görə də qeyd olunmur. Biz IP ünvanlarını hash edirik və əvəzinə onlar saxlanılır. Bu, verilənlər bazası vandalizminin qarşısını almaq üçün edilir.
|
||||
Server orijinal IP ünvanlarını yalnız operativ yaddaşda (RAM) saxlayır. Sui-istifadənin qarşısını almaq üçün orijinal ünvanların əvəzinə onların heş dəyərlərini saxlayırıq.
|
||||
|
||||
### OAuth vasitəsilə YouTube hesabıma daxil olmaq haqqında bəzi mübahisələr eşitdim!
|
||||
|
||||
|
||||
@@ -17,7 +17,7 @@
|
||||
|
||||
### Как се съхранява моят IP адрес?
|
||||
|
||||
Бекендът държи незакодирани IP адреси само в изменяемата памет (RAM). Те не се съхраняват на твърд диск и следователно не се записват. Ние кодираме IP адресите, и това се съхранява. Това се прави, за да се предотврати вандализмът върху базата данни.
|
||||
Сървърът пази оригиналните IP адреси само в оперативната памет (RAM). Съхраняваме техните хешове вместо оригиналните адреси, за да предотвратяваме злоупотреби.
|
||||
|
||||
### Чух за OAuth и достъп до акаунта ми на YouTube!
|
||||
|
||||
|
||||
@@ -16,7 +16,7 @@
|
||||
|
||||
### كيف يتم تخزين عنوان IP الخاص بي؟
|
||||
|
||||
يحتفظ الخلفية بعناوين IP غير المشفرة في الذاكرة المتطايرة (RAM) فقط. هذه العناوين لا يتم تخزينها على القرص الصلب، وبالتالي لا يتم تسجيلها. نقوم بتشفير عناوين IP، ويتم تخزين هذا التشفير بدلاً من ذلك. يتم ذلك لمنع تخريب قاعدة البيانات.
|
||||
يحتفظ الخادم بعناوين IP الأصلية في ذاكرة RAM فقط. ونخزّن قيم التجزئة (hashes) الخاصة بها بدلاً من العناوين الأصلية، للمساعدة في منع إساءة الاستخدام.
|
||||
|
||||
### سمعت بعض النقاش حول OAuth والوصول إلى حساب YouTube الخاص بي!
|
||||
|
||||
|
||||
@@ -114,9 +114,9 @@ export default {
|
||||
bullet4: "¿Puedo compartir mi contador de «dislikes» con vosotros?",
|
||||
bullet4text:
|
||||
"Próximamente. Estamos investigando en usar Oauth u otra API de solo lectura con alcance limitado para que los creadores puedan compartir sus contadores de «dislikes» verificablemente.",
|
||||
bullet5: "¿Qué datos almacenáis y cómo son guardados?",
|
||||
bullet5: "¿Qué datos tratáis y cómo se gestionan?",
|
||||
bullet5text:
|
||||
'La extensión almacena únicamente aquellos datos estrictamente necesarios para su buen funcionamiento, cómo la dirección IP o el ID del vídeo que estés viendo. Tus datos nunca serán vendidos a terceros. Si quieres saber más sobre nuestras políticas de seguridad y privacidad, consulta nuestro <a href="https://github.com/Anarios/return-youtube-dislike/blob/main/Docs/SECURITY-FAQ.md">documento de preguntas frecuentes sobre seguridad</a>.',
|
||||
'La extensión procesa únicamente aquellos datos estrictamente necesarios para su buen funcionamiento, cómo la dirección IP o el ID del vídeo que estés viendo. Tus datos nunca serán vendidos a terceros. Si quieres saber más sobre nuestras políticas de seguridad y privacidad, consulta nuestro <a href="https://github.com/Anarios/return-youtube-dislike/blob/main/Docs/SECURITY-FAQ.md">documento de preguntas frecuentes sobre seguridad</a>.',
|
||||
bullet6: "¿Cómo funciona la API y el «backend»?",
|
||||
bullet6text:
|
||||
"El «backend» utiliza datos archivados de cuando la API de YouTube seguía proporcionando el contador de «dislikes», los votos de usuarios de la extensión y su extrapolación. En un futuro cercano permitiremos que los creadores de contenido puedan proporcionar sus cifras de «dislikes» de forma fácil y segura, e incorporaremos los datos archivados de ArchiveTeam (4.560 millones de vídeos) en nuestra base de datos. También puedes ver un vídeo al respecto.",
|
||||
|
||||
Reference in New Issue
Block a user