Is your data safe with Ai? Your company documents and your personal data.

01The 4 questions inside the 1 question

Most people argue about question 4 and never ask question 1 or question 2. That is backwards. When I go and test a live system, the near miss is almost always question 2.

02Where it lives, and who can open it

Start with your company documents. In the systems I build, the files live in the client's own storage account and their own database, paid for by them. The bill has their name on it. So if we walk away tomorrow, they keep every file and we keep no copy. That is the whole test for question 1, and it takes 1 minute: whose name is on the storage account.

If we walk away, you keep every file and we keep no copy.

Question 2 is where real firms lose data. A safe system has 2 locks, one behind the other. The front door lets in only the email addresses on an approved list, and if that check ever breaks it shuts instead of opening. Behind it, the database itself denies everyone by default. Think of a rule glued to the filing cabinet that says nobody opens this, unless your name is on the list, and the list starts empty.

Why 2 and not 1. Every web app hands a small public key to your browser. It sits in the page source, anyone can read it, and that is by design. It is the doorbell, not the door key. But if there is no rule on the cabinet, that doorbell opens every drawer. This is the most common way a small firm leaks a whole database without anybody hacking anything.

For your personal data, the same 2 questions get smaller and easier. Which app is holding this, and is the account in my own name. If you cannot answer that about your own ID photos or your money papers, that is today's job, not a technical project.

03What leaves the building, and when

Question 3 is the one owners feel in their stomach. Here is the honest answer for the systems I build. 1 document leaves, for about 4 seconds, because a person pressed a button. It is read and handed straight back, like a page passed through a bank window. The archive never leaves.

Reading a licence by hand takes close to 1 hour. This takes about 4 seconds, and a person confirms what came back on the screen before it counts. So the speed is real, and the control stays with a human being.

And here is a choice I made on purpose, against the loud advice of the moment. We did not tip the archive, hundreds of thousands of documents, into an Ai so people could chat with it. Exact questions need exact answers. A misread expiry date does not look like a mistake, it looks like a normal day, until it costs money.

A misread expiry date is a silent, expensive failure.

04Does the Ai company keep it, or learn from it

Question 4, and this is where the fear lives. The business Ai services say in their own terms that they do not train on what you send. Your inputs are held for a short time for abuse checks, then dropped. If you need more than that, a zero data retention agreement means they hold nothing at all. You do not have to take my word for it. Ask the vendor to send you that page.

Now the part nobody wants to say out loud. Pasting a client contract into a free chat app on your own phone is a different thing with different terms. And somebody on your team is probably doing it right now. That needs a policy, not a panic. 1 page: what may go in, what may never, and where the real work happens instead.

There is a 5th thing that is not about safety at all. It is about ownership. An Ai assistant can learn your business in 5 days, and then that memory sits as chat history inside a tool you rent by the month. Keep 1 file you own, in your own words, with how your firm actually works. The tool can change. The file is yours.

05I attacked a live client system from the outside

Talk is cheap, so I went and looked. I came at a client's live system the way a stranger would, with nothing but a browser. Every page sent me to the login. The login page source held nothing secret, only 2 values that are public by design, sitting across 8 script files. Then I took that public key and tried every table in the database while the system was live.

The 3 soft ones had been made later, by a different route, and they missed an old instruction. Nothing leaked, but 1 lock is not 2. The fix that matters was not patching 3 tables. It was making the database lock every new table the moment it is born, so nobody has to remember.

The same pass found something else. 1 confirmation could delete a whole company folder, which meant the newest clerk held the owner's power without knowing it. Now that action needs a second approval and its own permission level.

Security is a habit of going to look and writing down what you find, not a certificate on the wall.

A checklist needs someone sharp on a bad day. A system does not care what day it is. Today I run a 7 check pass before any client command center goes live, and it covers the 2 locks, secrets never reaching the browser, and each client's data kept in its own separate home, never mixed with another client's.

06Your personal data, and the 5 questions to ask

I wrote this down in my own book in 2022, lesson 104, and I still hold it. When I connect my wallet or sign in on some site, that is my decision. Nobody is forcing me. So I read before I click sign. That is my side of the deal.

The other side is bigger: "if a user can get hurt, it is the product owner's job to take the extra measures." If you build anything people log into, that line is your job description. And fear should not stop us from using new things that improve our lives. Read, then decide, then use it.

Ask them in that order. If they get uncomfortable at the 3rd one, you just learned the most useful thing you will learn that day.

07So, is your data safe with Ai

It can be, and it is not automatic. Safe looks like this: the files in your own account, 2 locks on the way in, 1 document leaving for 4 seconds on a human press, and a vendor whose own written terms say they do not learn from it. 4 questions, 4 separate answers, each one you can check yourself.

Unsafe does not look dramatic. It looks like nobody ever asked.

08Questions, answered