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.

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

Discovery data sharing and privacy policies #38

Open
oneiros opened this issue Dec 19, 2024 · 1 comment
Open

Discovery data sharing and privacy policies #38

oneiros opened this issue Dec 19, 2024 · 1 comment

Comments

@oneiros
Copy link
Collaborator

oneiros commented Dec 19, 2024

We recognized early on that at least some FASP will need to receive PII from fediverse servers and that this will need to be as transparent as possible. As under GDPR this must become part of the fediverse server's privacy policy, we went so far as to require the specifications to include this information (see https://github.com/mastodon/fediverse_auxiliary_service_provider_specifications/blob/main/general/v0.1/provider_specifications.md#privacy-policy-information).

I fully expected the discovery provider specifications to be the first instance where this would become necessary. But then we decided on a concept that was slightly different from my initial expectation: In our current proposal fediverse servers only share URIs of content/accounts with FASP. FASP then need to fetch the actual content or account information themselves.

I am pretty confident that URIs are not PII. But that means I have absolutely no idea what to put into the specification regarding privacy policies 😦

(See also this discussion: #36 (comment))

Any ideas or help would be really appreciated.

@ThisIsMissEm
Copy link

In this case, whilst the Fediverse server isn't directly sending PII to the FASP, the FASP may be requesting it based on the URIs sent, therefore the FASP would be processing PII. At least, that's my assumption

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants