How phone measurements become driving information.
Avyro · Evolute LLC
Measurements & safety
Last updated: October 7, 2026 · Applies to Avyro by Evolute LLC
Native speed, without invented continuity
Avyro uses the operating system’s valid native speed estimate and its reported accuracy. GPS and platform location services can be affected by signal obstruction, multipath, device settings, hardware, and missed updates. A valid speed reading is not discarded merely because its uncertainty is large. The current analysis does not add another averaging filter or replace gaps with position-derived or invented speed values. We do not claim to duplicate Apple Maps, Google Maps, or Waze algorithms.
What Momentum measures
Momentum is an informational score from 0 to 100. It combines the supported Smoothness and Speed care components, giving Smoothness slightly more weight. When both exist, the weights are 0.40 and 0.35, normalized by their sum; the final result rounds down. If only one is supported, that component supplies the score. An absent component is not treated as 100 or zero. Very short trips or insufficient measurements can remain unscored.
Smoothness uses retained hard-braking and rapid-acceleration events per distance and changes in acceleration from sufficiently precise consecutive speed estimates. Speed care uses the duration of sustained speeding among intervals with decisive speed and posted-limit evidence. Missing or ambiguous intervals do not earn perfect-driving credit and do not cause a speeding deduction.
Road limits and driving moments
Posted limits come from matched road data, currently OSM-derived regional packages with limited regional coverage. They can be missing, outdated, or matched to a nearby road. The actual posted sign and traffic law control. Speeding assessment uses a buffer of the greater of 5 mph or 8% above the matched limit, reported speed uncertainty, and a sustained run of at least five seconds. That analysis buffer is not permission to exceed a legal speed limit.
Maneuvers use stricter precision and physical-continuity checks than speed display because differentiation amplifies noise. GPS gaps are not driver penalties. Sharp-turn candidates are review prompts and are excluded from score deductions; vehicle-frame cornering is not calibrated. Abrupt braking can be the correct response to a hazard. High-confidence phone-use detections can reduce the drive score.
Phone-use detection, confidence and alerts
Phone-use detection combines native driving speed, screen-state evidence and sustained handset motion. It does not inspect messages, app content or touches in other apps, identify a passenger, or establish texting. A confidence percentage expresses the strength of the available evidence; it is not a measured probability or a guarantee of accuracy. Vehicle vibration, mounts, signal gaps and platform restrictions affect results.
Android uses interactive-screen and dismissed-keyguard state; a recent unlock strengthens the evidence but is not required. On iOS, file-protection availability is indirect and can differ from the current screen-lock state. Score-affecting iOS detections require Avyro to be active with sustained handset motion. Phone use in other apps or while Avyro is suspended may not be detected. CarPlay or Android Auto controls alone do not supply handset-handling evidence.
Qualified detections require confidence of at least 80%. The drive-score deduction is one point per four detected seconds, rounded up, capped at 20 points per drive. Missing evidence earns neither phone-use credit nor a deduction. An individual passenger-use or incorrect-detection correction removes its deduction; undo restores it. Previously saved assessments are retained.
Accepted coaching or full-ride sharing can send a Family alert when a qualified event is recorded. At most one phone-use alert is sent per drive. Alerts depend on connectivity, permissions and platform delivery. Event time, duration and confidence can be shared; notification text contains no route coordinates or message content. Corrections update the shared report and cancel alerts still awaiting delivery, but cannot retract a notification already delivered. Check-in-only agreements do not include phone-use alerts.
Coverage, history and privacy
Detailed Evidence and retention screens explain measurements, coverage, rejected-fix diagnostics and assessment versions separately from the main trip story. GPS position coverage, native-speed availability, posted-limit availability, and decisive speed assessment describe different things. Imported, legacy, passenger or expired records may not qualify for current comparisons or milestones. Privacy zones hide route points without erasing the underlying local record.
Use results constructively
A score of 100 is not a claim of perfect driving, complete measurement, or freedom from risk. The formulas are product parameters, not a population-validated safety model. Device recordings do not establish fault, intent, legal speed compliance, or fitness to drive. Discuss the circumstances of a moment rather than treating a report as a verdict.
Review only when parked. Family check-ins depend on recording, connectivity and service delivery, and may arrive late or not arrive. Avyro does not summon emergency help. In an emergency use the appropriate local emergency service.