Reporting

[neilstuartcraig]

Hi I just watched @maudnals (excellent!) talk from Chrome Dev Summit and was wondering if there will be a reporting (using the Reporting API) mechanism so website operators can learn when the privacy budget is exceeded? I think this would be vital, otherwise website owners won't know when their changes trigger violations, i am thinking especially of adverts and other 3rd party content which the website operator can't easily necessarily themselves. Ideally the report would have some way of identifying the source (origin/caller etc.) of the violation to help triage what needs to be fixed. Cheers

[maudnals]

Hi @neilstuartcraig, great, thank you for watching and for your input on this! A reporting mechanism (either via the Reporting API or via an another mechanism, e.g. a specific privacy budget reporting mode) sounds very useful, especially for the reasons you're mentioning: in the current privacy model proposal, a site's budget is also shared with its third-party content. I also talked with @asankah, engineer on the privacy budget. He is supportive of this idea. We're still at an early stage, but the idea of reporting could be explored in future iterations of the proposal, e.g. when designing the enforcement mechanisms for the privacy budget. +Developer tooling should also go along with this, though this is browser-specific :)