Changes

Jump to: navigation, search

Security/Anti tracking policy

7 bytes removed, 18:23, 28 January 2019
Fix mailto
# Preventing the creation of fraudulent accounts or the completion of fraudulent purchases. For example, a payment processor may examine device properties when processing a payment to determine whether the purchaser is a bot. This allows the payment processor to prevent bots from making purchases with stolen credit cards. Similarly, a captcha provider may use device information to decide whether to prompt users to manually solve a captcha.
In some cases techniques are dual-use, such that they are used both to lower the risk of user harm and for purposes unrelated to user harm, including tracking. We will handle these techniques on a case-by-case basis depending on the potential user harm they create and mitigate. We will consider requests for other classes of exceptions on the basis of whether they serve to address specific user interests or harms. Requests for such exceptions should be directed to [http://mailto:antitracking-policy@mozilla.com antitracking-policy@mozilla.com].
Confirm
25
edits

Navigation menu