Security and data

How we handle your data

We use only the data a build needs, on plans that don’t train on it, and we log every run.

White stairs in clean lightA padlock with its key in it, wearing down into the system’s marks and building back

Which AI providers we use

We choose the provider for each build by the task and your own data rules.

Whether your data trains a model

It doesn’t. We use business and API plans where the provider commits not to train on customer content. The AI tool register explains how to check this for any tool.

What a system can see

Only what the work needs. Access is scoped to named folders, mailboxes or records, read-only wherever the work allows, and widened one step at a time with your agreement.

Before anything leaves your firm

Anything that leaves your firm or changes a record waits for a person. The system prepares it and flags what it isn’t sure of. Your originals are never changed.

What gets logged

Every run records what it read and what it did, in a form the process owner can read.

Privacy law

We are a Canadian company and work under PIPEDA and the provincial privacy acts that apply.

If something goes wrong

Report a concern to hello@miloworks.ai.

The policy we follow ourselves

We work to the same AI use policy we give to clients.

Questions we get asked

Can everything stay inside our own accounts?

Often, yes. Many builds run entirely on a client’s own accounts. The working session covers what is possible for yours.

The same questions, about other tools

Need this for procurement?

Send us your questionnaire and we’ll answer it in writing.