Privacy by design
The Free Check stays on the page. Founding-rider enrollment stores a small, explicit request. Personalized fit media, accounts, payment, and results remain gated.
The Free Check runs on the page and saves nothing. A founding-rider request is stored separately for program review, but it does not create a Roth account or connect an identity to the phone app. Public Apple, Google, and email account access is not enabled.
The Free Check runs in the browser. Roth does not upload or save its answers and does not use them to create an account.
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.
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.
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.
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.
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.
Use the request reference and reply email at /beta/withdraw. The response is deliberately non-enumerating.
Public account creation, phone-app account continuity, checkout, personalized result delivery, and Expert Review are unavailable. The current customer-facing flow does not collect riding video, measurements, payment information, a fit history, or a personalized result.
Private recording, short media-retention windows, export, authenticated deletion, fitter access, and research controls are product requirements under development—not controls a public visitor can use today.
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.
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.
No account required
Your Free Check answers stay in the browser and are not saved to a Roth account.