Apps & internet

Tigerfish Locked Down Cloud Storage After Police Transcripts and Bodycam Footage Were Left Open Online

589 words, 3 min

tigerfish locked down cloud storage after police transcripts pixabay 838384

Image: blickpixel on Pixabay

Tech news by email, once a week

Unsubscribe any time. Privacy policy

San Francisco transcription company Tigerfish secured a cloud storage bucket on or around November 20, 2026, after it was found to hold police interview transcripts, bodycam footage and other customer files with no password protecting them. The company serves police departments, prosecutors and technology firms.

What was in the open bucket

The files sat in an Amazon S3 storage bucket that anyone could open without credentials. The address was easy to guess, so a person did not need inside knowledge to reach the contents. According to reports on the incident, the bucket held transcripts of police interviews, body-camera video, raw audio and video that customers had sent in for transcription, and client invoices.

Tigerfish sells transcription of recorded speech. Customers upload recordings and receive text back, so the storage behind that service can hold some of the most sensitive material those customers produce. Law enforcement interviews and bodycam clips can involve victims, witnesses, suspects and minors.

Advertisement

A warning that went unanswered

Security researcher Anurag Sen found the exposed bucket in October and emailed Tigerfish to report it. He received no reply. Tigerfish later said the researcher's message had been caught by its spam filter. The company blocked all public access to the bucket after a reporter contacted it.

Based on those accounts, the files were reachable for at least several weeks between the October discovery and the November lockdown. The exact date the bucket first became public has not been stated.

Customers still lack answers

Several basic facts are unconfirmed. Nothing published so far establishes whether anyone other than the researcher opened or downloaded the files. S3 can log access requests, but only if logging was switched on, and Tigerfish has not said whether it was.

It also remains unclear whether Tigerfish has told the police departments, prosecutors and companies whose recordings were in the bucket. The company has not said how many customers or how many files were affected, or how far back the stored material goes. No regulator or court filing has been reported.

A leak of this kind can create legal problems for the agencies involved. Recordings tied to open investigations or prosecutions may be subject to confidentiality rules, and an agency that learns its footage was exposed may have its own notification duties. Those obligations vary by state and by the type of record, and no agency has commented publicly on what it plans to do.

What customers of transcription services can check

Any organization that has sent recordings to Tigerfish can ask the company in writing whether its files were in the exposed bucket, when they were stored, and whether access logs exist for the period. Agencies and businesses that use other transcription vendors can ask the same questions about storage settings and about where security reports are sent. A vendor's security contact should be a monitored address, not a general inbox where one email can disappear into a spam folder.

For the technical side, the failure is a familiar one. Cloud storage providers offer settings that block public access across a whole account, and security teams commonly turn them on by default. Whether Tigerfish had such a setting enabled before the bucket was found is not known.

Tigerfish has not published a statement describing the incident, a timeline or any remediation steps beyond closing public access. No competing transcription provider has commented either.

Tigerfish said the researcher's October warning reached its spam filter. The company has not yet said whether customers have been notified.

Featured image: blickpixel on Pixabay

Advertisement

Get the week's tech news by email

One email a week with Trendblog's stories on AI, hardware, apps and crypto.

We'll email you to confirm your address. Unsubscribe any time. Privacy policy