OpenLevo exists because your bike generates fascinating data and you should own all of it. Your data never leaves your phone unless you export it, and the app never shows you a number it can't stand behind.
Pairing, riding, recording, stored routes, and range planning work with zero network. There is no server because there is nothing a server should know about your rides. Your activities are files on your phone and a stored ride can be exported as GPX or FIT.
Your bike's serial number and your home location are excluded from every share and export unless you explicitly opt in. No analytics SDK ships in the app, and this website carries no trackers, no cookies, no fingerprinting. The same boundary holds for AI: the Studio's assistant connector runs on your Mac, reads only files you name, and never uploads footage or ride data.
Your rides are files on your phone, not rows in someone else's database. Export a stored ride as GPX or FIT, or save its measured track into Navigate as a route you can follow again. FIT keeps rider power in the standard channel and recorded motor power in its own named developer field. A ride recorded on the Watch reaches your Mac the same way it was recorded: over your own Wi-Fi, code-paired and encrypted, confirmed on the watch, with no cloud in the path.
Owner Research Mode is a clean-room evidence tool—not a secret control panel.
Face ID, Touch ID, or the device passcode protects Research Mode. A session exists only after an explicit tap while connected, stays in memory on that iPhone, and disappears when cleared or when the app process ends.
Serials, session IVs, firmware and key material, pairing data, advertisements, names, device identifiers, location and opaque log payloads never enter the research record.
OpenLevo has no research cloud or remote developer access. The only handoff is the redacted JSON file you deliberately send with the iOS share sheet; its replay path is offline and cannot contact a bike.
These are firm commitments, guarded by automated tests. They will not be re-opened.
No slider, no hidden gesture, no "debug menu". Removing the assist cutoff legally reclassifies your bike as an unregistered motor vehicle — illegal on trails and paths, voiding warranty and insurance, and shifting crash liability onto you. It also overruns the motor's thermal duty cycle. Worst of all, it's the single biggest reason e-MTB trail access gets revoked for everyone. No code path in OpenLevo writes the speed-limit parameter — and a regression test proves it on every release.
The protocol is reverse-engineered. Writing unverified parameters risks a configuration your dealer can't recover. The Studio exposes an honest preview editor, but no executable tuning write control; hardware validation and read-back come first.
Without a validated recovery path, flashing firmware can brick a motor. OpenLevo reads version information and nothing more.
The rider stays in control. Preview controls cannot execute a write. Any future write requires a standing-still bike and an explicit confirmation showing exactly what changes; nothing may optimize itself mid-descent.
Every number carries its provenance — measured, derived, or estimate. Range projections wear a ~ and a confidence band that widens when the model knows less.
Recording is phone-authoritative and journaled to disk as it happens. A Bluetooth drop, a locked screen, or even a crash costs you seconds of data, never the ride.
Honest status, like everything else here.
The core ride stays consistent while each system contributes only the channels it actually provides.