privacy

Privacy policy

Effective September 22, 2026 · Version 0 · Applies to highmileage.xyz and the High Mileage ticketing & waiver app

This is what we collect, why we collect it, where it goes, and what you can do about it. It is written in plain English because you are supposed to be able to read it. The short version: we collect what it takes to run a run, we keep signed waivers because they are legal records, and we never sell your details to anyone.

1. Who we are

High Mileage is a run club in Los Angeles, California. The company behind it is Curative Company Inc., doing business as High Mileage and as ORUZU. When this policy says “we,” “us,” or “High Mileage,” it means Curative Company Inc. We hold the data described here and we are responsible for it.

High Mileage runs are co-produced by ORUZU and Weerd. Weerd is a separate partner. It does not receive the list, the waiver records, or the ticket records.

Questions, requests, and complaints all go to one place: hi@highmileage.xyz.

2. What this policy covers

highmileage.xyz — the website, including “the list” sign-up form.
The ticketing & waiver app at highmileage-app.vercel.app (moving to tickets.highmileage.xyz) — the waiver, your pass, and the check-in tools our staff use at the door.
Emails and texts we send you.

It does not cover other companies’ services we link to or hand you off to: Partiful (RSVPs for some runs), Shopify’s checkout pages (ticket purchases), and Instagram. Each of those has its own privacy policy, and what you give them is governed by it.

3. What we collect, and why

We collect only what running the event requires. Nothing is collected “just in case.” Here it is, surface by surface.

3.1 The list (highmileage.xyz)

When you join the list we store:

Your email address (required — it is what the list is).
Your mobile number, only if you tick the box asking for texts. The phone field does not appear until you do.
The exact wording of the consent you agreed to, and its version. We keep the words, not just a checkbox, so the record is readable years later.
The page you signed up from, your browser’s user-agent string, the date and time, and a salted hash of your IP address. We do not store the IP address itself. The hash is evidence that a sign-up came from somewhere, which is all a consent record needs.

Why: to email you when runs are announced, and — if you asked for it and texting has been switched on — to text you meet points and start times. Email and text consent are separate. Ticking the text box is optional and is never a condition of anything.

If you tick the text box before texting has been switched on, we keep the number with your sign-up but we do not text it. We will not start texting you unless there is a consent on record. See the SMS terms.

3.2 Buying a ticket

Tickets are sold through Shopify. Shopify runs the checkout and takes the payment, so Shopify collects your name, email, and payment details under its own policy. We never see or store your card number.

Shopify then notifies us that an order was paid. From that notification we keep only what the door needs: the Shopify order and line-item identifiers, a short confirmation code (it looks like HM-XXXX) that is printed on your confirmation, the last four digits of the order number as a tie-break at the door, the name the buyer typed for each ticket (when buying for a group, the buyer names who each ticket is for — a name, not a signature; that person still signs their own waiver), the ticket’s status, which signed waiver it is tied to, and an append-only log of every change to it.

Why: to issue exactly one ticket per seat, to tie each ticket to a signed waiver, and to check you in once at the door. Ticket records are participation records — see section 6.

3.3 Signing the waiver

Every participant signs their own waiver. Nobody can sign for anyone else. If you buy tickets, you sign yours as part of buying; everyone you bought for signs their own before the run. When you sign we store:

Your full legal name, typed — that is your electronic signature.
Your email address, so we can send you your pass and a copy of what you signed.
Your mobile number, only if you give one (it is required only if you also opt in to texts).
Your date of birth and the age it implied on the day you signed. High Mileage runs are 21 and over; this is how we know.
An emergency contact name and number, if you choose to give one. It is asked last and is optional.
Which run you signed for.
The exact text of the waiver you agreed to and its version; whether you said yes or no to the optional photo & video release, and the text you saw if you said yes; whether you said yes or no to the optional run-day texts, and the text you saw if you said yes.
Your pass code — a random code that gets you in at the door.
The circumstances of the signature: whether it was signed online or in person, the date and time, your browser’s user-agent string, and your IP address. Unlike the list, the IP is stored as-is here, because a signature record needs to show where it came from.
Whether the pass email reached you, and later, whether and when you checked in and which staff member checked you in.

