TOC #9

Merged
muppeth merged 2 commits from Points into 1.2 2019-10-11 21:56:46 +00:00
Owner

Decide on points for new version of Privacy Policy

Decide on points for new version of Privacy Policy
Owner

What I like about our current PP, and what people were positively commenting about, is that it is not too 'Lawyered up". The structure is simple, the alguage is simple so I would like to keep it in this casual form and just add what we are missing.

the current TOC is:

  1. What do we do with your data
  2. What we do not do with your data
  3. Access to your information
  4. Your Rights
  5. Per Service additional privacy policies and exceptions
    We could add:
  • What this Privacy policy covers --> the nature of federated services

  • What data do we collect?

  • How do we store your data?

  • Additional Privacy Policies and exceptions per service

  • Changes on this Privacy Policy

What I like about our current PP, and what people were positively commenting about, is that it is not too 'Lawyered up". The structure is simple, the alguage is simple so I would like to keep it in this casual form and just add what we are missing. the current TOC is: 1. What do we do with your data 2. What we do not do with your data 3. Access to your information 4. Your Rights 5. Per Service additional privacy policies and exceptions We could add: - What this Privacy policy covers --> the nature of federated services - What data do we collect? - How do we store your data? - Additional Privacy Policies and exceptions per service - Changes on this Privacy Policy
Owner

Table of Contents

  1. What this Privacy policy covers?
  2. What data do we collect?
  3. How do we store your data?
  4. Additional Privacy Policies and exceptions per service
  5. Your rights (I would include Access to your information here) -> I think it has to be kept.
  6. Changes on this Privacy Policy
# Table of Contents 1. What this Privacy policy covers? 2. What data do we collect? 3. How do we store your data? 4. Additional Privacy Policies and exceptions per service 5. Your rights (I would include Access to your information here) -> I think it has to be kept. 6. Changes on this Privacy Policy
Owner

Where would the points that Muppeth pointed? I'm not sure if it covers everything that the GDPR requires, according to what I shared in the forum.

Where would the points that Muppeth pointed? I'm not sure if it covers everything that the GDPR requires, according to what I shared in the forum.
Owner

Table of Contents

!. What this Privacy policy covers?
2. What data do we collect?
3. What do we do with your data
4. What we do not do with your data (I like this...it could be merged with point 3)
5. How do we store your data?
6. Additional Privacy Policies and exceptions per service
7. Your rights -> Access to your information
8. Changes on this Privacy Policy

## Table of Contents !. What this Privacy policy covers? 2. What data do we collect? 3. What do we do with your data 4. What we do not do with your data (I like this...it could be merged with point 3) 5. How do we store your data? 6. Additional Privacy Policies and exceptions per service 7. Your rights -> Access to your information 8. Changes on this Privacy Policy
Author
Owner

I would change the point 5 to something like

"5. Detailed privacy notice per service"
or
"5. Detailed overview per service provided by Disroot.org"

The current proposed point 5 is still somehow connected to the previous way, which lists only exeptions etc, while we want to change it to give general overview per service. So even if the details are the same (like we dont keep logs for this service) it should be mention for all the ones affected, to avoid confusion where people think we keep logs for everything for 24 hours.

I would change the point 5 to something like "5. Detailed privacy notice per service" or "5. Detailed overview per service provided by Disroot.org" The current proposed point 5 is still somehow connected to the previous way, which lists only exeptions etc, while we want to change it to give general overview per service. So even if the details are the same (like we dont keep logs for this service) it should be mention for all the ones affected, to avoid confusion where people think we keep logs for everything for 24 hours.
Author
Owner

Additionally I think we need to add information about definitions, which should also include federation explanation (brief or link to more detailed one). Not sure if this should be added to !. What this Privacy policy covers? as a sub point of it, or make it into a 'stand alone' point.

Additionally I think we need to add information about definitions, which should also include federation explanation (brief or link to more detailed one). Not sure if this should be added to `!. What this Privacy policy covers?` as a sub point of it, or make it into a 'stand alone' point.
Owner

Table of Contents

!. What this Privacy policy covers?

  • Definitions used on this Privacy Policy
  1. What data do we collect?
  2. What do we do with your data?
    • What we do not do with your data
  3. How do we store your data?
    • Where the data is stored?
  4. Per service detailed privacy notices
  5. Your rights
    • Access to your information
  6. Changes on this Privacy Policy
## Table of Contents !. What this Privacy policy covers? * Definitions used on this Privacy Policy 1. What data do we collect? 2. What do we do with your data?<br> * What we do not do with your data 3. How do we store your data? * Where the data is stored? 4. Per service detailed privacy notices 5. Your rights<br> * Access to your information 6. Changes on this Privacy Policy
Author
Owner

Can we agree to the last proposal?

Can we agree to the last proposal?
Owner

I think we have the base to start, isn't? Since it covers and include all the points we've been talking about and described by the GDPR as the ones that are necessary to be in the PP.

I think we have the base to start, isn't? Since it covers and include all the points we've been talking about and described by the GDPR as the ones that are necessary to be in the PP.
Owner

Looks ok.

Looks ok.
muppeth referenced this issue from a commit 2019-10-11 21:56:46 +00:00
muppeth closed this pull request 2019-10-11 21:56:46 +00:00
Author
Owner

Merged and Ready to work on content \o/

Merged and Ready to work on content \o/
muppeth deleted branch Points 2019-10-11 21:57:16 +00:00
Sign in to join this conversation.
No reviewers
No Milestone
No Assignees
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#9
No description provided.