What the current website collects—and what it does not.

Roth’s current public data boundary

Mountain Brook Run LLC operates Roth Bike Fit through the Roth Cycling Labs product organization. This draft covers the public website, Free Check, general contact flow, and first-party founding-rider enrollment.

The Free Check stays on the page and saves nothing to a Roth account. Public Apple, Google, and email account access is not enabled, so the current website does not create an internal rider identifier or connect an identity to the phone app.

The enrollment form stores a bounded request

The founding-rider form submits directly to Roth through the website and stores the request in Roth’s private operations database. It does not require a configured mail application.

The enrollment form is not designed to collect health information, symptoms, payment data, passwords, measurements, riding video, private report links, or identity documents.

• Name and reply email
• Supported bike category
• Phone platform and indoor setup
• Country or region
• A short non-medical fit goal
• Permission to contact the rider about this request
• A separate yes-or-no case-study follow-up choice

Program contact and case-study follow-up are separate

Roth uses the request to check current program fit, manage the review queue, reply about the request, and record the rider’s separate case-study follow-up choice. A request does not create an account, take payment, guarantee an invitation, or authorize publication of a case study.

Contact permission and case-study follow-up permission are recorded separately. Case-study follow-up is optional and does not itself authorize Roth to publish a name, image, quote, result, or story.

After a successful submission, the website shows a stable reference number and confirmation page. Automated acknowledgement email delivery is not enabled yet, so the on-page reference is the reliable receipt.

Website delivery and private database storage

Vercel delivers and protects the website and application endpoint. Neon stores the private enrollment record for Roth. Those providers may process the information needed to provide those services under their own service and security controls.

Website delivery and abuse prevention may involve an IP address, browser or device details, requested page, request time, and security events. The enrollment database stores keyed security digests for rate limiting rather than the visitor’s raw IP address or user-agent string.

Named funnel counts without rider or form data

Roth uses privacy-focused aggregate page and funnel counts to understand which public information is useful and where visitors leave the readiness, enrollment, account, and app-continuation paths.

Vercel Web Analytics may process an event time, page or funnel route path, referring site, coarse location, device type, operating system, and browser for aggregate reporting. Roth’s seven custom funnel events contain only an approved event name and no custom properties.

Analytics runs only on rothbikefit.com. Roth removes query strings and fragments before a page view is sent and suppresses page views on sensitive and operational routes. A custom funnel event includes its approved event name and current route path, while its origin URL is normalized to the site root; it includes no query, custom property, identifier, or form value. Roth does not send Free Check answers, form entries, names, email addresses, health information, payment information, measurements, video, report data, account identifiers, or enrollment references.

Vercel Web Analytics does not use cookies. Vercel describes the analytics records as anonymous aggregate data and resets the request-derived visitor hash each day; the visitor-session hash is discarded after 24 hours.

The current Vercel Pro reporting window is 12 months. Vercel states that aggregate analytics data is guaranteed to be viewable for that window and may be stored longer. Roth reviews aggregate trends rather than reconstructing an individual browsing session.

• Eligibility check started
• Eligibility result reached
• Enrollment form started
• Enrollment request saved
• Account path started
• Account setup completed
• App-continuation page opened

The contact form and beta form work differently

The general contact form prepares a draft in the visitor’s own email application. The website does not transmit or save those contact-form fields. If the visitor sends the message, the visitor’s email provider and Roth’s email provider process it.

Do not include health information, payment details, passwords, identity documents, private report links, measurements, or riding video in a general email.

No advertising cookies or cross-site tracking

Roth has not enabled advertising, remarketing, cross-site tracking, or analytics cookies. Privacy-focused Vercel Web Analytics is enabled for aggregate public page and named funnel counts. The Free Check does not save answers in a cookie or rider profile.

Website delivery and abuse prevention may use limited request information or browser storage that is necessary to provide and protect the public pages and enrollment endpoint. Public Clerk account-session storage is not active.

Vercel Web Analytics does not use cookies. Vercel describes the analytics records as anonymous aggregate data and resets the request-derived visitor hash each day; the visitor-session hash is discarded after 24 hours.

Withdrawal stops request contact; it is not hard deletion

A rider can use the first-party withdrawal page with the request reference and reply email. Roth returns the same accepted response whether or not a matching request exists. For a match, withdrawal closes the review queue and records revocation of granted contact and case-study follow-up permissions.

Roth has not published or implemented an automatic deletion deadline for founding-rider requests. A withdrawal changes the request to withdrawn and retains limited request, consent, status, and security history; it does not hard-delete that history. A rider may contact Roth with an access, correction, or deletion question while the final retention procedure is under review.

A founding-rider enrollment request is not a Roth account. Withdrawing an enrollment request and deleting a previously issued Roth account are separate operations.

The current public website does not create a Roth account. A person who was previously issued a Roth account can use the direct deletion control in the Roth app; public website sign-in remains closed.

Use /beta/withdraw for a founding-rider request. Use hello@rothbikefit.com for an access, correction, privacy, or previously issued controlled-account question.

Personalized fit media and payment remain gated

The public website does not currently collect a rider’s fit measurements, riding video, payment information, or personalized result through the customer-facing flow. Roth must publish and test the applicable media, retention, access, export, deletion, billing, and privacy controls before those capabilities open.

Who operates Roth and what this draft covers

Mountain Brook Run LLC is the legal operator. Roth Cycling Labs is the product organization for Roth Bike Fit. Questions may be sent to hello@rothbikefit.com.

July 26, 2026 · WEB-11 analytics and consent alignment · revision 2. Revision 2 adds the live privacy-focused analytics boundary and the exact-consent standard for any future rider story. It keeps public accounts and website-to-app continuity gated and confirms that checkout, personalized results, and Expert Review are unavailable.

Business and legal approval pending. Paid-service terms are not in effect · payment is unavailable.