Why: the waiver is a legal agreement. Its record has to be able to prove, years later, who agreed to exactly what, and when. Everything on this list serves that one purpose or gets you through the door.

Signing the waiver does not put you on the marketing list. Your waiver email is used to send your pass and your copy of the agreement. If you want run announcements, join the list or tick the texts box separately.

3.4 At the door

Staff working the door see a roster for that run on a staff device: names, pass codes, and check-in status. That is all the roster shows. Access needs a staff PIN that is never put in a web address. Nothing on the door device outlives the shift — the PIN and staff name are held only for the browser session.

3.5 Writing to us

If you email hi@highmileage.xyz, we keep the email so we can answer it and, if it was a request under this policy, so we can show we acted on it.

3.6 What we do not collect

No accounts, no passwords. You sign for yourself and get a pass; there is nothing to log in to.
No card numbers. Shopify handles payment end to end.
No location tracking. We know which run you signed for, not where you are.
No advertising identifiers, no ad pixels, no data bought from anyone.
No data from anyone under 21. See section 8.

4. Where it goes

We use a small number of companies to store and move this data. They process it to provide their service to us, not for their own purposes.

Supabase: Hosts our own database — the list, waivers, tickets, check-ins. Only our server can read or write it. No database key is ever sent to your browser.
Vercel: Hosts the website and the app, and runs the small server functions behind them. Like any host, it keeps short-term request logs.
Shopify: Sells tickets and takes payment. We see order identifiers, never card details.
Klaviyo: Sends list emails. When you join the list, your email address and the fact that you consented are mirrored to Klaviyo so it can send to you. Klaviyo also sends our texts. If you opt in to texts, your mobile number and your text consent go to Klaviyo for that reason only. Our own record stays the source of truth.
Google Workspace: Runs the hi@highmileage.xyz inbox.
An email delivery service: Sends your pass and your copy of the waiver. This is deliberately separate from the marketing list so a pass can never fail to arrive because of a marketing account problem.

We do not use any other third party to hold your personal information. If that changes, this policy changes first.

5. What we never do

We never sell or rent your details. Not to advertisers, not to data brokers, not to anyone.
We never share the list, the waiver records, or the ticket records with sponsors or partners of a run. A sponsor may hear how many people came. It does not get a name.
We never share your mobile number or your text consent with third parties or affiliates for marketing or promotional purposes. Text opt-in data and consent are never shared with any third party.
We never use waiver or ticket records for marketing. They are legal and participation records. That is all they are used for.
We never text you without a recorded consent, and our texts are only ever about the runs — meet points, start times, route changes, announcements, your pass.
We never sneak a consent past you. Email consent and text consent are separate boxes; the photo release is a separate box; none of them is ticked for you.

We would disclose personal information if the law required it — a valid court order or subpoena — or to defend a legal claim about a run. That is what the waiver record exists for.

6. How long we keep it

The list: Until you unsubscribe or ask us to remove you. After that we keep a minimal note that you opted out, so that we never contact you again by mistake.
Waivers, tickets, check-ins: These are legal and participation records. We keep them for at least as long as a legal claim about that run could be brought — in California, generally two years from the run — and longer if a claim is raised or the law requires it. See section 9 for what that means for deletion requests.
Door devices: Nothing is kept after the shift. The staff PIN and name live only for the browser session.
Emails to hi@: As long as the conversation is live, plus long enough to show we acted on a request.
Hosting logs: Our host’s standard short-term retention. We do not extend it.

We take retention seriously in both directions. Our database is built so that a waiver record cannot be casually deleted — it has to be exported and checksummed first — because destroying a legal record by accident is as much a failure as leaking one.

7. Photos and video at runs

We photograph and film our runs, and we publish some of it — on highmileage.xyz, on our own social accounts, and in recaps of the run.

