FIG. 3B illustrates various data structures used by some implementations, including an event record 3168 i, a user profile 3163 i, and a device profile 3165 i. The event record 3168 i corresponds to an event i and data for the event i. In some instances, the data for motion event i includes event start data 31681 indicating when and/or how the event started, event segments data 31682, raw video data 31683, event end data 31684 indicating when and/or how the event ended, event features data 31685, scene features data 31686, associated user information 31687, and associated devices information 31688. In some instances, the event record 3168 i includes only a subset of the above data. In some instances, the event record 3168 i includes additional event data not shown such as data regarding event/motion masks. The event segments 31682 includes information regarding segmentation of motion event i. In some instances, event segments are stored separately from the raw video data 31683. In some instances, the event segments are stored at a lower display resolution than the raw video data. For example, the event segments are optionally stored at 480p or 780p and the raw video data is stored at 1080i or 1080p. Storing the event segments at a lower display resolution enables the system to devote less time and resources to retrieving and processing the event segments.