<!--
- Copyright 2016-2017 Soren Stoutner <soren@stoutner.com>.
+ Copyright © 2017-2018,2020-2022 Soren Stoutner <soren@stoutner.com>.
- This file is part of Privacy Browser <https://www.stoutner.com/privacy-browser>.
+ Translation 2017-2018,2021 Francesco Buratti. Copyright assigned to Soren Stoutner <soren@stoutner.com>.
- Privacy Browser is free software: you can redistribute it and/or modify
+ This file is part of Privacy Browser Android <https://www.stoutner.com/privacy-browser-android>.
+
+ Privacy Browser Android 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.
- Privacy Browser is distributed in the hope that it will be useful,
+ Privacy Browser Android 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.
You should have received a copy of the GNU General Public License
- along with Privacy Browser. If not, see <http://www.gnu.org/licenses/>. -->
+ along with Privacy Browser Android. If not, see <http://www.gnu.org/licenses/>. -->
<html>
<head>
- <style>
- h3 {
- color: 0D4781;
- }
-
- 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>
+ <meta charset="UTF-8">
- <p>First-party cookies are set by the website in the URL bar at the top of the page.</p>
+ <link rel="stylesheet" href="../css/theme.css">
- <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>
+ <!-- Setting the color scheme instructs the WebView to respect `prefers-color-scheme` @media CSS. -->
+ <meta name="color-scheme" content="light dark">
+ </head>
- <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>
+ <body>
+ <h3><svg class="header"><use href="../shared_images/cookie.svg#icon"/></svg> Cookies proprietari</h3>
- <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>I cookies proprietari sono definiti dal sito web nella barra della URL all'inizio della pagina.</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>Fin dagli albori di internet divenne ovvio che sarebbe stato molto utile per i siti web essere in grado di salvare informazioni sui computer per eventuali accessi successivi.
+ Ad esempio, un sito web che fornisca informazioni meteo potrebbe chiedere all'utente la sua posizione geografica e salvarla in un cookie.
+ Nel caso di un accesso successivo al sito web da parte dell'utente, le informazioni meteo sarebbero quindi caricate in automatico per quella posizione geografica,
+ senza che si renda necessario per l'utente indicarla nuovamente.</p>
+ <p>Come per quasi ogni cosa sul web, persone intelligenti hanno ideato moltissimi modi per abusare dei cookies e usarli per finalità che gli utenti non approverebbero,
+ se solo sapessero cosa sta succedendo. Ad esempio, un sito web può salvare su un dispositivo un cookie con un numero seriale univoco.
+ In questo modo, ogni volta che l'utente visiterà il sito da quel dispositivo, sarà collegato ad un profilo unico mantenuto sul server per quel particolare numero seriale,
+ anche se il dispositivo si connette con indirizzo IP diverso.</p>
- <h3><img class="title" src="../en/images/cookie_dark_blue.png"> Third-Party Cookies</h3>
+ <p>Quasi tutti i siti web con login richiedono che i cookies siano abilitati perché l'utente possa accedere.
+ E' questo il metodo che utilizzano per essere sicuri che sia sempre lo stesso utente che si sposta da una pagina all'altra del sito ed è, a nostro parere, l'unico utilizzo legittimo dei cookies.</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>Se i cookies sono abilitati ma JavaScript è disabilitato, l'icona della privacy sarà gialla <img class="inline" src="../shared_images/warning.svg"> come avvertimento.</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/">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/cookie.svg#icon"/></svg> Cookies di terze parti</h3>
- <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>
+ <p>I cookies di terze parti sono impostati da porzioni di un sito web che sono caricate da server diversi dalla URL in cima alla pagina web.
+ Non esiste mai alcuna ragione valida per abilitare i cookies di terze parti. Privacy Browser 3.8 ha rimosso questa opzione, e anche Google sta pianificando di
+ <a href="https://www.theverge.com/2020/1/14/21064698/google-third-party-cookies-chrome-two-years-privacy-safari-firefox">disabilitarli in futuro</a>.
+ Sui dispositivi con Android KitKat (versione 4.4, API 19), WebView non
+ <a href="https://developer.android.com/reference/android/webkit/CookieManager.html#setAcceptThirdPartyCookies(android.webkit.WebView, boolean)">fa distinzione
+ tra i cookies proprietari e i cookies di terze parti</a>. In questo modo abilitare i cookies significa abilitare anche quelli di terze parti.</p>
- <h3><img class="title" src="../en/images/ic_web_dark_blue.png"> DOM Storage</h3>
+ <h3><svg class="header"><use href="../shared_images/web.svg#icon"/></svg> 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 <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>
+ <p>Il Document Object Model storage, conosciuto anche come web storage, è come se fossero i cookies con gli steroidi.
+ Laddove la massima dimensione di memeoria utilizzata da tutti i cookies di una singola URL è di 4 kilobyte, il DOM storage può memorizzare anche
+ <a href="https://en.wikipedia.org/wiki/Web_storage#Features">alcuni megabyte per ogni sito</a>.
+ A differenza dei cookies, il DOM storage non invia tutti i dati nelle intestazioni con ogni richiesta.
+ Al contrario utilizza JavaScript per leggere e scrivere i dati, il che significa che non può funzionare se JavaScript è disabilitato.</p>
- <h3><img class="title" src="../en/images/ic_subtitles_dark_blue.png"> Form Data</h3>
+ <h3><svg class="header"><use href="../shared_images/subtitles.svg#icon"/></svg> Dati dei moduli</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>
+ <p>I dati dei moduli contengono informazioni che sono digitate nei web forms, come il nome dell'utente, gli indirizzi, numeri di telefono, ecc.,
+ e li elenca in un menù a tendina in caso di accessi futuri.
+ A differenza delle altre modalità di memorizzazione locale, i dati dei moduli non vengono inviati ai web server senza che ci sia una interazione con l'utente.
+ A partire da Android Oreo (versione 8.0, API 26), i dati dei moduli di WebView sono stati sostituiti dal
+ <a href="https://medium.com/@bherbst/getting-androids-autofill-to-work-for-you-21435debea1">servizio Autofill</a>.
+ Per questo motivo i controlli dei dati dei moduli non sono presenti nei dispositivi Android più recenti.</p>
</body>
</html>
\ No newline at end of file