Browse Source

add privacy policy

master
AJ ONeal 9 months ago
parent
commit
a4c2da82c5
4 changed files with 211 additions and 9 deletions
  1. 7
    3
      app/index.html
  2. 6
    4
      index.html
  3. 197
    2
      legal.html
  4. 1
    0
      legal/index.html

+ 7
- 3
app/index.html View File

@@ -331,13 +331,16 @@
331 331
           <button type="submit">Start Over</button>
332 332
           -->
333 333
         </form>
334
+      </div>
334 335
 
335 336
           <br>
336
-          <br>
337
-          <br>
338 337
           <div><small>
339 338
           <h3></h3>
340
-          <a href="https://git.coolaj86.com/coolaj86/greenlock.html">View Source</a> (git)
339
+          <div>
340
+              <a href="https://git.coolaj86.com/coolaj86/greenlock.html" target="_blank">View Source</a> (git)
341
+              | <a href="https://greenlock.domains/legal/#terms" target="_blank">Terms of Service</a>
342
+              | <a href="https://greenlock.domains/legal/#privacy" target="_blank">Privacy Policy</a>
343
+          </div>
341 344
           <!-- or
342 345
           <pre><code>git clone https://git.coolaj86.com/coolaj86/greenlock.html.git</code></pre>
343 346
           Or view the live site code (same as live-site branch):
@@ -345,6 +348,7 @@
345 348
           -->
346 349
           </small></div>
347 350
 
351
+
348 352
         <script src="./js/bacme.js"></script>
349 353
         <script src="./js/app.js"></script>
350 354
 

+ 6
- 4
index.html View File

@@ -55,7 +55,7 @@
55 55
           </div>
56 56
           <button type="submit">Go</button>
57 57
           <div class="domain-subtext">Domain, subdomain, or wildcard domain</div>
58
-          
58
+
59 59
           <div class="acme-advanced-fields">
60 60
             <label><input name="acme-api-type" type="radio" value="v02" checked required>
61 61
               Production
@@ -64,15 +64,17 @@
64 64
               Testing</label>
65 65
             <input id="js-acme-api-url" type="url" placeholder="ACME directory url">
66 66
             <div>
67
-              <a href="https://git.coolaj86.com/coolaj86/greenlock.html">View Source</a> (git)
67
+              <a href="https://git.coolaj86.com/coolaj86/greenlock.html" target="_blank">View Source</a> (git)
68
+              | <a href="https://greenlock.domains/legal/#terms" target="_blank">Terms of Service</a>
69
+              | <a href="https://greenlock.domains/legal/#privacy" target="_blank">Privacy Policy</a>
68 70
             </div>
69 71
           </div>
70 72
         </form>
71 73
       </div>
72 74
       <div class="column-row">
73 75
         <div class="why-you-need">
74
-          <h2>Why you need SSL certificates</h2>
75
-          If your website doesn't have the green lock from an SSL Certificate, Google Chrome will soon label your website as not secure.
76
+          <h2>Why you need HTTPS</h2>
77
+          SSL Certificates are required for secure login, accepting payments, and for browsers like Google Chrome to stop showing security warnings to your users.
76 78
         </div>
77 79
       </div>
78 80
       <!-- or

+ 197
- 2
legal.html View File

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

+ 1
- 0
legal/index.html View File

@@ -0,0 +1 @@
1
+../legal.html

Loading…
Cancel
Save