What River People records during an active run
When you start active tracking and grant the necessary location permission, River People may collect GPS track points, route, distance, duration, speed, start time, and end time. Background location can be used while an active run continues.
Tracking stops when you end the run. Device settings, battery controls, canyon walls, tree cover, GPS quality, and operating-system behavior can create gaps or inaccurate points. Review the route instead of assuming every recorded coordinate is precise.
Review before saving
A paddling run contains more than telemetry. River People's phone review flow can connect the record to a river section, vessel, notes, skills, media, and gauge levels at the start and end where available.
Automatic section selection considers location near both the put-in and take-out, but paddlers should confirm the suggested section. Overlapping runs, alternate access points, and noisy GPS can make an automatic match imperfect.
Build a paddle log you can learn from
Distance and duration help reconstruct a day, while vessel, flow, notes, and skill records add context for comparing later runs. Record only what you directly know. If a gauge is indirect or delayed, note that limitation rather than treating it as the exact flow on every rapid.
Photos and videos can preserve useful memories and observations. Capture media only when it is safe, respect other paddlers, and use the visibility setting appropriate for each item.
Choose who can see each part
River People supports feature-specific visibility such as public, crew-only, and private content. Media can have per-item privacy behavior. Review the selected audience before saving sensitive routes, locations, injury details, or photographs.
Blocking and visibility settings reduce interactions but cannot undo information already shared or captured by others. Learn more in the River People Privacy Policy.
Remote rivers require resilient saving
Runs may end where network service is weak. River People includes offline-aware synchronization and client-key deduplication behavior intended to reduce lost or duplicate saves during retries. Keep the app installed and allow pending work to synchronize when a connection returns.
For watch-recorded sessions, final authentication, review, and saving may still require the companion phone. See the wearables guide for platform details.