First-Party Cookies First-Party CookiesCookies can be divided into two types. First-party cookies are cookies set by the website in the URL bar at the top of the page.
+ -From the early days of the internet, it became obvious that it would be advantageous for websites to be able to store - information on a computer for future access. For example, a website that displays weather information could ask the - user for a zip code, and then store it in a cookie. The next time the user visited the website, weather information - would automatically load for that zip code, without the user having to enter the zip code, and without the need for - the user to create an account on the website (which would be overkill for such a simple task).
+ + + -Like everything else on the web, clever people figured out all types of ways to abuse cookies to do things that users - would not approve of if they knew they were happening. For example, a website can set a cookie with a unique serial - number on a device. Then, every time a user visits the website on that device, it can be linked to a unique profile - the server maintains for that serial number, even if the device connects from different IP addresses, as cell phones often do.
+ +Some websites with logins require first-party cookies to be enabled for a user to stay logged in. Cookies aren't the only only way - a website can maintain a user logged in as they move from page to page on the site, but if a particular website has chosen to - implement logins in that way, enabling first-party cookies on that site will be the only way to use the functionality.
+Las cookies de primera parte son cookies establecidas por la página web en la barra URL de la parte superior de la página.
-If first-party cookies are enabled but JavaScript is disabled, the privacy icon will be yellow 
- as a warning.
Desde los primeros dÃas de internet, se hizo evidente que serÃa ventajoso para las páginas web el poder almacenar información en un ordenador para un acceso futuro. + Por ejemplo, una página web que muestre información meteorológica podrÃa solicitar al usuario un código postal y luego almacenarlo en una cookie. + La próxima vez que el usuario visite la página web, la información meteorológica se cargará automáticamente para ese código postal, sin que el usuario tenga que volver a introducirlo.
+Como todo en la web, gente inteligente descubrió todo tipo de maneras de abusar de las cookies para hacer cosas que los usuarios no aprobarÃan si supieran que estaban ocurriendo. + Por ejemplo, una página web puede establecer una cookie con un número de serie único en un dispositivo. + Luego, cada vez que un usuario visite la página web con ese dispositivo, puede vincularse a un perfil único que el servidor mantiene para ese número de serie, + incluso si el dispositivo se conecta desde diferentes direcciones IP.
- Third-Party CookiesCasi todas las páginas web con logins requieren que las cookies estén habilitadas para que el usuario pueda iniciar sesión. + Asà es como se aseguran de que sigues siendo tú al pasar de una página a otra de la web, y es, en mi opinión, el único uso legÃtimo de las cookies.
-Third-party cookies are set by portions of a website that are loaded from servers different from the URL at the top of the page. - For example, most website that have advertisements load them from a third-party ad broker, like Google's - Ad Sense. Every time the website loads, it requests the ad - broker to display some ads. The ad broker analyzes any information they may have about the user, looks at the current - rate advertisers are willing to pay for their ads, and selects those to display. The section of the website that displays - the ads is loaded from the third-party broker's server instead of the main server.
+Si las cookies están activadas pero JavaScript está desactivado, el icono de privacidad será amarillo 
como advertencia.
Because most of the advertisements on the internet are displayed from only a few brokers, it didn't take long for them to realize - that they could set a tracking cookie on the user's device and know every place that user goes. Every time an ad loads from a broker, - the first thing it does it check to see if if the device already has a unique serial number in a tracking cookie. If it does, it looks up - the profile for that serial number and makes a note of the new site. This is why a user can do a search on one website for a - product that they typically don't look for, like walnuts, and then suddenly start seeing advertisements for walnuts on every - website they visit.
-In addition to ad brokers, social media sites discovered they could get in on the action. A few years ago, the major social media sites - like Facebook and Twitter convinced a large number of websites that it would be in there best interest to place little social media - icons on their pages. These are not just images. They contain imbedded code that - links back to the social media site, and, among other things, loads a third-party cookie on the device. These cookies are placed even if the user does - not have an account with the social media platform. Over time, companies like Facebook (which also run an ad network) have built up quite a large number - of detailed profiles about people who have never even - created an account on their site.
+There is almost no good reason to ever enable third-party cookies. On devices with Android KitKat or older (version <= 4.4.4 or API <= 20), WebView - does not differentiate - between first-party and third-party cookies. Thus, enabling first-party cookies will also enable third-party cookies.
+Las cookies de terceros son instaladas por partes de un sitio web que se cargan desde servidores diferentes a la URL que aparece en la parte superior de la página. + No hay ninguna buena razón para activar las cookies de terceros. La versión 3.8 de Privacy Browser eliminó la opción, e incluso Google planea + desactivarlas en un futuro.. + En dispositivos con Android KitKat (versión 4.4, API 19), WebView no + distingue entre cookies de origen y de terceros. + Por lo tanto, si se habilitan las cookies, también se habilitarán las de terceros.
-
DOM StorageDocument Object Model storage, also known as web storage, is like cookies on steroids. Whereas the maximum combined storage size for all cookies from - a single URL is 4 kilobytes, DOM storage can hold between 5-25 megabytes per site. - Because DOM storage uses JavaScript to read and write data, enabling it will do nothing unless JavaScript is also enabled.
+El almacenamiento del Modelo de Objetos del Documento, también conocido como almacenamiento web, es como cookies con esteroides. + Mientras que el tamaño máximo de almacenamiento combinado para todas las cookies de una sola URL es de 4 kilobytes, el almacenamiento DOM puede soportar + megabytes por sitio. A diferencia de las cookies, el almacenamiento DOM no envÃa todos los datos de las cabeceras con cada solicitud. + Más bien, utiliza JavaScript para leer y escribir datos, lo que significa que no funciona cuando JavaScript está desactivado.
-
Form DataForm data contains information typed into web forms, like user names, addresses, phone numbers, etc., and lists them in a drop-down box on future visits. - Unlike the other forms of local storage, form data is not sent to the web server without specific user interaction.
- +Los datos de formulario contienen la información introducida en los formularios web, como los nombres de los usuarios, las direcciones, los números de teléfono, etc., + y los listan en un cuadro desplegable en futuras visitas. + A diferencia de las otras formas de almacenamiento local, los datos de los formularios no se envÃan al servidor web sin una interacción especÃfica del usuario. + A partir de Android Oreo (versión 8.0, API 26), los datos de formulario de WebView fueron sustituidos por el + servicio Autofill o Autorelleno. + Por ello, los controles para los datos de los formularios ya no aparecen en los dispositivos Android más nuevos.
+ \ No newline at end of file