Useful guidance starts with honest limits.

What the product combines

Your reported concerns, bike identity, setup checks, recorded movement and follow-up rides are considered together. Source-linked fitting rules provide a structured review. Manufacturer and identified retailer charts provide frame-size starting points.

The purchased Steve Hogg material informed the rule catalogue and review process. It does not make our camera system independently validated, certify the product or imply Hogg’s endorsement. Paid resource text is not reproduced in these guides.

Current validation status

Automated tests check calculations, safety gates, source-range matching and data ownership. These are software checks. We have not completed an independent rider study, quantified clinical accuracy, proved injury prevention or demonstrated aerodynamic improvements.

The learning articles are product guidance, with independent fitter review still pending. The model guides reuse cited catalogue records; they do not certify each used-bike listing or current stock.

Recording quality

Side-view recordings need a level, visible and securely supported setup, adequate warm-up, at least 20 detected cycles, 100 usable samples and 75% usable frames. Uploaded clips need at least 20 seconds and confirmation of at least two minutes of prior steady riding. Live recordings currently require at least two minutes. Passing these checks is not proof of measurement accuracy.

Before/after replay aligns two manually selected moments. It does not automatically match cadence, detect true pedal dead centres or calculate new joint angles. Different speeds can drift apart; compare marked stills or a short aligned segment.

Where your data goes

Video analysis and saved browser footage stay on the recording device. Download important videos to your device’s files. Browser storage can be cleared or evicted. Footage is not copied by account autosave or the two-device monitor.

Sessions, symptoms, measurements, optional movement notes and saved bike comparisons are stored with your account. The same-account monitor exchanges recording status and measurement summaries for a limited session; it does not stream video. No paid cloud video archive is active.

The review pack is a file you download. Nothing is sent to a practitioner automatically. Choose the recipient and files yourself, and check the pack before sharing because it includes your reported concerns.

Email accounts

When email sign-in is enabled, we store your verified email with your account and send a one-time code through Resend. Sign-in emails contain no fit answers, measurements or recordings. Necessary sign-in cookies keep you signed in for up to 30 days; they are not advertising cookies.

Codes expire after 10 minutes and have limited attempts. Expired sign-in records are removed during subsequent sign-in activity. Short-lived request limits use protected identifiers to reduce unwanted emails. Your account email remains stored with your account. You can sign out of all email sessions from your account.

Voluntary rider trial feedback

The feedback form sends only the answers you enter: device and browser details, task results, an optional ease rating and your comment. It does not automatically attach footage, fit records, measurements or an email address. Leave health details and private session links out of comments.

Your report is linked to your account so you can reload, update or delete it. The site owner can read submitted reports and mark their review status. Reports stay stored until deleted; you can delete your report on the feedback page. This is voluntary product-testing feedback, not an anonymous survey or an accuracy study.

Website problem reports without an account

The public help form sends the topic, device and browser choices, and the comment you enter to the site owner. It does not attach your account, fit, email address or footage. Leave identifying details, health information and private links out of comments. No email is requested, so individual replies are not available.

A daily protected identifier derived from the connection address limits unwanted submissions; the help report does not store the address or full browser details. Reports older than 90 days and expired request limits are removed on the next report submission or owner review. Reports are separate from optional visitor analytics. Open help or report a problem.

Optional private test counts

Owner test-event recording is off by default and can be enabled for the owner’s browser in the owner-only launch workspace. When enabled, named events and broad page categories are counted by day under the owner’s account. No health answers, footage, measurement values or session IDs are sent in these events. The counts are not anonymous to the service because account ownership protects access. The owner can turn recording off and delete stored test counts in the launch workspace. Google Search Console is connected for public-page indexing and search performance. It does not connect to private fit-session records. Visitor analytics and service progress reporting are described below.

Visitor analytics and fitting progress

Optional visitor analytics starts only when you choose “Allow analytics”. It records public page names, broad traffic source, a recognised trial-campaign label, device category and named actions such as opening a fit or downloading a summary. Random browser and visit identifiers distinguish visits; a browser is not a verified person. Visits restart after 30 minutes of inactivity and the browser identifier expires after 90 days. Full URLs, query strings, search terms, names, emails, fit answers, measurement values and recordings are excluded from our analytics payloads.

When connected, Google Analytics receives the same limited named actions after consent, with advertising features and automatic enhanced measurement disabled. Google may process device, connection and approximate location information as part of its service. Our own reporting stores no IP addresses or full user-agent strings. You can change your choice using “Analytics choices” in the site footer. Declining does not prevent a fit, and withdrawing stops future visitor collection; it does not erase previously collected reports.

Separately, saving a fitting session records minimal service milestones: the furthest saved step, basic or video route, completion at follow-up planning, and whether a follow-up ride has been saved. An opaque record key prevents repeated saves and two devices from producing duplicate completions. These operational milestones do not contain the answers, measurements or video. If you allow visitor analytics, we associate the milestone with your random browser identifier, broad source and device category; otherwise these are unknown. Owner tests are excluded from customer reports.

The owner can see aggregate reports. A session with no save for 24 hours is labelled inactive, not permanently abandoned. Event records older than 90 days, and visit or fit-milestone records inactive for 90 days, are deleted on the next analytics collection or report refresh. Deleting a fit also removes its operational milestone record. Google Analytics has its own retention settings. Analytics began after launch; it does not reconstruct earlier visitor history.

When more help matters

Follow the session’s safety questions. Stop self-adjustment when the bike cannot be safely controlled or when symptoms call for an individual assessment. A qualified fitter can help review sustainable contact positions; a clinician can assess health concerns.