Flock Safety CEO address posts: what is confirmed and whether it affects you

On or around 22 August 2026, Flock Safety CEO Garrett Langley appeared on Fox News’ Saturday in America and said: “When people talk about just one of these, privacy or safety, they’re prioritizing the wrong thing, and what we have to prioritize as a country is compromise.” That appearance and that line are confirmed from the broadcast itself.

On 27–28 August 2026, posts on X circulated a purported home address and Street View images said to be his. Newsweek, IBTimes UK, and later aggregators wrote about those posts. They did not verify the address and did not publish it. Newsweek contacted Flock; no reply was published. Flock’s own site has no statement. Langley and the company have neither confirmed nor denied the posts. No regulator, platform, or primary source has said the address is his or that a doxxing of a real home took place as described.

This is not a leak of your information

Coverage of a CEO being “targeted” and an address “shared online” can sound like a company breach that might include you — especially when the company builds street cameras. That is the frame most write-ups leave sitting there. What they do not say clearly enough is what has actually been shown: some people on X posted a claimed address. Journalists confirmed that the posts exist. They did not confirm that Flock was hacked, that camera footage was allegedly stolen, that a customer or license-plate list is out, or even that the house in those posts belongs to Langley.

The honest read is narrower than the headlines. Anger at a surveillance firm got aimed at one executive. Unverified personal details were passed around. That is not the same thing as your name, your home, your car, or video of your street leaving Flock. Silence from the company is not proof the address is real, and it is not proof that anything about you is involved. If cameras in your area are a separate worry, this story does not answer it — and it does not mean your records may now be public.

What to actually expect

• You should not expect a breach notice from Flock about this. Nothing confirmed so far is a company data leak that would trigger one.
• The outlets that covered the posts have already said they will not print the address. That does not remove the original posts from X, and copies can keep circulating.
• Do not expect Langley or Flock to settle the address question on a deadline you can use. As of the 28 August 2026 Newsweek update, there was still no published comment on the posts.
• Near term, the likely “new” coverage is the same unverified posts being repeated, not independent proof from property records, the company, or a regulator.

What you can and cannot fix

The posts from 27–28 August 2026 cannot be pulled back. If they showed a real home, that information is already copied. If they did not, the claim still exists. Either way, that cannot be undone from here — and none of the reporting shows that your address, ID number, or camera data was in those posts. There is no confirmed dump of the public to recall, and no scan of “were you in this incident” can honestly answer that, because there is no confirmed dataset of victims to check you against.

• Do not search for, screenshot, or reshare the claimed address. Spreading unverified home details does not protect you. It is how a rumor becomes a pile of copies no one can clean up, and it can put a real household at risk even if the original post was wrong.
• Treat this as a story about one executive and unverified social posts, not as a cue to freeze credit, replace cards, or assume Flock lost a file with your name on it. Those steps do not match what is known. Save them for a confirmed leak of your records.
• If the real issue for you is the cameras, not these posts, that is a local question — who runs them, what they keep, and who can see it — not something you fix by reacting to an unverified address. This incident does not give you a takedown of leaked personal data, because your personal data has not been shown to be the data in question.