Confirmed users
29
edits
Security/Anti tracking policy: Difference between revisions
Jump to navigation
Jump to search
m
Missing word
m (Fixed typo (repeated word)) |
m (Missing word) |
||
| Line 36: | Line 36: | ||
* '''Supercookies.''' This refers to a collection of techniques that involve storing tracking identifiers in areas of the browser that are not cleared when the standards-defined locations are cleared. This allows a tracker to re-establish a tracking identifier after a user or user agent clears storage. For example, a party which uses multiple domains to encode a tracking identifier in HTTPS Strict Transport Security flags would be considered to use supercookies. | * '''Supercookies.''' This refers to a collection of techniques that involve storing tracking identifiers in areas of the browser that are not cleared when the standards-defined locations are cleared. This allows a tracker to re-establish a tracking identifier after a user or user agent clears storage. For example, a party which uses multiple domains to encode a tracking identifier in HTTPS Strict Transport Security flags would be considered to use supercookies. | ||
While this type of tracking is not currently blocked in Firefox, we may apply additional restrictions to the third parties engaged in this type of tracking in future. | While this type of tracking is not currently blocked in Firefox, we may apply additional restrictions to the third parties engaged in this type of tracking in the future. | ||
== Policy circumvention == | == Policy circumvention == | ||