1.What_it_covers #10

Manually merged
fede merged 6 commits from 1.What_it_covers into master 2019-10-24 18:01:18 +00:00
Owner
No description provided.
antilopa was assigned by fede 2019-10-12 17:39:07 +00:00
muppeth was assigned by fede 2019-10-12 17:39:07 +00:00
maryjane was assigned by fede 2019-10-12 17:39:07 +00:00
meaz was assigned by fede 2019-10-12 17:39:07 +00:00
fede self-assigned this 2019-10-12 17:39:07 +00:00
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.
Author
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.
Author
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. :)
Author
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
Author
Owner

I think so too.

I think so too.
muppeth approved these changes 2019-10-16 14:19:26 +00:00
Owner

Ok lets all approve and move on.

Ok lets all approve and move on.
antilopa approved these changes 2019-10-16 14:26:01 +00:00
meaz approved these changes 2019-10-16 20:13:40 +00:00
fede closed this pull request 2019-10-24 18:01:18 +00:00
fede closed this pull request 2019-10-24 18:01:18 +00:00
Sign in to join this conversation.
No reviewers
No Milestone
4 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: Disroot/Disroot-Privacy-Policy#10
No description provided.