Social media OSINT and police officers

How this plays out for police officers

OSINT — open-source intelligence, the practice of building a target file from public information — works against cops in stages. Someone gets your name from a body-cam clip, a news article, or a forum post. They search the name, find a LinkedIn from before you joined the job, an old college Facebook tag, a 5K race result, a wedding registry. None of it looks like much. Together, it's a profile.

The bridge from the online footprint to your front door is usually a broker page. The public-info side tells the searcher who you are. The broker page tells them where you sleep.

What's at stake

Old college tags and family photos are the parts most cops underestimate. A photo of your back porch from 2014. A sibling's reunion post that includes your real name. A check-in at the gym you still go to. Any of it can connect to who you are now.

The family piece compounds it. Your spouse's LinkedIn. Your kid's club soccer roster. Your parents' Facebook. Each one adds a thread the searcher can pull.

What to do right now

Lock down what you control. Run the social media leak playbook when your name surfaces on LinkedIn, Facebook, or Instagram. Privacy settings. Location tagging off. Geotagged photos removed. Tags by family members removed where you can. Talk to your spouse and adult kids about what they post that names you.

Run a free scan to see which broker pages connect your name to your address. For the broader pattern, see social media OSINT.

How we handle it

We don't operate your social accounts. That part is on you. What we handle is the broker side — the layer that turns an OSINT profile into a home address. Same cadence on every site that has you, every two weeks.

For NJ officers, Daniel's Law — the state statute that lets covered officers sue data brokers for failing to remove their home address — gives us a stronger lever on the broker side.