Skip to content

Add privacy considerations related to legal processes and coercion #1504

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

Merged
merged 4 commits into from
Jun 26, 2024

Conversation

msporny
Copy link
Member

@msporny msporny commented Jun 19, 2024

This PR is an attempt to address issue #1502 by adding a few more privacy considerations related to legal processes and coercion.

/cc @zoracon


Preview | Diff

@msporny msporny requested a review from selfissued as a code owner June 19, 2024 20:38
@msporny msporny added editorial Purely editorial changes to the specification. CR1 This item was processed during CR1 labels Jun 19, 2024
Copy link
Contributor

@longpd longpd left a comment

Choose a reason for hiding this comment

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

The phrasing "such that a [=holder=] can push back on the over-collection of information that is unnecessary for the transaction." I presume means the holder can decline to share specific information requested. Is that what this implies? If so, then saying that explicitly would be better.

@msporny
Copy link
Member Author

msporny commented Jun 20, 2024

I presume means the holder can decline to share specific information requested. Is that what this implies? If so, then saying that explicitly would be better.

Yes, that's what was meant, your text is more clear. I'll update the PR to use your text, thanks @longpd !

Copy link

@zoracon zoracon left a comment

Choose a reason for hiding this comment

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

The phrasing and changes overall address my initial concerns about addressing law enforcement, coercion, and the unreliability of private browsing.

@msporny
Copy link
Member Author

msporny commented Jun 26, 2024

Editorial, multiple reviews, changes requested and made, no objections, merging.

@msporny msporny merged commit 581e7d2 into main Jun 26, 2024
1 check passed
@msporny msporny deleted the msporny-priv-updates branch June 26, 2024 23:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CR1 This item was processed during CR1 editorial Purely editorial changes to the specification.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

10 participants