A doorbell camera watches your street and answers to its manufacturer. You can look at what it recorded; you do not hold it, and you cannot say who else can. The proposal here is narrower than a privacy argument and harder to dismiss: give a citizen their own eyesight — one recording that belongs to the person the way a body camera belongs to an officer.
The procurement record gives that proposal an uncomfortable shape. Amazon Web Services is the largest government cloud vendor in this register by a wide margin: $42.9bn across 27 awards, and 93 deployments in 21 of the 35 geographies tracked. Its GovCloud capability list includes Amazon Rekognition — face detection and comparison across image and video. The company that sells the doorbell also sells the platform.
That is a statement about concentration, not a connection between the two, and nothing in this record shows one. What it does show is who has a column. Across 1,922 procurement entries, ten describe an individual. All ten are litigants.
- AWS: $42.9bn across 27 awards; 93 deployments across 21 of the 35 geographies in the register
- Amazon Rekognition — face detection/comparison and image/video analysis — listed under AWS GovCloud (US)
- 10 of 1,922 procurement records describe an individual; every one of them is a litigant
- Ring appears nowhere in this register: the consumer product sits outside the procurement record entirely
Open questions
- Who would hold a citizen-owned recording, and on whose infrastructure?
- Is a record you own but cannot take off the platform really yours?
- What would it take for the observed person to appear in a procurement register at all?
References
Both describe the gap this proposal is aimed at. Neither shows that a consumer camera and a government platform are linked.
Not independently verified
Topics: Proposed solutions · Technology · Surveillance & memory access · Law enforcement & government