<!--
- Copyright 2016 Soren Stoutner <soren@stoutner.com>.
+ Copyright 2016-2017 Soren Stoutner <soren@stoutner.com>.
This file is part of Privacy Browser <https://www.stoutner.com/privacy-browser>.
along with Privacy Browser. If not, see <http://www.gnu.org/licenses/>. -->
<html>
-<head>
- <style>
- h3 {
- color: 0D4781;
- }
+ <head>
+ <style>
+ h3 {
+ color: 0D4781;
+ }
- img.title {
- vertical-align: bottom;
- height: 32;
- width: 32;
- }
- </style>
-</head>
+ img.title {
+ vertical-align: bottom;
+ height: 32;
+ width: 32;
+ }
+ </style>
+ </head>
-<body>
-<h3><img class="title" src="images/cookie_dark_blue.png"> First-Party Cookies</h3>
+ <body>
+
<h3><img class="title" src="images/cookie_dark_blue.png"> First-Party Cookies</h3>
-<p>Cookies 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.</p>
+ <p>First-party cookies are set by the website in the URL bar at the top of the page.</p>
-<p>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).</p>
+
<p>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).</p>
-<p>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.</p>
+
<p>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.</p>
-<p>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.</p>
+ <p>Many websites with logins require first-party cookies to be enabled for a user to stay logged in. Cookies aren’t the 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.</p>
-<p>If first-party cookies are enabled but JavaScript is disabled, the privacy icon will be yellow <img src="images/warning.png" height="16" width="16">
- as a warning.</p>
+
<p>If first-party cookies are enabled but JavaScript is disabled, the privacy icon will be yellow <img src="images/warning.png" height="16" width="16">
+ as a warning.</p>
-<h3><img class="title" src="images/cookie_dark_blue.png"> Third-Party Cookies</h3>
+
<h3><img class="title" src="images/cookie_dark_blue.png"> Third-Party Cookies</h3>
-<p>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
- <a href="https://www.google.com/adsense/start/#?modal_active=none">Ad Sense</a>. 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.</p>
+
<p>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
+
<a href="https://www.google.com/adsense/start/#?modal_active=none">Ad Sense</a>. Every time the website loads, it requests the ad
+ broker to display an ad. 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 the one 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.</p>
-<p>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.</p>
+ <p>Because most of the advertisements on the internet are processed by 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 they typically don’t look for, like walnuts, and then suddenly start seeing advertisements for walnuts on every
+ website they visit.</p>
-<p>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 <a href="https://developers.facebook.com/docs/plugins/like-button/">imbedded code</a> 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 <a href="http://www.theverge.com/2016/5/27/11795248/facebook-ad-network-non-users-cookies-plug-ins">never even
- created an account on their site</a>.</p>
+
<p>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 <a href="https://developers.facebook.com/docs/plugins/like-button/">embedded code</a> 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 runs an ad network) have built up quite a large number
+
of detailed profiles about people who have <a href="http://www.theverge.com/2016/5/27/11795248/facebook-ad-network-non-users-cookies-plug-ins">never even
+ created an account on their site</a>.</p>
-<p>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 <a href="https://developer.android.com/reference/android/webkit/CookieManager.html#acceptThirdPartyCookies(android.webkit.WebView)">differentiate
- between first-party and third-party cookies</a>. Thus, enabling first-party cookies will also enable third-party cookies.</p>
+ <p>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 <a href="https://developer.android.com/reference/android/webkit/CookieManager.html#setAcceptThirdPartyCookies(android.webkit.WebView, boolean)">differentiate
+ between first-party and third-party cookies</a>. Thus, enabling first-party cookies will also enable third-party cookies.</p>
-<h3><img class="title" src="images/ic_web_dark_blue.png"> DOM Storage</h3>
+
<h3><img class="title" src="images/ic_web_dark_blue.png"> DOM Storage</h3>
-<p>Document 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 <a href="https://en.wikipedia.org/wiki/Web_storage#Storage_size">5-25 megabytes per site</a>.
- Because DOM storage uses JavaScript to read and write data, enabling it will do nothing unless JavaScript is also enabled.</p>
+
<p>Document 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 <a href="https://en.wikipedia.org/wiki/Web_storage#Storage_size">megabytes per site</a>.
+ Because DOM storage uses JavaScript to read and write data, enabling it will do nothing unless JavaScript is also enabled.</p>
-<h3><img class="title" src="images/ic_subtitles_dark_blue.png"> Form Data</h3>
+
<h3><img class="title" src="images/ic_subtitles_dark_blue.png"> Form Data</h3>
-<p>Form 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.</p>
-</body>
+
<p>Form 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.</p>
+ </body>
</html>
\ No newline at end of file
<!--
- Copyright 2016 Soren Stoutner <soren@stoutner.com>.
+ Copyright 2016-2017 Soren Stoutner <soren@stoutner.com>.
- This file is part of Privacy Browser <https://www.stoutner.com/privacy-browser>.
+ Translation 2017 Jose A. León Becerra. Copyright assigned to Soren Stoutner <soren@stoutner.com>.
- Privacy Browser is free software: you can redistribute it and/or modify
- it under the terms of the GNU General Public License as published by
- the Free Software Foundation, either version 3 of the License, or
- (at your option) any later version.
+ Este archivo es parte de Navegador Privado (Privacy Browser) <https://www.stoutner.com/privacy-browser>.
- Privacy Browser is distributed in the hope that it will be useful,
- but WITHOUT ANY WARRANTY; without even the implied warranty of
- MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
- GNU General Public License for more details.
+ Navegador Privado (Privacy Browser) es software libre: puedes redistribuirlo y/o modificarlo
+ bajo los términos de la Licencia Pública General GNU, como se ha publicado por
+ la Fundación del Software Libre, tanto la versión 3 de la Licencia, o
+ (a su opción) cualquier versión posterior.
- You should have received a copy of the GNU General Public License
- along with Privacy Browser. If not, see <http://www.gnu.org/licenses/>. -->
+ Navegador Privado (Privacy Browser) es distribuído con la esperanza de que será útil,
+ pero SIN NINGUNA GARANTÍA; ni siquiera la garantía implícita de
+ MERCANTILIDAD o APTITUD PARA UN PROPÓSITO PARTICULAR. Vea la
+ Licencia Pública General para más detalles.
+
+ Usted debería haber recibido una copia de la Licencia Pública General GNU
+ junto con Navegador Privado (Privacy Browser). Si no es así, vea <http://www.gnu.org/licenses/>. -->
<html>
-<head>
- <style>
- h3 {
- color: 0D4781;
- }
+ <head>
+ <style>
+ h3 {
+ color: 0D4781;
+ }
- img.title {
- vertical-align: bottom;
- height: 32;
- width: 32;
- }
- </style>
-</head>
+ img.title {
+ vertical-align: bottom;
+ height: 32;
+ width: 32;
+ }
+ </style>
+ </head>
-<body>
-<h3><img class="title" src="../en/images/cookie_dark_blue.png"> First-Party Cookies</h3>
+ <body>
+ <h3><img class="title" src="../en/images/cookie_dark_blue.png"> Cookies de primera parte</h3>
-<p>Cookies 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.</p>
+ <p>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.</p>
-<p>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).</p>
+ <p>Desde los primeros días de internet se hizo obvio que sería algo ventajoso para las páginas web el poder guardar información en un ordenador para un acceso futuro. Por ejemplo,
+ una página web que muestra información del tiempo podría preguntar al usuario por un código postal, y luego guardarlo en una cookie. La próxima vez que el usuario visitara la
+ página web, la información del tiempo sería automáticamente cargada para ese código postal, sin que el usuario tenga que poner su código postal, y sin la necesidad por parte del usuario
+ de crear una cuenta en la página web (que sería excesivo para una tarea tan simple).</p>
-<p>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.</p>
+ <p>Como todo lo demás en la web, gente inteligente averiguó todas las formas de abusar de las cookies para hacer cosas que los usuarios no aprobarían si supieran que están 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 el usuario visite la página web con ese dispositivo, puede ser
+ vinculado a un perfil único, incluso si el dispositivo se conecta desde direcciones IP diferentes, como a menudo hacen los teléfonos celulares.</p>
-<p>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.</p>
+ <p>Muchas páginas web con inicios de sesión requieren que sean habilitadas las cookies de primera parte para que un determinado usuario siga conectado en dicha sesión. Las cookies no
+ son la única forma en que una página web puede mantener conectado en una sesión a un usuario mientras se mueve de una página a otra en ese sitio web, pero si una página web en particular
+ ha elegido implementar inicios de sesión de esa manera, la única forma de poder usar la funcionalidad de ese sitio web será habilitando cookies de primera parte.</p>
-<p>If first-party cookies are enabled but JavaScript is disabled, the privacy icon will be yellow <img src="../en/images/warning.png" height="16" width="16">
- as a warning.</p>
+ <p>Si las cookies de primera parte están habilitadas pero Javascript está deshabilitado, el icono de privacidad será amarillo <img src="../en/images/warning.png" height="16" width="16"> como advertencia.</p>
-<h3><img class="title" src="../en/images/cookie_dark_blue.png"> Third-Party Cookies</h3>
+ <h3><img class="title" src="../en/images/cookie_dark_blue.png"> Cookies de terceras partes</h3>
-<p>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
- <a href="https://www.google.com/adsense/start/#?modal_active=none">Ad Sense</a>. 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.</p>
+ <p>Las cookies de terceras partes son establecidas por ciertas partes de una página web que son cargadas desde servidores diferentes a la URL de la parte superior de la página. Por ejemplo,
+ la mayoría de páginas web que tienen anuncios los cargan desde una compañía de publicidad de terceros, como <a href="https://www.google.com/adsense/start/#?modal_active=none">Ad Sense</a>
+ de Google. Cada vez que se carga la página web, solicita a la compañía de publicidad que muestre un anuncio. La compañía de publicidad analiza cualquier información que pueda tener sobre el usuario,
+ analiza la tasa actual que los anunciantes están dispuestos a pagar por sus anuncios, y selecciona uno para mostrar. La sección de la página web que muestra los anuncios es cargada desde el servidor
+ de la compañía de terceros en vez de hacerlo desde el servidor principal.</p>
-<p>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.</p>
+ <p>Ya que la mayoría de los anuncios en internet se muestran desde solo unas pequeñas compañías, no les llevó a éstas mucho tiempo en darse cuenta que podrían establecer una cookie de seguimiento
+ en el dispositivo del usuario y así conocer cualquier lugar al que el usuario va. Cada vez que un anuncio se carga desde una compañía, lo primero que hace es comprobar si el dispositivo ya tiene un
+ único número de serie en una cookie de seguimiento. Si es así, busca el perfil para ese número de serie y toma nota del nuevo sitio web. Es por esto que un usuario puede hacer una búsqueda en
+ una página web por un producto que normalmente no busca, como nueces, y luego de pronto empieza a ver anuncios de nueces en cada página web que visita.</p>
-<p>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 <a href="https://developers.facebook.com/docs/plugins/like-button/">imbedded code</a> 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 <a href="http://www.theverge.com/2016/5/27/11795248/facebook-ad-network-non-users-cookies-plug-ins">never even
- created an account on their site</a>.</p>
+ <p>Además de compañías de publicidad, las páginas de redes sociales descubrieron que también podían entrar en acción. Hace unos pocos años, las principales páginas de redes sociales
+ como Facebook y Twitter convencieron a un gran número de páginas web que sería por su mejor interés colocar pequeños iconos de redes sociales en sus páginas. Éstos no son sólo imágenes.
+ Contienen <a href="https://developers.facebook.com/docs/plugins/like-button/">código incrustado</a> que enlazan de nuevo a la web de la red social, y entre otras cosas cargan una cookie de terceras partes en el dispositivo.
+ Estas cookies se colocan aunque el usuario no tenga una cuenta con la plataforma de la red social. A través del tiempo, compañías como Facebook (la cual también corre una red de anuncios) han construído un gran
+ número de perfiles detallados sobre personas que <a href="http://www.theverge.com/2016/5/27/11795248/facebook-ad-network-non-users-cookies-plug-ins">ni siquiera han creado una cuenta en su web</a>.
-<p>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 <a href="https://developer.android.com/reference/android/webkit/CookieManager.html#acceptThirdPartyCookies(android.webkit.WebView)">differentiate
- between first-party and third-party cookies</a>. Thus, enabling first-party cookies will also enable third-party cookies.</p>
+ <p>Prácticamente no existe una buena razón por la cual se deban habilitar las cookies de terceras partes. En dispositivos con Android KitKat o más antiguos (versión <= 4.4.4 o API <= 20). WebView no
+ <a href="https://developer.android.com/reference/android/webkit/CookieManager.html#acceptThirdPartyCookies(android.webkit.WebView)">diferencia entre cookies de primera parte y de terceras partes</a>. Así que habilitando las cookies de
+ primera parte se habilitarán también las de terceras partes.</p>
-<h3><img class="title" src="../en/images/ic_web_dark_blue.png"> DOM Storage</h3>
+ <h3><img class="title" src="../en/images/ic_web_dark_blue.png"> Almacenamiento DOM</h3>
-<p>Document 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 <a href="https://en.wikipedia.org/wiki/Web_storage#Storage_size">5-25 megabytes per site</a>.
- Because DOM storage uses JavaScript to read and write data, enabling it will do nothing unless JavaScript is also enabled.</p>
+ <p>El almacenamiento Modelo de Objeto de Documento (Document Object Model), también conocido como almacenamiento web, es como cookies en esteroides. Mientras el tamaño de almacenamiento combinado máximo para todas las cookies
+ de una única URL es de 4 kilobytes, el almacenamiento DOM puede tener <a href="https://en.wikipedia.org/wiki/Web_storage#Storage_size">megabytes por sitio web</a>. Debido a que el almacenamiento DOM usa Javascript para leer y escribir
+ los datos, habilitarlo no hará nada a menos que Javascript sea habilitado también.</p>
-<h3><img class="title" src="../en/images/ic_subtitles_dark_blue.png"> Form Data</h3>
+ <h3><img class="title" src="../en/images/ic_subtitles_dark_blue.png"> Datos de formulario</h3>
-<p>Form 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.</p>
-</body>
+ <p>Los datos de formulario contienen información escrita en formularios web, como nombres de usuario, direcciones, números de teléfono, etcétera, y los enumera en un cuadro desplegable en futuras visitas.
+ A diferencia de las otras formas de almacenamiento local, los datos de formulario no son enviados al servidor web sin una interacción específica del usuario.</p>
+ </body>
</html>
\ No newline at end of file
projects / PrivacyBrowserAndroid.git / commitdiff