The Thorium Authors and the Chromium team are committed to preserving and fostering a diverse, welcoming community. Below is our community code of conduct, which applies to the Thorium repository, the Chromium repository, Alex313031 blog content, and any other Chromium-supported communication group or Thorium discussion board, as well as any private communication initiated in the context of these spaces, including GitHub Issues. This code of conduct must be followed by everyone contributing to or engaging with the Thorium project, regardless of affiliation or position.
Simply put, community discussions should be:
Treat everyone with respect. Build on each other's ideas. Each of us has the right to enjoy our developer experience and participate without fear of harassment, discrimination, or condescension, whether blatant or subtle. Remember that Thorium and Chromium is a geographically distributed team and that you may not be communicating with someone in their primary language. We all get frustrated when working on hard problems, but we cannot allow that frustration to turn into personal attacks.
You are empowered to politely engage when you feel that you or others are disrespected. The person making you feel uncomfortable may not be aware of what they are doing - politely bringing their behavior to their attention is encouraged.
If you are uncomfortable speaking up, or feel that your concerns are not being duly considered, you can email me at Alex313031@gmail.com, or if it is specific to Chromium, at community@chromium.org to request involvement from a community manager. Please note that without a way to contact you, an anonymous report may be difficult to act on. You may also create a throwaway account to report. In cases where a public response is deemed necessary, the identities of victims and reporters will remain confidential unless those individuals instruct us otherwise.
I will always respond in some way, but also keep in mind that while all reports will be taken seriously, I or the Chromium community managers may not act on complaints that we feel are not violations of this code of conduct.
Consequences for failing to comply with this policy may include, at the sole discretion of the a Thorium Maintainer or the Chromium community managers:
Participants warned to stop any harassing behavior are expected to comply immediately; failure to do so will result in an escalation of consequences.
This Code of Conduct is based on the Chromium Code of Conduct > chromium.googlesource.com/chromium/src/+/master/CODE_OF_CONDUCT.md, which is based on the Geek Feminism Code of Conduct > https://geekfeminismdotorg.wordpress.com/about/code-of-conduct/, the Django Code of Conduct > https://www.djangoproject.com/conduct/, and the Geek Feminism Wiki "Effective codes of conduct" guide > https://geekfeminism.fandom.com/wiki/Code_of_conduct_evaluations.
This Code of Conduct is available for reuse under the Creative Commons Zero (CC0) license. https://creativecommons.org/publicdomain/zero/1.0/legalcode
In general I feel that Thorium doesn't need a Privacy Policy, but basically it is similar to the Chromium/Chrome one, except Thorium has additional privacy patches that reduce stuff sent to Google as well as prefetching data sent to sites. I also needed a privacy policy page to use for my Chrome Developer Console to upload my Chromium Extensions, Apps, and Themes, so this is for that too. Outside of things in Chrome's Privacy Policy (sans some things), I don't collect, use, know, or want to know about anything related to you. Privacy is held dear by me, and I pass that on as a token of respect to any user of any software I create. In regard to my Extensions and Apps, the only data sent out is metrics that the Chrome Web Store collects for every Extension/App/Theme. Anyway, you can find the latest Chrome Privacy Policy, as well as archived versions Here.
Addendum: Mercury's privacy policy reflects Mozilla Firefox's Privacy Policy, with the caveat similar to Thorium in that I have added patches to reduce tracking, telemetry, etc.
