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.

Sign up for GitHub

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

Jump to bottom

[Privacy] Clarify that availability callback does not include human readable names #82

Closed
mfoltzgoogle opened this issue May 4, 2017 · 1 comment
Closed

[Privacy] Clarify that availability callback does not include human readable names #82

mfoltzgoogle opened this issue May 4, 2017 · 1 comment
Labels
privacy-tracker Group bringing to attention of Privacy, or tracked by the Privacy Group but not needing response.

Comments

@mfoltzgoogle
Copy link
Contributor

mfoltzgoogle commented May 4, 2017 •
edited

https://lists.w3.org/Archives/Public/public-privacy/2017JanMar/0009.html

  1. Does the RemotePlaybackAvailabilityCallback object include a human-readable name to identify the Callback object? E.g. “kitchen speaker”, “bedroom TV”, “Medical device”? Would this also be exposed outside of the UA? Privacy implications would vary depending on where this human-readable name is disclosed, if any.

It seems clear enough this is not the case, but perhaps we can add a sentence in the Privacy section clarifying this.
@mfoltzgoogle mfoltzgoogle added the privacy-tracker Group bringing to attention of Privacy, or tracked by the Privacy Group but not needing response. label May 4, 2017
@mfoltzgoogle mfoltzgoogle changed the title [Privacy] [Privacy] Clarify that availability callback does not include human readable names May 4, 2017
@mfoltzgoogle mfoltzgoogle mentioned this issue May 9, 2017
Merged
@mfoltzgoogle
Copy link
Contributor Author

Closing as I believe this is addressed by the PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
privacy-tracker Group bringing to attention of Privacy, or tracked by the Privacy Group but not needing response.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@mfoltzgoogle