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.

legal.html 9.2KB

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