I wouldn't say their response "misses the point", I'd say it's a lazy response and they don't care (or have enough financial motivation) to dive deeper into the

I wouldn't say their response "misses the point", I'd say it's a lazy response and they don't care (or have enough financial motivation) to dive deeper into the underlying cause of the problem. I really like your idea of a physical pairing procedure. It's not a large price to pay for dramatically increased privacy. Some other possible partial-solutions I initially thought of: 1.) Don't allow users to create their own password. Generate a strong password for them, and only show it to them once upon password creation/change. (like how API secret keys are often only displayed once upon creation) --- this would eliminate the "same password on multiple sites" issue 2.) Require a device whitelist where some type of fingerprinting/calibrating is done upon initial login by each device added to the list. 3.) Geofence logins to a pre-specified radius surrounding the camera location. E.g. if the parents work < 10 miles from home, they can set up a radius of 10 miles and understand that if they travel further than 10 miles away from home they won't be allowed access. --- this would be hackable, but would at least add another layer of protection.