Really? Or are you kidding?

I'm not sure. I had never considered that it might be
listening. That raises a bunch of questions, like where are the microphones and what kinds of sounds count as triggers?
Interior mic (the one used for voice commands and phone) and stuff like glass breaking or other high pitched, sharp sounds that indicate a collision with the vehicle by something.
I'm not sure on the exact location of the "watch areas" for the cameras (Might be something to check sometime), but substantial change between frames in any watch area will cause a sentry event. After the initial V10 release I had over 780 events from being parked in my closed garage. Found that the camera brightness levels were fluctuating wildly with the flicker of the rectified LED lights.
Soft reboot corrected the brightness levels, but I was still getting 20-50 a day. I reviewed some and checked the trigger moment, looking for "change" in the frames. Turned out it was the fact that the garage door didn't close completely, leaving about half an inch of daylight coming in under the door. Anything that cast a shadow under the door - birds, cats, kids, whatever - would trigger the sentry. Adjusted door. Solved.
After all that, my point is:
It would be really spiffy if the sentry recording would include an overlay indicator of the trigger zone, and maybe indicator of the trigger camera/time in either a text file or the videos' filenames