Does our data stay ours when an agency builds AI for us?

We build on the systems that are already there. That is why the answer to the data question can be short: your data stays where it is today. In your mailbox, in your document folder, in the accounting package, in the database under your own application.

What we add is a program that reads and writes there. It fetches what that one step needs, does something with it, and puts the result back in the system you are looking at anyway. A second copy of your data only appears when the route really calls for it, and then we agree up front what goes in it and how long it stays.

Where possible the system runs in your own environment and your own accounts. The cloud account is in your name, the storage is your storage, and the mailbox something leaves from is yours. We get access, we take nothing with us.

That has a practical side too. If it runs in your accounts, your administrators see it in their own logs, they can switch it off without calling us, and nothing has to change hands if the collaboration ever ends.

An AI system is mostly ordinary code. In one or two places along the route there is a model call. What goes out is the piece that step needs: one job sheet, not the folder. One mail, not the mailbox.

We do not train public models on your data. Which provider, which region and which retention period apply per project is something we look up, and that outcome is named in the data processing agreement.

We sign an NDA and a data processing agreement as standard, even for a first project of two weeks. It says who is responsible for what, and the parties we bring in are named in it.

We write the code and keep it running. That is why you pay no licences and no amount per user, not even as your team grows, and we fix bugs without a bill. You can request a full export of your data at any moment, and that agreement is in the same document.