Privacy, Accountability, and Empathy

All kinds of tactical phrases become popular in the world of business and technology. "Designing with empathy" is one that has always stuck with me. Maybe it's because I get very frustrated with poorly designed apps in a world where you need to have more and more of them to conduct regular business with today's companies. Or maybe it was years and years of being in the consulting world and seeing that the biggest reason projects failed wasn't the technology execution, but instead a lack of a adoption for a product where the designers chose not to take the users on the journey with them.

But in today's world, actual empathy has become increasingly personal. And probably no aspect of empathy is more important in this AI, Flock Camera world than privacy. And who can blame people. Spam calls and emails, identity theft, cyber bullying are all common and not trending in great directions.

One example where privacy has become increasingly personal is the use of AI glasses, where there has clearly been a social backlash. At Headjacks as we near our beta release and think about our next version features, we have had our eyes (pardon the pun) on this market and where it is going. It's not hard to imagine how effective AI Glasses could be in a mobile work platform that can literally see what you see and help you do your job better.

But a funny thing has happened with AI Glasses. They make people uncomfortable. The idea that you could be in a conversation with someone having no idea that they are recording your conversation. Or maybe it is someone you asked to come repair something in your house and anywhere they go they could be taking photos without you even knowing. It just feels icky. You know AI Glasses are in the middle of a social backlash when AI Glasses companies are touting their lack of a built in camera as a feature. "Have you tried our privacy-enhanced AI glasses?"

But in the meantime, we are trying to solve an accountability gap in the industry. Even if you trust that your team is doing great work for you clients, it doesn't mean that your customers will believe it. So features that ensure you are at the locaton where you are performing the service, or photos that help verify your work can also feel intrusive if you can't trust that those features are being used responsibly and only with consent.

So as a company looking to become "The Evolution of Mobile Workforce Management" how do we stay out of the "icky" column?

Feature Principles to Protect User Privacy

Not only does location and camera use require permission, you can always choose "Only While Using the App". When the app is not open, we don't need your current location or your camera.
No Tracking Off the Clock — location data only flows while you're actively clocked into a job, not before, not after, not in the background. If you're not working, we're not watching.
Photos Serve One Purpose — there's no camera roll access, no open gallery. A photo exists to answer one specific task question on one specific job, and that's the only thing it's ever reviewed against.
Tenant Walls Are Real Walls — every client's data lives in its own database, not a shared pool with a permission flag. There's no shared table for a bug to leak out of.
The AI Never Sees Raw IDs — before any text reaches our AI assistant, internal identifiers and storage links get stripped and swapped for plain language. We don't even let it echo a raw database handle back at someone.
Some AI Never Leaves Your Phone — our assistant can run fully on-device, offline. In that mode, your data never makes a round trip to the cloud at all.
Built Free, By Design — the app itself is free to use. There's no ad-tech or data-resale model funding it, so there's no business reason to collect more than the job requires.

The Point of All of This

None of these are dramatic features. That's sort of the point. Privacy done well doesn't announce itself — it just quietly removes the reasons for someone to feel watched. The accountability gap we're trying to close only works if the people closing it, your workforce, trust the tool doing it.

We don't think privacy and accountability have to be a trade-off. You can know the work got done without knowing everything about the person who did it. That's the version of "The Evolution of Mobile Workforce Management" we're building.