Repository navigation
Report Delivery #194
Description
That said, a user agent SHOULD make a effort to deliver reports as soon as possible after queuing, as a report’s data might be significantly more useful in the period directly after its generation than it would be a day or a week later.
It seems there's privacy implications here that ought to be called out. As reporting later would reveal new things about the user.
Activity
clelland commentedon Mar 5, 2021
Besides knowing that the user had been on the page for a day (or a week,) which is pretty trivial for a site to know, are there other categories of info that you'd find specifically concerning?
The text there was originally in the "v0" spec, which didn't tie reports to the page lifetime. Since we're doing that now, the only way that a report can be delayed that much would be if the user kept the page open for that long. If a reporting implementation were to delay all reports, for instance, until the page was unloaded, would you see that as problematic, privacy-wise?
annevk commentedon Mar 9, 2021
I think (it's been a while) I was thinking more about the case where the user has closed the document, but the user agent decides to not do reporting until shutdown or some such.
yoavweiss commentedon Sep 14, 2022
@clelland - Is the behavior that @annevk talks about something that's still specified in Reporting?