HiRoxHiRox

Last updated 3 November 2026

Privacy

This covers the HiRox website, waitlist, member accounts, Race Partners, results, newsletter and course advertising at hirox.app. HiRox is made by Teddy App Labs, LLC.

What we collect when you apply

What other visitors see from applications

The live map, the globe and the join banners show your initials, your city, your division and when you joined. If you tick the box, your first name and the first letter of your surname are shown instead of your initials. Your surname and your email address are never shown.

Why we use it

To run the waitlist: to know who applied, to invite applicants in waves before launch, and to email you about access to HiRox. We do not sell your details or use them for advertising.

Who handles it for us

Cloudflare hosts the site, stores the waitlist and runs Turnstile, the check that tells people from bots. Turnstile reads signals from your browser for that check only.

PostHog processes the anonymous website events described below in its US cloud. Our server sends only the limited event fields; it does not forward your IP address, browser headers or application details to PostHog.

Newsletter subscriptions

The newsletter is a separate, optional subscription. Applying for early access does not subscribe you. When you sign up we store your email, subscription status, signup dates, and the wording and version of your consent. Submitting the newsletter form subscribes you directly; no email confirmation is required.

Resend handles welcome and newsletter delivery, contact preferences, and delivery failures or spam complaints. We keep delivery references and the minimum information needed to prevent duplicate sends and honor opt-outs. We do not add tracking pixels or rewrite links for click tracking in these templates.

Legacy unconfirmed records are removed after 30 days without another signup attempt. Queued message content is cleared after completion or cancellation; minimal delivery and opt-out records remain to honor your preferences. You can unsubscribe using any newsletter's link or ask us to delete your subscriber data.

Public race results

Result pages use public race data from HYRESULT, with source links and update information. These records can include a racer's published name, team members, category, age group, country, ranks and times. They are separate from applications and newsletter contacts. We do not infer a subscriber's identity from a race result. Event and result pages may retrieve fresh source records through our server; your browser's IP address and cookies are not forwarded.

Write to us to report an incorrect result or request removal of a record from HiRox. Changes made on the original results site may take time to appear in a cached copy.

Member accounts and athlete profiles

We store your email address to sign you in using a single-use code delivered by Resend. Signing in does not subscribe you to marketing. An essential HttpOnly cookie, hirox_member, keeps you signed in for up to 30 days. Signing out revokes that session. We store hashed session tokens and code-verification records, with short-term rate-limit records to protect sign-in.

Your profile can contain a display name, city, bio, photo and optional Instagram, X, TikTok, YouTube and Reddit links. These are profile links, not connected social accounts. Your email is never public. Your profile and photo remain private unless you request publication and HiRox approves the current version. Changes require another review. Approved public profiles can show your full race name and linked results.

Race claims and Race Partners

To claim a result, you select the participant and privately upload a registration confirmation with ticket and QR codes covered. The document and review notes are stored by Cloudflare and are accessible only to you and authorized HiRox reviewers. Proof documents stay private after approval. We do not automatically delete them after review; contact hello@hirox.app to request removal or dispute an ownership link. The first approved claim supplies your locked profile name.

Partner listings store your chosen race, date, category, goal and whether you need a partner or are available. Approved listings appear publicly only with an approved, published profile. Interest requests and accept/decline decisions are private to the involved accounts and authorized administrators. Accepted connections use the social links each racer has chosen to publish; we do not disclose email addresses. Accounts, profiles, listings and claim records remain stored until removed through a reviewed request. You can unpublish your profile or close your listings in your account.

Account pages record anonymous navigation and request outcomes. Analytics never includes your account ID, name, email, sign-in code, social links, photos or claim documents. Contact hello@hirox.app to access, correct or request deletion of your account, uploaded photos or claim documents.

Course advertising

If you apply for a virtual course placement, we store your brand, contact email, website link, banner image, selected race and space, review status and booking/payment references. We use these to review and operate your placement and resolve payment issues. Your contact email and unapproved artwork stay private. Only approved, paid placements can publish the brand, image and destination link.

A booking-specific essential HttpOnly cookie lets this browser access its application for up to 30 days. Local storage remembers the application ID until you clear site data; that ID alone does not grant access. Advertising applications do not subscribe you to the newsletter. Banner images are served from HiRox, with no third-party ad tracking pixels.

When payments are enabled, Stripe hosts checkout and processes your payment information for Teddy App Labs, LLC. HiRox stores payment references and status, not your card number. Visiting an advertiser's website takes you to that site's own privacy practices. Contact us to access, correct or request deletion of an advertising application.

Private editorial access

Editors use an essential, signed session cookie that lasts up to 12 hours. It is not an advertising identifier and is not set for ordinary visitors.

Photos on the race map

The city photos come from Wikimedia Commons under free licences, and each card credits its photographer and licence. They are served from hirox.app, so viewing them sends nothing to Wikimedia.

Cookies and analytics

After you apply, the page keeps a cookie, hx_applied, on your device for a year, so it remembers your application when you come back: your number, your first name and your place on the map. Our servers do not read it. "Apply for another racer" deletes it, and so does clearing your browser's cookies.

We use anonymous analytics to understand visits, return visits, race-page interest, the application journey, newsletter signup, account sign-in, profile updates, race claims and Race Partners. Events include page views, Apply and race-link clicks, scroll milestones, form starts, submission attempts and whether an application succeeded, already existed or failed. Newsletter events also record when the form becomes visible, interaction starts, a submission is attempted and whether it creates a new subscription, changes nothing or fails. Account and Race Partners events distinguish attempts, accepted requests and failures; acceptance is not proof of email delivery, moderation approval or a completed partner match. Individual result and athlete paths are replaced with generic route templates. We record the published page path and a broad traffic-source category such as Google or Instagram, never full referring links or URL query values.

A random visitor ID is saved in your browser's local storage for up to one year. A separate tab-session ID renews after 30 minutes without a tracked interaction. These IDs are not linked to your application or subscriber record. We do not send names, email addresses, form answers, location or security-check tokens to PostHog. We do not use advertising trackers, session recordings or automatic form capture.

Do Not Track and Global Privacy Control signals turn analytics off. You can also turn it off here; this removes the analytics visitor and session IDs from this browser and stops future events. Clearing site data resets this choice.

Analytics choices are available when JavaScript is enabled.

How long we keep applications

We keep your application until the waitlist closes after launch. Then we delete it, unless you have become a HiRox user. You can ask us to delete your application sooner. The browser-storage lifetimes described above are separate from this application-retention period.

Support and feature requests

When you use our contact form, we send your name, email address, request type, subject and message to the HiRox team through Cloudflare Email Service. Your email is used as the reply address. These messages are held in our support mailbox to handle your request; they are not published, added to the waitlist or used to subscribe you to marketing. Please avoid including passwords, payment details or private documents. You can email hello@hirox.app to request deletion of your support correspondence.

Cloudflare Turnstile and a short-term IP-based request limit protect the form from spam. We do not store the form contents in the website database or include them in analytics.

Your choices

Write to hello@hirox.app to see, correct or delete your application or subscription, request a result correction or removal, or take your name off the live map.