OurHike/site/Privacy/index.html at main · ghzhost/OurHike · GitHub

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
<!doctype html>
<html lang="en">
  <head>
    <meta charset="UTF-8" />
    <meta name="viewport" content="width=device-width, initial-scale=1.0" />
    <title>Privacy Policy — OurHike</title>
    <meta
      name="description"
      content="What OurHike collects, why, and how to ask about or delete your data."
    />
    <meta name="theme-color" content="#122016" />
    <link rel="icon" type="image/svg+xml" href="../favicon.svg" />

    <style>
      /* Same tokens as the landing page (site/index.html), so this reads as
         the same product rather than a bolted-on legal page. */
      :root {
        --pine-900: #122016;
        --forest-600: #355c3a;
        --forest-500: #47784b;
        --moss-300: #96b98c;
        --sage-200: #c7dabd;
        --stone-900: #2b2620;
        --stone-700: #5a5346;
        --stone-500: #8a8271;
        --stone-150: #e4ddca;
        --paper-100: #f7f3e9;
        --paper-0: #fffdf7;

        --bg: var(--paper-100);
        --surface: var(--paper-0);
        --fg-1: var(--stone-900);
        --fg-2: var(--stone-700);
        --fg-3: var(--stone-500);
        --border: var(--stone-150);
        --accent: var(--forest-600);
        --accent-fg: var(--paper-0);
        --radius: 14px;
      }

      @media (prefers-color-scheme: dark) {
        :root {
          --bg: #14130e;
          --surface: #1e1d16;
          --fg-1: #ece7d8;
          --fg-2: #b9b3a1;
          --fg-3: #8e8878;
          --border: #37342a;
          --accent: var(--moss-300);
          --accent-fg: var(--pine-900);
        }
      }

      *,
      *::before,
      *::after {
        box-sizing: border-box;
      }

      body {
        margin: 0;
        background: var(--bg);
        color: var(--fg-1);
        font-family:
          ui-sans-serif,
          system-ui,
          -apple-system,
          "Segoe UI",
          Roboto,
          Helvetica,
          Arial,
          sans-serif;
        font-size: 1.0625rem;
        line-height: 1.65;
        -webkit-font-smoothing: antialiased;
      }

      .wrap {
        width: 100%;
        max-width: 42rem;
        margin-inline: auto;
        padding-inline: 1.25rem;
      }

      header.top {
        background: var(--pine-900);
        color: var(--paper-0);
        padding-block: 1.5rem;
      }

      .lockup {
        display: flex;
        align-items: center;
        gap: 0.65rem;
        text-decoration: none;
        color: inherit;
        font-weight: 800;
        letter-spacing: -0.02em;
        font-size: 1.15rem;
      }

      .lockup__mark {
        border-radius: 9px;
        flex-shrink: 0;
        box-shadow: 0 4px 16px rgb(0 0 0 / 0.35);
      }

      main {
        padding-block: 2.5rem 4rem;
      }

      h1 {
        font-size: clamp(1.9rem, 6vw, 2.4rem);
        letter-spacing: -0.02em;
        line-height: 1.1;
        margin: 0 0 0.5rem;
      }

      .updated {
        color: var(--fg-3);
        font-size: 0.92rem;
        margin: 0 0 2rem;
      }

      .lede {
        font-size: 1.1rem;
        color: var(--fg-2);
      }

      h2 {
        font-size: 1.3rem;
        letter-spacing: -0.01em;
        margin: 2.25rem 0 0.75rem;
        display: flex;
        align-items: center;
        gap: 0.6rem;
      }

      h2::before {
        content: "";
        width: 9px;
        height: 22px;
        border-radius: 4px;
        background: var(--accent);
        flex-shrink: 0;
      }

      h3 {
        font-size: 1.02rem;
        margin: 1.4rem 0 0.5rem;
      }

      p,
      li {
        text-wrap: pretty;
      }

      ul {
        padding-left: 1.3rem;
        margin: 0.75rem 0;
      }

      li {
        margin: 0.4rem 0;
      }

      a {
        color: var(--accent);
        text-underline-offset: 2px;
      }

      .card {
        background: var(--surface);
        border: 1px solid var(--border);
        border-radius: var(--radius);
        padding: 1.25rem 1.5rem;
        margin: 1.5rem 0;
      }

      .note {
        border-radius: 0 10px 10px 0;
        padding: 0.9rem 1.1rem;
        margin: 1.25rem 0;
        font-size: 0.97rem;
        background: color-mix(in srgb, var(--accent) 12%, transparent);
        border-left: 4px solid var(--accent);
      }

      footer {
        border-top: 1px solid var(--border);
        margin-top: 2rem;
        padding-block: 1.75rem 3rem;
        color: var(--fg-3);
        font-size: 0.9rem;
      }
    </style>
  </head>

  <body>
    <header class="top">
      <div class="wrap">
        <a class="lockup" href="../">
          <svg
            class="lockup__mark"
            width="30"
            height="30"
            viewBox="0 0 96 96"
            role="img"
            aria-label="OurHike"
          >
            <defs>
              <linearGradient id="mark-split" x1="0" y1="0" x2="1" y2="1">
                <stop offset="50%" stop-color="#355c3a" />
                <stop offset="50%" stop-color="#5a5346" />
              </linearGradient>
              <clipPath id="mark-round">
                <rect width="96" height="96" rx="20" />
              </clipPath>
            </defs>
            <g clip-path="url(#mark-round)">
              <rect width="96" height="96" fill="url(#mark-split)" />
              <rect x="41" y="16" width="20" height="76" rx="10" fill="#fff" />
            </g>
          </svg>
          OurHike
        </a>
      </div>
    </header>

    <main class="wrap">
      <h1>Privacy Policy</h1>
      <p class="updated">Last updated August 13, 2026</p>

      <p class="lede">
        OurHike is a small, volunteer-built offline map for the Appalachian
        Trail, currently in public beta. This page explains what
        information we collect, why, and what you can do about it — in
        plain language, not legalese. If something here is unclear,
        <a href="https://github.com/OurHike/OurHike/issues"
          >open an issue</a
        >
        and ask.
      </p>

      <div class="note">
        You can use the core map — the trail, water, shelters, and
        campsites, even offline — without creating an account or handing
        over any personal information at all.
      </div>

      <h2>Information we collect</h2>

      <h3>Account information</h3>
      <p>
        Creating an account is only needed to submit a trail report or
        contribute in other ways — not to use the map. If you sign in, we
        (through our authentication provider, Supabase) collect:
      </p>
      <ul>
        <li>
          Your <strong>email address</strong>, whether you sign in with a
          magic link, a password, or a Google account you already have.
        </li>
        <li>
          If you sign in with Google, the basic profile information Google
          shares to verify your identity (your email address, typically
          nothing beyond that).
        </li>
        <li>
          If you set a password, it's stored and hashed by Supabase — we
          never see or store it ourselves.
        </li>
        <li>
          A <strong>trail name</strong> you choose yourself, and the kind
          of hiker you say you are (thru, section, day, or maintainer).
          Your trail name — not your real name or email — is what other
          hikers see if you post a report.
        </li>
      </ul>

      <h3>Location</h3>
      <p>
        OurHike can use your device's GPS to show your position on the
        map. That location is used on your device only and is not sent
        anywhere unless you choose to attach it to a report you submit —
        for example, to mark exactly where a blowdown or a water source
        is.
      </p>
      <p>
        That includes the off-trail alert. If you turn it on, OurHike
        watches your position continuously to notice when you may have
        left the trail — and it does that entirely on your phone. Your
        track is not uploaded, not stored on our side, and not used for
        anything else.
      </p>

      <h3>Notifications</h3>
      <p>
        <strong>OurHike sends exactly one kind of notification: the
        off-trail alert.</strong> Nothing else — no news, no reminders,
        no marketing, no "come back and use the app". That is a rule in
        the code rather than a promise here: there is a single function
        allowed to send a notification, and an automated check reads the
        whole codebase and fails the build if anything else tries to.
      </p>

      <h3>Reports you submit</h3>
      <p>
        If you report a trail condition (a blowdown, flooding, a shelter
        needing repair, and so on), we collect what you put in it: the
        category, any note you write, the location if you include one,
        and the time you wrote it. A report may in the future let you
        attach a photo, in which case that photo is collected too.
      </p>
      <p>
        Reports about other people ("bad hikers") are handled more
        carefully than trail-condition reports: they go only to safety
        moderators, never shown publicly.
      </p>

      <h3>Information kept only on your device</h3>
      <p>
        The downloaded map data, your app preferences, and any report
        you've written but haven't yet been able to send (there's often no
        signal on the trail) are stored locally on your phone using your
        browser's on-device storage. We don't have access to this until a
        report is actually sent.
      </p>

      <h3>Standard technical information</h3>
      <p>
        Like almost any website, the infrastructure that serves OurHike
        (GitHub Pages, Cloudflare, and similar) may log ordinary technical
        details — such as IP address and browser type — as part of normal
        operation. We don't collect this ourselves or use it to identify
        you.
      </p>

      <h3>Usage analytics</h3>
      <p>
        We don't currently run any analytics or event-tracking tool in the
        app. We're likely to add some limited, aggregated analytics in the
        future — for example, which screens or features get used — to
        help us understand what's working and prioritize what to build
        next. If we do, we'll aim to keep it as non-identifying as we
        reasonably can, and we'll update this page when it happens rather
        than after the fact.
      </p>

      <h2>How we use this information</h2>
      <ul>
        <li>To run the app: show your position, sync your account, and let you submit and track reports.</li>
        <li>To keep the trail community trustworthy: moderators use report details to verify conditions and act on safety concerns.</li>
        <li>To improve OurHike: understanding what's used and what isn't, in aggregate.</li>
      </ul>
      <p>
        We do not sell your personal information, and we don't run
        advertising in the app.
      </p>

      <h2>Who we share it with</h2>
      <ul>
        <li>
          <strong>Supabase</strong>, our authentication provider — handles
          sign-in and stores your account credentials on our behalf.
        </li>
        <li>
          <strong>Trail clubs and maintainers</strong> may see reports
          relevant to the sections they maintain, and public reports are
          visible (by trail name, not real name or email) to anyone using
          the app.
        </li>
        <li>
          We may disclose information if required to by law, or to
          protect the safety of someone on the trail.
        </li>
      </ul>
      <p>
        <strong>Map tiles come from three places, and asking for a tile
        says roughly where you are looking.</strong> The trail data and
        the downloadable offline maps come from our own storage at
        Cloudflare. The default background map comes from
        <a href="https://openfreemap.org/">OpenFreeMap</a>
        (<code>tiles.openfreemap.org</code>), and the hillshading and
        contours from
        <a href="https://registry.opendata.aws/terrain-tiles/"
          >AWS Terrain Tiles</a
        >
        (<code>s3.amazonaws.com</code>). None of those requests carries
        your account, your trail name
        or anything else that identifies you — but the servers involved
        do see which part of the map was fetched, in the ordinary way any
        website sees which page you asked for.
      </p>
      <p>
        If you would rather not fetch tiles at all while you walk,
        downloading the map for offline use is the answer: once it is on
        your phone, the map draws from your own device and asks nobody
        anything.
      </p>

      <h2>Your choices</h2>
      <ul>
        <li>Browse the map, water, shelters, and closures with no account at all.</li>
        <li>
          Ask us to see, correct, or delete the account information we
          hold by
          <a
            href="https://github.com/OurHike/OurHike/issues"
            >opening an issue</a
          >
          — no need to put personal details in the issue itself, just ask
          and we'll follow up.
        </li>
        <li>Clear locally stored map data and preferences any time from your device or browser settings.</li>
      </ul>

      <h2>Children's privacy</h2>
      <p>
        OurHike isn't directed at children, and we don't knowingly collect
        information from anyone under 13.
      </p>

      <h2>Security</h2>
      <p>
        We take reasonable steps to protect the information we hold, but
        no method of storage or transmission is completely secure, and we
        can't guarantee absolute security.
      </p>

      <h2>Changes to this policy</h2>
      <p>
        We may update this policy as the app changes. We'll update the
        date at the top when we do, and for meaningful changes we'll try
        to call it out on the app's
        <a href="https://github.com/OurHike/OurHike"
          >GitHub page</a
        >.
      </p>

      <h2>Contact</h2>
      <p>
        Questions about this policy or your data:
        <a href="https://github.com/OurHike/OurHike/issues"
          >open an issue on GitHub</a
        >.
      </p>

      <footer>
        <p>
          <a href="../">Back to OurHike</a>
        </p>
      </footer>
    </main>
  </body>
</html>