Skip to content

Update Protection to clarify user control and access protection #9

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

Open
wants to merge 10 commits into
base: main
Choose a base branch
from
36 changes: 19 additions & 17 deletions index.bs
Original file line number Diff line number Diff line change
Expand Up @@ -78,23 +78,25 @@ and embodied in the various standards that user agents implement.
## Protection ## {#protection}

[[design-principles#safe-to-browse|It should be safe to visit a web page.]]
That is, simply visiting a page must not allow
the page to make permanent changes to the user's computer or environment
(for example by installing malware),
and simply visiting should reveal
as little information as practical about the user to the page,
to the user's environment,
and to any other interested actor.

Users can opt into sharing more information with a page they visit,
for example by entering or auto-filling data into form fields,
or granting permissions to the page.
Users can also allow the page to make changes to their environment,
for example by installing native programs that the page offers.
Even in these cases,
user agents should strive to prevent pages from tricking their users
and should help their users notice
when they might be giving the page more power than they intended.
Specifically, visiting a page must not allow it to make changes to the user's computer or environment,
such as installing software, accessing hardware,
or exposing sensitive information without clear user intent.
Additionally, user agents must prevent web pages from tracking individuals unless they have explicitly enabled it.

Choose a reason for hiding this comment

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

New pgf here for the new concept? Privacy and host security are pretty distinct ideas. I'd almost reorder the entire section on that basis (deal with host security stuff with pgf 1 part 1 and pgf 3; then deal with privacy with pgf 1 part 2 and pgf 2...

Any data shared should be as little information as practical,
only what is needed to achieve the individual's goals,
and consistent with their preferences and safety,
in alignment with [data minimization](https://www.w3.org/TR/design-principles/#data-minimization) principles.

Users can [choose to share more information](https://www.w3.org/TR/privacy-principles/#dfn-opt-in),
whether by entering data, allowing auto-fill,
or granting permissions.
User agents should prevent pages from tricking their users
and help them notice when they may give the page more control than intended.

Access to the user's local environment, such as local files,
should be strictly limited and only allowed when the user clearly intends to provide access.
This should occur through direct user actions,
with clear warnings to prevent accidental exposure of data.


## Honesty ## {#honesty}
Expand Down