This policy explains what information the For The 22 website collects, how it's used, and who it's shared with. It covers this website only — not Mighty Oaks Foundation, Project Echelon, or any other organization's own website or donation platform, each of which has its own privacy policy.

For The 22 does not process donations or payments directly, and does not sell personal information.

General contact form (/contact): name, organization, email, phone (optional), the topic you select, and your message.

Sponsorship request form (/sponsors/request): contact name, organization name, email, phone, website, industry, proposed sponsorship level, proposed cash/in-kind value, type of support, a description of the proposed support, desired recognition, an optional requested mile number, how you heard about the campaign, and an optional message. See our Sponsorship Vetting Workflow for how this is reviewed.

Administrator accounts: campaign administrators sign in with an email and password to manage the review queue. This is not available to, or used by, site visitors.

Server logs: like most websites, our hosting infrastructure processes IP addresses transiently to serve requests and to rate-limit form submissions against spam and abuse. We do not maintain a database table of visitor IP addresses.

We do not use advertising or analytics tracking cookies at this time. The only cookies set are a short-lived one used during the WHOOP account-connection flow (admin-only) and a session cookie for administrator sign-in.

The 'Latest Training' snapshot on the Race page — recovery, sleep performance, day strain, and recent workouts — is the athlete's own data, pulled from his personal WHOOP account, which he has connected to this site himself. It is not collected from site visitors, and visitors cannot connect their own WHOOP accounts through this site.

This data is displayed publicly as part of telling the campaign's story. The underlying account credentials (OAuth tokens) are stored server-side only and are never exposed to the browser.

To respond to general inquiries and sponsorship proposals.

To evaluate sponsorship requests through our review process before any sponsorship, gift, or benefit is accepted or a sponsor is recognized publicly.

To administer the campaign — for example, tracking fundraising progress and mile status.

To protect the site and its forms from spam and abuse.

Supabase: our database, authentication, and hosting infrastructure provider. Form submissions and administrator accounts are stored in Supabase.

WHOOP: provides the athlete's training data displayed on the Race page, as described above.

Jakroo: our third-party merchandise/team-store provider. If you buy Tri For The 22 merchandise, your order, sizing, shipping, and payment-card information are collected and processed by Jakroo on its own platform, not this site. We do not collect or store your payment-card information, and we may receive only limited order or transaction information from Jakroo. Jakroo's own privacy policy and terms apply to that purchase.

We do not currently use an email delivery provider or analytics provider. If we add one, we'll update this policy first.

Donate buttons route to each beneficiary nonprofit organization's own, separately operated donation platform — see the disclaimer on our Donate and Partners pages. We don't receive or process your payment information for those donations.

We keep contact and sponsorship request submissions, including the sponsorship review history, for as long as reasonably needed for campaign administration and recordkeeping (including declined or withdrawn sponsorship requests, which we retain for audit purposes rather than deleting).

If you'd like your submission removed, contact us using the form on this site and we'll evaluate the request. A fixed retention schedule is under legal review and will be published here once finalized.

This site is not directed to children under 13, and we do not knowingly collect personal information from children.

You can decline to submit a form — nothing on this site requires you to provide personal information to browse it.

Depending on where you live, you may have additional legal rights over your information (for example, under CCPA or GDPR). That jurisdiction-specific language is under legal review and will be published here once finalized; in the meantime, contact us using the form on this site with any request.

We'll post any changes to this policy on this page and update the date below.