Whether we can publish you is governed by the optional photo & video release in the waiver. It defaults to no. If you say yes, you can withdraw at any time by emailing hi@highmileage.xyz; we will make no new use of your image and will remove material in which you are recognizable from the channels we control within 14 days. If you say no, your name goes on the do-not-publish list our team checks before anything goes out, and we will not knowingly publish material in which you are recognizable on our own channels.

Being honest about the limits: a run happens in public, other people have cameras, and we cannot recall copies that others have already saved or re-shared. If something of you does get published by us, email us and we will take it down from every channel we control within 14 days.

The release is never used for paid advertising, never sold or licensed, and never handed to a sponsor for its own marketing. That is written into the release itself.

8. 21 and over

High Mileage runs, the website, and the list are for adults 21 and over. We do not knowingly collect personal information from anyone under 21. The waiver cannot be signed by anyone under 21 — the age check is enforced in the system, not just on the page. If you believe we hold information about someone under 21, email us and we will delete it.

9. Your choices and your rights

Unsubscribe

Email: use the unsubscribe link in any list email, or email hi@highmileage.xyz.
Texts: reply STOP to any text. You may get one final message confirming it, then nothing. You can also email us. Opt-outs are honored within ten business days. Full details in the SMS terms.

Access, correction, deletion

Email hi@highmileage.xyz from the address we have on file and tell us what you want: a copy of what we hold about you, a correction, or deletion. We will answer within 45 days, usually much sooner. We verify requests by replying to the address on record; we will not release anyone’s information to a different address.

What we cannot delete, and why. A signed waiver is a legal record, not a marketing entry. It exists to prove what you agreed to before you ran. If you ask us to delete it, we will not scrub it — we retain it for the period in section 6, and if we ever remove it we export and archive it first. The same goes for ticket and check-in records. What we can do on request is take you off every list, stop every message, remove your emergency contact if you no longer want it on file, and tell you plainly what we kept and why. We would rather say this here than surprise you later.

California residents

Whether or not the California Consumer Privacy Act technically applies to a business our size, we treat the following as your rights, and we honor them for everyone:

To know what personal information we have collected about you, where it came from, why, and who we have shared it with. (Sections 3 and 4 are that list.)
To delete it, subject to the legal-record exception explained above.
To correct anything that is wrong.
To opt out of sale or sharing — which is easy, because we do not sell or share personal information for advertising, and there is nothing to opt out of.
Not to be treated differently for exercising any of these. You still run.

Send any of these to hi@highmileage.xyz. If someone is asking on your behalf, we will need to hear from you directly before we act.

10. Cookies and your browser

highmileage.xyz sets no cookies. It stores exactly one thing in your browser: a flag (named hm_age_ok) that remembers you passed the 21+ screen, so you are not asked again on every visit. It contains no information about you. Clearing your browser’s site data removes it.

The ticketing & waiver app uses the same single flag. On staff devices it additionally holds the door PIN and the staff member’s name for the duration of the browser session. Nothing on either site tracks you across other websites.

11. Analytics

The website is built so that it can load Google Analytics and Microsoft Clarity. As of this version, both are switched off and nothing is loaded. If we switch either on, it would run only after you pass the 21+ screen, it would set its own cookies under its own policy, and we will update this page and its version first.

12. Security

Our database can only be reached by our own server; no database key ever ships to a browser. The list stores a hash of your IP, not the address. Door access needs a long PIN sent only in a request header. Payment never touches our systems. We keep the number of people and services with access small.

No system is perfectly secure, and we will not pretend ours is. If we learn of a breach involving your information, we will tell you, and we will tell you what happened.

13. Changes to this policy

This policy is versioned and dated at the top. When it changes, the version and date change with it, and a material change will be flagged on this page and, where we can reach you, announced to the list before it takes effect. We will not quietly widen what we do with your information.

14. Contact

Curative Company Inc., doing business as High Mileage
Los Angeles, California
hi@highmileage.xyz