Documentation for Privacy, TOS, FAQ

[QuincyLarson]

We will use existing freeCodeCamp privacy and terms of service documents. We do want to make it so people can make their account private and delete their account. We should preferably handle these through the existing freecodecamp.org/settings page.

[chrismgonzalez]

I was just about to ask if we want to use FCCs terms on this. Looks like that’s been answered. Will add them this weekend.

[chrismgonzalez]

The FCC privacy policy is quite long. I will need to trim it down to reflect the goals of Chapter. I will definitely need some input to determine what to keep and what to drop.

[ceciliaconsta3]

Do we need to take into account CCPA updates?

[QuincyLarson]

@chrismgonzalez Our privacy policy was hand-written by a lawyer-developer who is well versed in modern web apps. We could trim it down but we should be careful about it. I recommend instead just updating the specifics slightly. Very few people read the privacy policy, but the ones who do appreciate it being comprehensive.

[allella]

Regarding privacy settings, we've touched on what privacy settings to offer for MVP.

Quincy suggested the need for at least a user-level privacy setting.

Perhaps we start out with allowing a user to be globally shown as "Private Member" or "Private Guest" to the public. However, I'd think the organizer and admin would be able to see at least the person's name and email address.

Who can see what, even when you're marked as private needs to be addressed and made pretty clear in the UI, privacy policy, and privacy-related FAQ.

[chrismgonzalez]

Got it. Good to know.