Disroot
/
Disroot-Privacy-Policy
8
0
Fork 0
Code Pull Requests Releases Activity

1.What_it_covers #10

Manually merged
fede merged 6 commits from 1.What_it_covers into master 2019-10-24 20:01:18 +02:00
Conversation 12 Commits 6 Files Changed 1 +24 -90
fede commented 2019-10-12 19:39:07 +02:00
Owner
Copy Link
No description provided.
antilopa was assigned by fede 2019-10-12 19:39:07 +02:00
muppeth was assigned by fede 2019-10-12 19:39:07 +02:00
maryjane was assigned by fede 2019-10-12 19:39:07 +02:00
meaz was assigned by fede 2019-10-12 19:39:07 +02:00
fede self-assigned this 2019-10-12 19:39:07 +02:00
muppeth commented 2019-10-13 10:05:20 +02:00
Owner
Copy Link

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.
fede commented 2019-10-13 17:24:03 +02:00
Author
Owner
Copy Link

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.
👍 1
meaz commented 2019-10-14 00:05:01 +02:00
Owner
Copy Link

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.
muppeth commented 2019-10-14 00:09:26 +02:00
Owner
Copy Link

@fede shall we include here the federation explanation?

@fede shall we include here the federation explanation?
meaz commented 2019-10-14 00:15:42 +02:00
Owner
Copy Link

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

It is indeed probably the best place to explain about it.
fede commented 2019-10-14 00:40:51 +02:00
Author
Owner
Copy Link

I think it's the best place too.

I think it's the best place too.
muppeth commented 2019-10-14 17:39:53 +02:00
Owner
Copy Link

@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. :)
fede commented 2019-10-16 00:46:13 +02:00
Author
Owner
Copy Link

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.
muppeth commented 2019-10-16 01:26:57 +02:00
Owner
Copy Link

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).
meaz commented 2019-10-16 05:57:58 +02:00
Owner
Copy Link

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
👍 2
fede commented 2019-10-16 14:48:43 +02:00
Author
Owner
Copy Link

I think so too.

I think so too.
👍 1
muppeth approved these changes 2019-10-16 16:19:26 +02:00
muppeth commented 2019-10-16 16:19:39 +02:00
Owner
Copy Link

Ok lets all approve and move on.

Ok lets all approve and move on.
antilopa approved these changes 2019-10-16 16:26:01 +02:00
meaz approved these changes 2019-10-16 22:13:40 +02:00
fede closed this pull request 2019-10-24 20:01:18 +02:00
fede closed this pull request 2019-10-24 20:01:18 +02:00
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels   
1.2

Document Version

  
FEEDBACK

Comments on the text

  
PRIVACYSTATEMENT

Privacy statement related

  
REVIEW

Needs revision

  
UPDATE

Update

No Label
1.2
FEEDBACK
PRIVACYSTATEMENT
REVIEW
UPDATE
Milestone
Clear milestone
No items
No Milestone
Assignees
Clear assignees
No Assignees
antilopa
muppeth
meaz
fede
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.
Delete Branch "1.What_it_covers"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?