Community Privacy Policy

downey · June 9, 2016, 4:15pm

We now have a first draft of a privacy policy in the “governance” repo on GitHub:

LibreHealthIO/community-governance/blob/master/PRIVACY-POLICY.md

# LibreHealth Privacy Policy

LibreHealth is a free & open source project organized by a worldwide group of volunteers. Our challenges and goals are large. For that reason, we have a very permissive (non) privacy policy that mirrors our public mission.

Please assume that everything you contribute intentionally to LibreHealth is public. This includes messages on public forums, wikis, online discussions of all sorts, and software or documentation that you post to our websites.

Because we value mutual personal respect, disclosure of interests, and openness of expression, even your LibreHealth community profile is public information. There will be cases where you are invited to share private information for various purposes, and denote that information as such. In those cases, we commit to only disclosing that information without your permission upon receipt of valid legal orders, and whenever possible, following notice from LibreHealth to you.

Although what you disclose here is public, we are all limited by copyright and patent law in how we may use your contributions. Therefore, LibreHealth only accepts voluntary contributions of software and documentation that are expressly licensed to LibreHealth under an approved open source license. Refer to the LibreHealth Contribution Policy for additional details.

LibreHealth welcomes your questions or comments regarding this Privacy Policy. Send them to community@librehealth.io.

## Acknowledgements

*This work, "LibreHealth Privacy Policy", is a derivative of "OpenMRS Privacy Policy" by OpenMRS Inc., used under the Creative Commons 4.0 International Attribution License (CC BY 4.0). "LibreHealth Privacy Policy" is licensed under the Creative Commons 4.0 International Attribution License (CC BY 4.0) by Humanitech Inc.*

Your feedback, concerns, and comments, are welcome – either via pull request on GitHub (preferred) or by commenting here in this topic, or both!