Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update Privacy section to clarify network change #29

Merged
merged 3 commits into from
Sep 14, 2022
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
26 changes: 18 additions & 8 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@

Authors: [Darren Willis](https://github.com/darrenw), [Fergal Daly](https://github.com/fergald), [Ming-Ying Chung](https://github.com/mingyc) - Google

[![Super-Linter](https://github.com/WICG/unload-beacon/workflows/linter.yml/badge.svg)](https://github.com/WICG/unload-beacon/actions/workflows/super-linter.yml)
[![Super-Linter](https://github.com/WICG/unload-beacon/workflows/Lint%20Code%20Base/badge.svg)](https://github.com/WICG/unload-beacon/actions/workflows/super-linter.yml)
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

seems like it shouldn't be in this change.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry this is already commited to main branch. Not sure how to remove it from this PR but should be no-op on merging.

[![Spec Prod](https://github.com/WICG/unload-beacon/actions/workflows/auto-publish.yml/badge.svg)](https://github.com/WICG/unload-beacon/actions/workflows/auto-publish.yml)


Expand Down Expand Up @@ -304,16 +304,26 @@ special support may be needed to allow extension authors to block the sending (o

Specifically, beacons will have the following privacy requirements:

* Beacons must be sent over HTTPS.
* Beacons are only sent over the same network that was active when the beacon was registered
(e.g. if the user goes offline and moves to a new network, discard pending beacons).
* Delete pending beacons for a site if a user clears site data.
* Beacons registered in an incognito session do not persist to disk.
* Follow third-party cookie rules for beacons.
* Post-unload beacons are not sent if background sync is disabled for a site.
* If a page is suspended (for instance, as part of a [bfcache](https://web.dev/bfcache/)),
beacons should be sent within 10 minutes or less of suspension,
* [#30] Beacons must not leak navigation history to the network provider that it should not know.
* If network changes after a page is navigated away, i.e. put into bfcache, the beacon should not be sent through the new network;
If the page is then restored from bfcache, the beacon can be sent.
* If this is difficult to achieve, consider just force sending out all beacons on navigating away.
* [#27]\[TBD\] Beacons must be sent over HTTPS.
* [#34]\[TBD\] Crash Recovery related (if implemented):
* Delete pending beacons for a site if a user clears site data.
* Beacons registered in an incognito session do not persist to disk.
* [#3] If a page is suspended (for instance, as part of a [bfcache]),
beacons should be sent within 30 minutes or less of suspension,
to keep the beacon send temporally close to the user's page visit.
Note that beacons lifetime is also capped by the browser's bfcache implementation.

[#3]: https://github.com/WICG/unload-beacon/issues/3
[#27]: https://github.com/WICG/unload-beacon/issues/27
[#30]: https://github.com/WICG/unload-beacon/issues/30
[#34]: https://github.com/WICG/unload-beacon/issues/34
[bfcache]: https://web.dev/bfcache/

## Alternatives Considered

Expand Down
Loading