Let's Encrypt v2 (ACME draft 11) client for your browser. Companion to greenlock.js https://greenlock.domains
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

316 lines
10 KiB

  1. <!DOCTYPE html>
  2. <html>
  3. <head>
  4. <title>Root Legal</title>
  5. </head>
  6. <body>
  7. <h1>Greetings!</h1>
  8. <p>
  9. I, AJ ONeal, am not a big fan of legalize, but I am a fan of communicating
  10. clearly. I hope that this accomplish both defining some legal boundaries
  11. as well as communicating in a friendly and clear way, at least to the
  12. degree that suits our needs for the current stage of our products and
  13. services.
  14. </p>
  15. <p>
  16. This is important because it is our intent to create sustainable open
  17. source projects, which means that we do want to create brand value, grow
  18. community, and, eventually, be able to work full time on creating more
  19. great software and services.
  20. </p>
  21. <p>
  22. If you'd like to contact me, especially if you feel that I (or we) have
  23. made a mistake in how we operate, please do so:
  24. </p>
  25. <ul>
  26. <li><a href="mailto:coolaj86@gmail.com">coolaj86@gmail.com</a></li>
  27. <li><a href="tel:+13852360466">+1 (385) 236-0466</a></li>
  28. <li><a href="http://coolaj86.com">https://coolaj86.com</a></li>
  29. </ul>
  30. <h1>Contents</h1>
  31. <p>Here's what I've worked through so far:</p>
  32. <ul>
  33. <li><a href="#greenlock">Greelock Domains</a></li>
  34. <li><a href="#licensing">Licensing</a></li>
  35. <li><a href="#terms">Terms of Service</a></li>
  36. <li><a href="#trademark">Trademark</a></li>
  37. <li><a href="#privacy">Privacy</a></li>
  38. </ul>
  39. <h1 id="greenlock">Greenlock Domains&trade;</h1>
  40. <p>
  41. Greenlock Domains is a service provided by
  42. <em
  43. ><a href="https://coolaj86.com">AJ</a>, Brian,
  44. <a href="https://jshaver.net">John</a>, &amp; Josh</em
  45. >
  46. (collectively <a href="https://therootcompany.com">Root</a>) for automated
  47. TLS, SSL, and HTTPS.
  48. </p>
  49. <ul>
  50. <li>
  51. <a href="https://greenlock.domains" target="_blank">
  52. https://greenlock.domains</a
  53. >
  54. </li>
  55. <li>
  56. <a
  57. href="https://git.coolaj86.com/coolaj86/greenlock-express.js"
  58. target="_blank"
  59. >
  60. https://git.coolaj86.com/coolaj86/greenlock-express.js</a
  61. >
  62. </li>
  63. <li>
  64. <a
  65. href="https://git.coolaj86.com/coolaj86/greenlock.js"
  66. target="_blank"
  67. >
  68. https://git.coolaj86.com/coolaj86/greenlock.js</a
  69. >
  70. </li>
  71. <li>
  72. <a
  73. href="https://git.coolaj86.com/coolaj86/greenlock.html"
  74. target="_blank"
  75. >
  76. https://git.coolaj86.com/coolaj86/greenlock.html</a
  77. >
  78. </li>
  79. </ul>
  80. <p>
  81. Greenlock Domains is an important product / service combo to us because
  82. it's a huge milestone on the path to a more decentralized web. We believe
  83. in
  84. <em>ownership</em> and <em>control</em> and we're building a
  85. <a href="https://therootcompany.com">Home Server</a> because we envision a
  86. world in which everyone is empowered to make the choice of whether to rent
  87. or own their stuff.
  88. </p>
  89. <p>
  90. If we don't do this, well, with the way the cloud is headed, renting may
  91. be the only option in the future.
  92. </p>
  93. <p>We need <em>Root</em> because we want ownership.</p>
  94. <p>
  95. If at any time you feel that any of our messaging or practices are in
  96. conflict with our mission or these values, please let us know.
  97. </p>
  98. <h1 id="licensing">Licensing</h1>
  99. <p>
  100. Each of our products comes with its own LICENSE file and the license(s)
  101. may alse be in some sort of manifest file (such as package.json).
  102. </p>
  103. <p>
  104. We typically use the MIT and Apache-2.0 licenses for libraries that we
  105. actively want others to copy, modify, use and redistribute.
  106. </p>
  107. <p>
  108. We typically use ISC and MPL-2.0 with products for which we're a little
  109. more concerned about branding or about which we have particularly strong
  110. opinions.
  111. </p>
  112. <p>
  113. Although we do keep some of our software proprietary and we do use
  114. trademarks, because we believe in empowerment and choice we do our best to
  115. provide usable self-service forms of our products and services for
  116. personal use.
  117. </p>
  118. <p>
  119. If at any time you feel that our Licensing is in conflict with our mission
  120. or values, please let us know.
  121. </p>
  122. <h1 id="terms">Terms of Service</h1>
  123. <p>
  124. We want to make the world a better place. Everyone has a different
  125. definition of what "a better place" means, so the purpose of our terms is
  126. to rule out some things that we think makes the world (and particularly
  127. our world) a worse place:
  128. </p>
  129. <p>
  130. You agree that you will use the Greenlock&trade; service, code, libraries,
  131. documentation, etc (provided by <a href="#greenlock">us</a>) primarily for
  132. securing network connections for yourself, your customers, on your and
  133. your customer's devices on internets, intranets, and... other nets.
  134. </p>
  135. <p>
  136. You agree that you will take reasonable measures to keep up-to-date with
  137. security releases.
  138. </p>
  139. <p>
  140. You agree to not use our products or services in a way that would cause
  141. unusual or undue burden on our servers or services, our partners servers
  142. or services, or our customers servers or services, or in a way that harms
  143. or misrepresents the reputation or brand value (including causing brand
  144. confusion) of the aforementioned parties (or really anybody).
  145. </p>
  146. <p>
  147. This is not to say that you can't publicly have a negative opinion, but
  148. don't bite the hand that feeds and don't be vicious or misrepresentative.
  149. </p>
  150. <p>
  151. If you have a use case that may be in violation of these terms
  152. (particularly the part about undue burden), but you feel contributes to
  153. making the world a better place, we're here to help (assuming it also
  154. aligns with our values). Although it may not be appropriate to use our
  155. services, but perhaps we can help you with a solution based on our
  156. no-cost, low-cost or open source products.
  157. </p>
  158. <p>
  159. If at any time you feel that our Terms of Service are in conflict with our
  160. mission or values, please let us know.
  161. </p>
  162. <h1 id="trademark">Trademark</h1>
  163. <p>
  164. "Greenlock" and the "green G lock" mark are Trademarks of
  165. <a href="https://coolaj86.com" target="_blank">AJ ONeal</a>.
  166. </p>
  167. <p>
  168. We'll be coming out with a brand guide as to how you should use the marks.
  169. In the meantime: don't change the proportions, colors (excepting the case
  170. of greyscale and black and white).
  171. </p>
  172. <p>
  173. It is appropriate to use the trademark in a way that promotes the brand
  174. with proper attribution, linking to the official project repositories,
  175. etc.
  176. </p>
  177. <p>
  178. It is appropriate use the name greenlock in a plugin for Greenlock&trade;,
  179. as long as it is clear that it is a community contribution.
  180. </p>
  181. <p>
  182. If you create a "hard" fork of our code or any products or services, you
  183. should give your fork its own name, and not use ours. That sound, we
  184. gladly welcome your suggestiosn and pull requests.
  185. </p>
  186. <p>
  187. If you mirror our code you should make it clear that it is a mirror and
  188. link to the official repository. in association with usand the disclose
  189. that you use Greenlock
  190. </p>
  191. <p>
  192. If at any time you feel that our Trademark policies are in conflict with
  193. our values, please let us know.
  194. </p>
  195. <h1 id="privacy">Privacy Policy</h1>
  196. <p>What we collect and (more importantly) <em>Why</em>:</p>
  197. <p><strong>Name</strong>:</p>
  198. <p>
  199. In the cases that we collect your name, it's because we want to know how
  200. to address you. All four of us want to be personable if and when we reach
  201. out.
  202. </p>
  203. <p><strong>Email</strong>:</p>
  204. <p>
  205. There are three main purposes for which we may use your email address:
  206. </p>
  207. <p>
  208. 1. A one-time outreach to ask if you were able to do what you intended to
  209. do. We want to make a great product. Although open source projects
  210. traditionally have a <em>reactive</em> approach to communication (i.e. you
  211. file a bug and wait for a response), we believe that creating sustainable
  212. open source requires a <em>proactive</em> approach.
  213. </p>
  214. <p>
  215. 2. Security and legal notifications. It's important that we have a way to
  216. contact you if we've made a mistake or discover a mistake that needs to be
  217. addressed. This may include vulnerabilities as well as mandatory upgrades
  218. (such as when a significant change to the Let's Encrypt API is made).
  219. Making sure that our products work and are secure aligns with our values
  220. and contributes to our brand identity.
  221. </p>
  222. <p>
  223. 3. Opt-in updates. Many of you want to know when we have significant
  224. feature updates or when we have something that we believe is really
  225. valuable to share. We've created an opt-in avenue for that. And you can
  226. always opt-out as well.
  227. </p>
  228. <p><strong>Telemetry</strong>:</p>
  229. <p>
  230. We believe that the current open source model needs improvement - it often
  231. relies heavily on large centralized platforms which aggregate a lot of
  232. user information for the platform without appropriately targeting the
  233. relationship between authors and users of projcts (i.e. npm, github, etc).
  234. We believe that making open source sustainable means a greater focus on
  235. empowering authors and users. We've learned from other projects (Caddy,
  236. Heroku, and others) which use telemetry as part of a proactive approach to
  237. open source and we believe that it can be a great avenue for us to be
  238. proactive as well.
  239. </p>
  240. <p>
  241. We may use telemetry about operating system, browser, node version, code
  242. version, and other system-level information to better understand how we
  243. can serve our users (you) and proactively solve problems that we might not
  244. otherwise hear about. For example, if we see many page visits in a certain
  245. browser (or installs with a new version of node), but few successful
  246. registrations, we know that something is wrong.
  247. </p>
  248. <p><strong>Other</strong>:</p>
  249. <p>
  250. We also use Google Analytics on our web sites for basic functionality.
  251. Other than that, nothing else comes to mind right now. As we consider what
  252. we will do in the future, it will be measured against our mission and
  253. values. We never want to come across as spammy or forceful. We want to do
  254. things that help us build our brand, acknowledge our customers; things
  255. that are proactive, and that promote sustainable source.
  256. </p>
  257. <p>
  258. If at any time you feel that our Privacy policy is in conflict with our
  259. mission or values, please let us know.
  260. </p>
  261. <br />
  262. <br />
  263. <p>Copyright 2018 AJ ONeal</p>
  264. </body>
  265. </html>