Ride Record Report

Ride Record Report

Regarding legal issues relating to storage/retention of submitted videos, I propose the following:

The data stored on RideRecordReport would be:
    Email address: clear text.
    Password:      encrypted AES-256 {user has the key}.
    Question:      encrypted AES-256 {server has the key}.
    Answer:        encrypted AES-256 {server has the key}.
    VideoStorage:  encrypted AES-256 {user has the key}.
		   options 1-E-[a-p] above.
  

If a subpoena were given, the only thing RideRecordReport could provide is the registrants email address, their question and answer. If video storage selection is RideRecordReport, see: (1-A-E-d) below.

(1-A-E-p) RideRecordReport:

I did some timing/size testing using AES-256 encryption on a small 111K video file, which took less then a second: video is 111K, encrypted video is 111K, and implies there is almost no cost in CPU cycles and storage to encrypt the video. If the video were encrypted, and only the user knows the key, would this provide legal protection? If RideRecordReport needed the video, reach out to the user who submitted it and ask.

Thank you for your interest in RideRecordReport.