Closed Bug 1539536 Opened 6 months ago Closed 5 months ago

Content Blocking measurements using Prio

Categories

(Core :: Privacy: Anti-Tracking, enhancement, P1)

enhancement

Tracking

()

RESOLVED FIXED
mozilla68
Tracking Status
firefox68 --- fixed

People

(Reporter: xeonchen, Assigned: xeonchen)

References

Details

Attachments

(2 files, 1 obsolete file)

For a random sample of users of 1% of the release population, when a page is unloaded, randomly choose with probability p whether to send the following information for all trackers (for each page unload we either report all three points for all trackers, or report nothing):

  1. Was tracker X blocked on this page?
  2. Did tracker X receive an exception from our heuristics on this page?
  3. Did tracker X receive an exception from the Storage Access API on this page?
Blocks: 1522657
No longer blocks: 1522657
See Also: → 1522657, 1539641

The class |ContentBlockingLog| is header-only and it takes forever to re-build even if you make a little piece modification. This patch moves most of them into a newly created source file to avoid this condition.

Attachment #9055127 - Attachment is obsolete: true

randomly choose 1% users and their 0.14% page view to measure content blocking.

Attachment #9055814 - Flags: feedback?(senglehardt)
Attached file request.md
Attachment #9056663 - Flags: data-review?(chutten)
Comment on attachment 9056663 [details]
request.md

DATA COLLECTION REVIEW RESPONSE:

    Is there or will there be documentation that describes the schema for the ultimate data set available publicly, complete and accurate?

Yes. This collection is Origin Telemetry and is documented in its documentation: https://firefox-source-docs.mozilla.org/toolkit/components/telemetry/telemetry/collection/origin.html

    Is there a control mechanism that allows the user to turn the data collection on and off?

Yes. This collection is Telemetry so can be controlled through Firefox's Preferences.

    If the request is for permanent data collection, is there someone who will monitor the data over time?

No. This collection will expire in 6 months.

    Using the category system of data types on the Mozilla wiki, what collection type of data do the requested measurements fall under?

Category 3, Web activity. Pursuant to bug 1525008, Prio is an acceptable mitigation to allow this to be collected.

    Is the data collection request for default-on or default-off?

Default on for all channels. (Though there are at present only plans as far as Beta for this collection, and we are currently pref'd to only Nightly)

    Does the instrumentation include the addition of any new identifiers?

No.

    Is the data collection covered by the existing Firefox privacy notice?

Yes.

    Does there need to be a check-in in the future to determine whether to renew the data?

Yes. :xeonchen is responsible for renewing or removing the collection within the next six months.

---
Result: datareview+ (please file a follow-up bug to remove or renew the collection by October 8, 2019)
Attachment #9056663 - Flags: data-review?(chutten) → data-review+
Attachment #9055814 - Flags: feedback?(senglehardt) → feedback+
See Also: → 1543506
Blocks: 1543712
Pushed by xeonchen@gmail.com:
https://hg.mozilla.org/integration/autoland/rev/527df4f1c60d
implement content blocking measurements using prio; r=Ehsan,englehardt
Status: ASSIGNED → RESOLVED
Closed: 5 months ago
Resolution: --- → FIXED
Depends on: 1544598
You need to log in before you can comment on or make changes to this bug.