1.What_it_covers #10

Manually merged
fede merged 6 commits from 1.What_it_covers into master 2 years ago
fede commented 2 years ago
Owner
There is no content yet.
antilopa was assigned by fede 2 years ago
muppeth was assigned by fede 2 years ago
maryjane was assigned by fede 2 years ago
meaz was assigned by fede 2 years ago
fede self-assigned this 2 years ago
Owner

We still need Definitions used on this Privacy Policy, as well as a bit about Legal basis, responsible parties and i guess we can then move details of data protection office into there too.

We still need Definitions used on this Privacy Policy, as well as a bit about Legal basis, responsible parties and i guess we can then move details of data protection office into there too.
Poster
Owner

As I mentioned in the description, the GDPR definition of data is tremendously broad. The list of types of personal data that could lead to the identification of a natural person in the digital context further include email addresses, cookies, IP addresses and, overall, lots of online identifiers. It has to be adjusted to the context of Disroot.

As I mentioned in the description, the GDPR definition of data is tremendously broad. The list of types of personal data that could lead to the identification of a natural person in the digital context further include email addresses, cookies, IP addresses and, overall, lots of online identifiers. It has to be adjusted to the context of Disroot.
Owner

I like what you did Fede. I think it is pretty complete now.

I like what you did Fede. I think it is pretty complete now.
Owner

@fede shall we include here the federation explanation?

@fede shall we include here the federation explanation?
Owner

It is indeed probably the best place to explain about it.

It is indeed probably the best place to explain about it.
Poster
Owner

I think it's the best place too.

I think it's the best place too.
Owner

@fede can you add it then? I think we would be sort of ready with this one. :)

@fede can you add it then? I think we would be sort of ready with this one. :)
Poster
Owner

If the text is ok, we can move forward. I couldn't find a way to make it shorter.

If the text is ok, we can move forward. I couldn't find a way to make it shorter.
Owner

I think the text about federation should be more explanatory. Maybe something like this, though perhaps this fits more in Access to your information. So unless we add better explanation there, we should provide a bit more then suggested in the pull request:


Federated services: Services that operates on the basis of so-called Federation Protocols which enables users signed up at different services providers to interact with each other. Examples of these services are Nextcloud, Email, Hubzilla and XMPP.Because of the nature of the protocols (ability to send each other messages, likes, share files, chat) some of the data is naturally shared or transmited to other entities (eg. sending email to different provider). We cannot take responsiblity for privacy practices of others, however, sharing data with other service provider is the user's choice, and depending on service, user can decide with whom and what to share (eg. user can choose not to send the email to different provider).

I think the text about federation should be more explanatory. Maybe something like this, though perhaps this fits more in Access to your information. So unless we add better explanation there, we should provide a bit more then suggested in the pull request: --- **Federated services**: Services that operates on the basis of so-called **Federation Protocols** which enables users signed up at different services providers to interact with each other. Examples of these services are **Nextcloud**, **Email**, **Hubzilla** and **XMPP**.Because of the nature of the protocols (ability to send each other messages, likes, share files, chat) some of the data is naturally shared or transmited to other entities (eg. sending email to different provider). We cannot take responsiblity for privacy practices of others, however, sharing data with other service provider is the user's choice, and depending on service, user can decide with whom and what to share (eg. user can choose not to send the email to different provider).
Owner

I would keep what @fede wrote as it is a simple definition, like other definitions, and would add the rest of what @muppeth wrote in Access to your information

I would keep what @fede wrote as it is a simple definition, like other definitions, and would add the rest of what @muppeth wrote in Access to your information
Poster
Owner

I think so too.

I think so too.
muppeth approved these changes 2 years ago
Owner

Ok lets all approve and move on.

Ok lets all approve and move on.
antilopa approved these changes 2 years ago
meaz approved these changes 2 years ago
fede closed this pull request 2 years ago
fede closed this pull request 2 years ago
The pull request has been manually merged as 9e734db177.
Sign in to join this conversation.
No reviewers
No Milestone
4 Participants
Notifications
Due Date

No due date set.

Dependencies

This pull request currently doesn't have any dependencies.

Loading…
There is no content yet.