Revised privacy language #474
Conversation
It came to our attention while discussing #399 that the privacy language we have on 18f.gsa.gov is inaccurate and not in keeping with terms we are using on other 18F projects. This commit integrates more accurate terms.
|
👍 to this, thanks |
|
|
|
For the (public) record, this was a mistake on my part when reviewing copy. In the context of "sharing data with third parties" the statement was accurate. It's in the context of under the law sharing data with other teams within government it was inaccurate. |
|
And to disambiguate - I think what you mean, @NoahKunin, is how the statement works in relation to the name and email address we ask people to put into the newsletter signup form. We share it with other GSA teams, but not with third parties. (Though if we switch from HYDRA to e.g. Mailchimp, that would change.) I originally brought this statement up in #399 in the context that it was the only language relating to privacy on our whole website. So if it were interpreted as a statement of how we handle all of our visitors' information (including their user agent, request metadata, etc.), it wouldn't be accurate, since Google and Amazon both see that information. So I'm a 👍 for merging this, for sure, but it doesn't address the full scope of how our website handles visitor information. |
|
@konklone Correct, this is a technical hotfix while we tracker the larger issue. |
It came to our attention while discussing #399 that the privacy language we have on 18f.gsa.gov is inaccurate and not in keeping with terms we are using on other 18F projects. This commit integrates more accurate terms suggested by @polastre.