<!--
- Copyright © 2016-2018,2020 Soren Stoutner <soren@stoutner.com>.
+ Copyright © 2016-2018,2020-2021 Soren Stoutner <soren@stoutner.com>.
- Translation 2020 Thiago Nazareno Conceição Silva de Jesus <mochileiro2006-trilhas@yahoo.com.br>. Copyright assigned to Soren Stoutner <soren@stoutner.com>.
+ Translation 2021 Thiago Nazareno Conceição Silva de Jesus <mochileiro2006-trilhas@yahoo.com.br>. Copyright assigned to Soren Stoutner <soren@stoutner.com>.
This file is part of Privacy Browser <https://www.stoutner.com/privacy-browser>.
</head>
<body>
- <h3><svg class="header"><use href="../shared_images/cookie.svg#icon"/></svg> First-Party Cookies</h3>
+ <h3><svg class="header"><use href="../shared_images/cookie.svg#icon"/></svg> Cookies primários</h3>
- <p>First-party cookies are set by the website in the URL bar at the top of the page.</p>
+ <p>Os cookies primários são definidos pelo site na barra de URL na parte superior da 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 it again.</p>
+ <p>Desde os primórdios da Internet, tornou-se óbvio que seria vantajoso para os sites a capacidade de armazenar informações em um computador para acesso futuro.
+ Por exemplo, um site que exibe informações meteorológicas pode solicitar ao usuário um CEP e armazená-lo em um cookie.
+ Na próxima vez que o usuário visitar o site, as informações meteorológicas serão carregadas automaticamente para aquele CEP, sem que o usuário tenha que digitá-lo novamente.</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.</p>
+ <p>Como tudo na web, pessoas inteligentes descobriram todos os tipos de maneiras de abusar dos cookies para fazer coisas que os usuários não aprovariam se soubessem que estavam acontecendo.
+ Por exemplo, um site pode definir um cookie com um número de série exclusivo em um dispositivo.
+ Então, toda vez que um usuário visita o site nesse dispositivo, ele pode ser vinculado a um perfil exclusivo que o servidor mantém para aquele número de série,
+ mesmo se o dispositivo se conectar a partir de endereços IP diferentes.</p>
- <p>Almost all websites with logins require first-party cookies to be enabled for a user to log in.
- That is how they make sure it is still you as you move from page to page on the site, and is, in my opinion, one of the few legitimate uses for cookies.</p>
+ <p>Quase todos os sites com logins exigem que os cookies sejam ativados para o login do usuário.
+ É assim que eles se certificam de que ainda é você conforme você passa de uma página para outra no site, e é, na minha opinião, o único uso legítimo para cookies.</p>
- <p>If first-party cookies are enabled but JavaScript is disabled, the privacy icon will be yellow <img class="inline" src="../shared_images/warning.svg"> as a warning.</p>
+ <p>Se os cookies estiverem habilitados, mas o JavaScript estiver desabilitado, o ícone de privacidade ficará amarelo <img class="inline" src="../shared_images/warning.svg"> como um aviso.</p>
- <h3><svg class="header"><use href="../shared_images/cookie.svg#icon"/></svg> Third-Party Cookies</h3>
+ <h3><svg class="header"><use href="../shared_images/cookie.svg#icon"/></svg> Cookies de terceiros</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/">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>Os cookies de terceiros são definidos por partes de um site que são carregadas de servidores diferentes do URL na barra de endereços.
+ Não há um bom motivo para ativar cookies de terceiros. O Privacy Browser 3.8 removeu a opção e até o Google está planejando
+ <a href="https://www.theverge.com/2020/1/14/21064698/google-third-party-cookies-chrome-two-years-privacy-safari-firefox">desativá-la no futuro</a>.
+ Nos dispositivos com Android KitKat (versão 4.4, API 19), WebView não
+ <a href="https://developer.android.com/reference/android/webkit/CookieManager.html#setAcceptThirdPartyCookies(android.webkit.WebView, boolean)">diferencia entre cookies primários e de terceiros</a>.
+ Assim, habilitar cookies também habilitará cookies de terceiros.</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 their 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>
+ <h3><svg class="header"><use href="../shared_images/web.svg#icon"/></svg> Armazenamento DOM</h3>
- <p>There is 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>
+ <p>O armazenamento do Document Object Model, também conhecido como armazenamento na web, é como cookies com esteróides.
+ Considerando que o tamanho máximo de armazenamento combinado para todos os cookies de um único URL é de 4 kilobytes,
+ O armazenamento DOM pode conter <a href="https://en.wikipedia.org/wiki/Web_storage#Features">megabytes por site</a>.
+ Ao contrário dos cookies, o armazenamento DOM não envia todos os dados nos cabeçalhos com cada solicitação.
+ Em vez disso, ele usa JavaScript para ler e gravar dados, o que significa que não funciona quando o JavaScript está desabilitado.</p>
- <h3><svg class="header"><use href="../shared_images/web.svg#icon"/></svg> DOM Storage</h3>
+ <h3><svg class="header"><use href="../shared_images/subtitles.svg#icon"/></svg> Dados do Formulário</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 <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, it cannot be enabled unless JavaScript is also enabled.</p>
-
-
- <h3><svg class="header"><use href="../shared_images/subtitles.svg#icon"/></svg> 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.
- Beginning in Android Oreo (8.0), WebView’s form data was replaced by the <a href="https://medium.com/@bherbst/getting-androids-autofill-to-work-for-you-21435debea1">Autofill service</a>.
- As such, controls for form data no longer appear on newer Android devices.</p>
+ <p>Os dados do formulário contêm informações digitadas em formulários da web, como nomes de usuário, endereços, números de telefone, etc., e os relaciona em uma caixa suspensa em visitas futuras.
+ Ao contrário de outras formas de armazenamento local, os dados do formulário não são enviados ao servidor da web sem interação específica do usuário.
+ A partir do Android Oreo (versão 8.0, API 26), os dados do formulário WebView foram substituídos pelo
+ <a href="https://medium.com/@bherbst/getting-androids-autofill-to-work-for-you-21435debea1">Autofill service</a>.
+ Como tal, os controles para dados de formulário não aparecem mais em dispositivos Android mais recentes.</p>
</body>
</html>
\ No newline at end of file
projects / PrivacyBrowserAndroid.git / blobdiff