Comments/Suggestions on Privacy Considerations

[zoracon]

For 8.19 Private Browsing

It is my suggestion that Private browsing should not be relied on at all and implementers should be aware that all major browsers support modern mechanisms like Encrypted Client Hello and secure DNS. And they should utilize these modern data transport tools to ensure that Holder metadata and PII transferred over the wire be protected from leaks.

I don't see anything addressing law enforcement access and believe that should be addressed under Privacy.

For 8.16 Data Theft

Alternatives include keeping logs that the information was collected and checked, as well as random tests to ensure that compliance regimes are operating as expected.

I would like to see a note addressing compliance regimes have guidelines on law enforcement access whose terms of access are transparent to the Holder in case of situations like a warrant is issued.

IRL Example: https://www.404media.co/hacker-accesses-internal-tile-tool-that-provides-location-data-to-cops/

For 8.9 The Principle of Data Minimization

such that a holder can push back on the over-collection of information that is unnecessary for the transaction.

In the case where a Holder was coerced into giving more info than desired to a Verifier, there should be a log of what items were disclosed available locally to the user (They can choose to not have this done/opt out/ etc.) for future accountability measures.

[msporny]

Thank you for those suggestions @zoracon. I will take an action to write up a PR to address each concern you raised above with some spec text for you and the Working Group to review.

[iherman]

The issue was discussed in a meeting on 2024-06-19

• no resolutions were taken

View the transcript

2.6. Comments/Suggestions on Privacy Considerations (issue vc-data-model#1502)

See github issue vc-data-model#1502.

Manu Sporny: 1502 is important because of submission from Electronic Frontier Foundation.
… Happy to raise a PR to address the issue.
… Shouldn't only depend on private browsing mode, also want things to ensure that compliance regimes have guidelines about law enforcement access and that they are transparent to the holder.
… Also want logs that wallets would keep so that holder could see what was shared.
… No objections from group to Manu taking on PR.

[iherman]

The issue was discussed in a meeting on 2024-06-19

• no resolutions were taken

View the transcript

2.4. Comments/Suggestions on Privacy Considerations (issue vc-data-model#1502)

See github issue vc-data-model#1502.

Brent Zundel: Next is 1502, comments/suggestions on privacy considerations.
… Manu has assigned himself to raise a PR.
… May have lost Manu, not on Zoom anymore. Just editorial changes.

[msporny]

PR #1504 has been raised to address this issue. @zoracon, it would be good to get your feedback on that PR in the next 7 days, which is our typical merge window. This issue will be closed once PR #1504 has been merged.

[mccown]

Great suggestions.

[iherman]

The issue was discussed in a meeting on 2024-06-26

• no resolutions were taken

View the transcript

2.3. Comments/Suggestions on Privacy Considerations (issue vc-data-model#1502)

See github issue vc-data-model#1502.

Manu Sporny: these are comments from EFF.
… EFF has reviewed the PR and says it addresses their concerns.
… only other thing is edit from TallTed.

[msporny]

PR #1504 has been merged, closing.