← Back to MyCoordinated

Privacy in the AI Era: The Questions People Actually Ask

Published on July 2026

A glossy blue cloud uploading stacks of documents through a padlock, representing secure data upload

Most people chatting with an AI assume it’s just them and the model. It isn’t. That message usually passes through company servers, gets logged, sometimes reviewed, and depending on the tool, might end up shaping how the next version is trained. None of that requires anyone to be doing anything shady. It’s just how these tools work by default, and most people never think to ask until something makes them look closer.

For the everyday user, that’s more than fine. It rarely matters whether a prompt briefly touched a server somewhere along the way.

However, there are certain industries that aren’t allowed to disclose their documents to anyone else, including everyday AI chatbots. If you’re in law, compliance, or recruitment, handing a client file to a model is still handing it to a third party. The rules don’t make an exception just because the recipient this time is a model instead of a person.

This is where you need something more focused on privacy, something that still lets you enjoy AI tools without leaking client data to the AI. Here are a few ways we at MyCoordinated do it:

How we do it

  • Strip identifying details before anything reaches the model. Names, emails, phone numbers, and ID numbers are removed before your document or question goes to the AI, then restored once the answer comes back so it still reads normally to you.
  • Never send anything that ties a request back to you. AI providers offer fields to tag a request with an internal user ID, mainly for their own abuse monitoring. We never populate them. No user ID, no customer ID, no identifying headers of any kind.
  • Lock down what a link can reach. If the AI needs to open a webpage, it checks where that link actually resolves to first, blocks anything pointing at private or internal addresses, and re-checks at every redirect rather than just the first one.
  • Keep connected-app credentials off our servers. If you link email, cloud storage, or anything else, the access tokens stay on your side rather than sitting in our database.

Whether you’re just curious about privacy or bound by rules that don’t bend for AI, it comes down to the same thing: knowing exactly what happens to your data and how it is handled.