Changes

We will not block specific uses of the techniques practices described above when they are used to lower the risk of specific user harmparty using them is classified as a tracker. The following use cases are permissible under this policyWe [https: # Improving the security of client authentication//wiki. For example, a website may save device configuration details after a user logs in to determine when an unexpected device attempts to login at a future datemozilla. By doing so, the site mitigates the risk of unauthorized access to a user’s accountorg/index.php?title=Security/Anti_tracking_policy&diff=1214837&oldid=1214836# Preventing the creation Policy_Exceptions previously offered] a set 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 exceptions independent 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-usetracker classification, such that they are used both to lower the risk but as of user harm and for purposes unrelated to user harmJuly 9, including tracking2019 we will no longer grant new exceptions. We will handle these techniques on a case-by-case basis depending on stop honoring the potential user harm they create and mitigate. We will consider requests for other classes current set of exceptions on the basis in a future version of whether they serve to address specific user interests or harms. Requests for such exceptions should be directed to [mailto:antitracking-policy@mozilla.com antitracking-policy@mozilla.com]Firefox.