Family viewPrototypeDrives show up here.
After a drive, the driver taps Send to family in AutoSight and sends you the link. Open it on this phone and the drive appears here: the score, the drift moments, and a replay of each one. No video, no location. Everything stays on this device.
Sample data, generated to show how the view works. It isn't a real driver.
Week summary
Family goal
Focus Score per drive, last 4 weeks
Show as a table
| Drive | Score | Drift moments | Minutes |
|---|
Worth talking about
Integrity
Did AutoSight actually see the drives? Covered cameras, unplugging mid-drive, and miles driven with the AutoSight Camera off show up here.
Drives
Moment Replay
Shaded: attention off the road. Red line: alert. No video is ever recorded.
Automatic sync
OffDrives arrive here on their own after each trip, no links to send. Trips are encrypted on the driver's phone with a key only your family's devices have, so AutoSight's servers can't read them.
- Send this to the driver. They open it on the phone they drive with and say yes:
- For the AutoSight Camera, use this pairing code:
Save it as
autosight-pair.txton the camera's SD card (add the driver's first name after a space), or runpython -m autosight_edge pair CODE --driver Nameon the unit. - Optional, for another parent or guardian:
The driver link and camera code can only send drives: they can't read, change, or erase anything. The parent link can see and erase everything, so send it only to a co-parent or guardian.
Add drives
From the driver's phone: open the link they send. From the AutoSight Camera: import its trip files or a family bundle (python -m autosight_edge family-export).