Support

1. Open the iOS app → Settings → Web Account and confirm it says Connected as <your email>. If it doesn't, tap Sign in with bumpyride.me and re-pair.
2. If you've recently revoked tokens at /settings/tokens, your previous token is invalid; re-pair to mint a fresh one.
3. Confirm the phone has working network connectivity (other apps can reach the internet).
4. If none of the above helps, email us with your account email and the approximate time of the rides that aren't showing.

Recording a ride requires GPS while the phone's screen is off — for instance, when it's in your pocket or on a bar mount and you're not looking at it. The app stops collecting location the moment you tap Stop. The iOS background-location indicator stays visible on your status bar for the entire ride so you always know the app is recording.

A per-ride tag indicating whether the phone was riding on your body (in a pocket, hydration pack, etc.) or on a fixed bike mount. Body-on rides are mechanically damped — the vibration the phone measures is softer than the actual road — so we tag and track them separately. The app auto-detects pocket mode from the recording, and you can override it at save time or later from the ride's menu.

You can filter the iOS Bump Map by mode (All / Mounted / Pocket), and the same filter is available on your web bump map.

When you save a ride, BumpyRide scans the points for sustained decelerations — runs above 2.5 m/s² (≈ 0.25 g) lasting at least 0.8 seconds, refined with the same horizontal-acceleration signal the brake detector uses live. Adjacent events within three seconds collapse into a single higher-peak event. The detector runs on-device, so legacy rides recorded before iOS v1.3 get reprocessed in the background and re-synced to the web. You'll see each ride's brakes as red dots on the route map plus a list with time-into-ride and peak in g + m/s².

Whenever you feel like flagging a near-miss — a driver who cut you off, a door that swung open, anything you'd want remembered as a dangerous spot. The button captures only location and time so you can tap it without looking. A five- second undo banner appears after each tap. You can also long- press an entry from the ride's playback view to delete it later.

Aggregated across consenting riders, close calls become an obvious overlay on the public map for intersections that repeatedly produce them — useful as advocacy data for your local cycling group or DOT.

Three layers on the same 20 ft grid, switchable via tabs on the public map page: Bumpiness, Hard brakes, and Close calls. Each layer renders only cells where at least three distinct opted-in riders have contributed data on that specific layer — so a single rider can't publish a route by toggling sharing on.

Toggling sharing on (or off) is one decision that covers all three feature types together; there's no per-feature opt-out. If you'd rather not publish close calls, leave sharing off entirely.

A self-service delete flow is on the roadmap. In the meantime, email me@jordaneccl.es from the address tied to your account and we'll delete the account, every ride, every token, and every contribution to the public maps within seven days. We'll confirm by reply.

The iOS app has a per-ride Export to Photos action that saves a colored route image with a stats panel — handy for sharing. A full data export (JSON of every ride and its accelerometer windows) isn't built yet; it's on the roadmap. If you need an export today, email us — we can pull a per-account dump.

Email me@jordaneccl.es with:

• iOS version (Settings → General → About → Software Version).
• BumpyRide app version (the app's Settings tab).
• A description of what happened and what you expected.
• If reproducible: rough steps that reliably trigger the bug.

Screenshots, screen recordings, or sample ride exports all help.