← Blog
AI03.03.20262 min

Data rules before adopting AI

Data rules get written before the first incident, not after. You only need a few, but they have to exist before the tools reach the company.

AI tools almost always arrive from the bottom up: someone tries one, it works, and within a few weeks many people are using it. Nobody has decided anything, but in the meantime someone pastes a contract, a customer list or a piece of confidential code into a prompt. The first incident is never spectacular: it’s a question that arrives afterwards, “where did that document end up?”, which nobody can answer.

Why before

Writing rules after an incident turns them into a reaction: too strict, or too generic, and not credible to the people who have to follow them. Writing them beforehand, calmly, lets you decide what really matters and explain it to the team as a choice, not a ban.

Four decisions to put in writing

  1. Which data never leaves the company: customers, credentials, confidential code, personal and health data.
  2. Which tools are approved, and with what settings for data retention and training.
  3. What stays a human decision: contracts, hiring, assessments of people, anything with serious consequences.
  4. How a result is verified: who checks, and by what criterion.

The fourth is the most forgotten. An AI produces plausible answers even when they’re wrong, so you need a way of noticing that doesn’t depend on the goodwill of whoever is reading.

A rule nobody remembers at the moment they paste a text isn’t a rule.

Where to start

One page is enough. Divide data into three levels (open, internal, confidential) and write what can be done with each. Pick one approved tool to start with, instead of letting everyone use their own. Give the team thirty minutes to explain the why, not just the what. And set a date, three months out, to review everything in light of how it went.

What about GDPR?

If you process personal data, tool vendors are normally processors: you need an agreement, a check on where the data is stored and an eye on transfers outside the EU. Involve whoever handles privacy, or a lawyer, for this part: this article isn’t legal advice, it only says the question should be tackled beforehand, not afterwards.

Gaetano Del Prete Fractional CTO and developer for over twenty-five years. I help startups, SMEs and agencies make fewer technical decisions, but better ones. Book a call →