PMOpackFree check
Article

Where does my project data go when I use an AI reporting tool, and who can see it?

It goes to three places: the tool's own database, the AI provider the tool sends text to, and the hosting and support services the tool runs on. Who can see it depends on the plan you are on, the provider list, and how long each copy is kept. Ask for all three in writing before you upload anything.

This is the first question a sensible PMO director asks, and the one most vendors answer worst. Security reviews can take longer than the project they are reviewing. Most of that time went on getting straight answers to five plain questions. Here they are, so you can ask them in one email. This article is general information from a practitioner, not legal advice. Your data protection officer or legal team decides what your organisation may do.

The three places your data goes

When you upload a plan, a RAID log or a budget tracker to an AI reporting tool, the file does not sit in one place. It moves through at least three.

  1. The tool’s own database and file store. Your upload, the parsed data, the draft, the finished report, and the record of what was changed. This is the copy the vendor controls directly.
  2. The AI provider. Few tools run their own language model. Most send text to an outside provider and get a draft back. That text is seen by the provider’s systems, under the provider’s terms, not the tool’s.
  3. The services the tool runs on. Hosting, error logging, email, payments, uptime monitoring. Each one may hold a fragment: an email address, a stack trace with a project name in it, a backup of the database.

Under UK data protection law, your organisation is normally the controller for the programme data it uploads, and the tool is a processor acting on its instructions. The ICO puts it plainly: “Controllers make decisions about processing activities” and “Processors act on behalf of the relevant controller and under their authority.” The ICO also says a controller can “only use a processor that provides sufficient guarantees” and is “ultimately accountable for your own compliance and the compliance of your processors.” In plain words: the vendor’s answers are your problem to check, not theirs to assert.

The five questions to ask in writing

  1. Who are all your providers, and what does each one hold? You want the full list, not “industry-leading cloud infrastructure”. If the list is not on their website, ask why.
  2. Where is each copy stored? “UK” or “EU” for the main database is common. Ask separately about the AI provider and the logging service. The ICO’s guide calls sending personal information to an organisation outside the UK a “restricted transfer”, and says it must be covered by adequacy regulations, an appropriate safeguard such as the International Data Transfer Agreement or Addendum, or an exception. Ask which one applies.
  3. Does the AI provider train on what you send? Ask for the clause in the provider’s terms, with the date. Terms change. A screenshot from last year is not an answer.
  4. How long is each copy kept, and can we delete it? Upload, draft, published report, backups. Four answers. A tool built for audit will keep published reports a long time on purpose; that is a feature, but you should know it going in.
  5. Who can see it: on their side, and on ours? On theirs: do support staff have access, and is it logged? On yours: who can join a workspace, and what can each role do?

What “stored in the UK” does and does not tell you

It tells you where the main database lives. It does not tell you where the AI provider processes the text, where the error logs go, or where backups sit. None of those are necessarily a problem. Many providers offer UK or EU regions, and transfers can be lawful with the right safeguard. But you need to know, and so does your DPO. A vendor who can tell you the location of every copy without looking it up has done the work. One who cannot has not.

What to strip before you upload

Whatever the vendor says, the safest data is the data you did not send. Before uploading a file to any tool, mine included, go through it once:

  • Performance comments about named people. A milestone tracker rarely needs them.
  • Salary or day-rate columns in a resource plan. Replace with a role and a band.
  • Client names where a code will do, if the report is for an internal board.
  • Personal email addresses and mobile numbers in an owner column. A name is enough.

This is the ICO’s data minimisation principle in practice: personal data should be “adequate, relevant and limited to what is necessary” for the purpose. It is also just good hygiene. We cover the wider question in Can I put programme data into an AI tool and stay within UK GDPR?

A real example

A PMO lead on a financial services programme asked an AI reporting vendor the five questions above. The answers to questions one and two came back in a day. Question three took three weeks, because the vendor had to ask its own AI provider. Question four revealed that deleted reports stayed in backups for a year, which was fine, but nobody had said so. The programme went ahead with the tool. The DPO’s note said the deciding factor was not any single answer. It was that the vendor eventually wrote all five down and dated them.

Where PMOpack fits

Here are PMOpack’s own answers, as they stand on the privacy notice. The database is hosted in London, UK. The text needed for drafting is sent to Anthropic, whose Commercial Terms say that it may not train models on customer content. We do not use your programme data to train any model. Draft report files are removed after 7 days. Published packs and their audit record are kept permanently, so the record stays complete. Access to each workspace is limited to its members, and data is encrypted in transit and at rest by the hosting provider. The full provider list, with what each one is for, is in the privacy notice, and the Trust page describes what the record keeps. What PMOpack does not do: it does not claim zero data retention at the AI provider, and it does not prove a figure is true against your finance system. It checks the pack against itself, and a person decides.

Questions people ask

Does an AI reporting tool keep a copy of my file?
Usually yes, at least while it works on it. Ask how long the upload, the draft and the finished report are each kept, and whether you can delete them. The answers are often different for each.
Does the AI provider see my data as well as the tool?
If the tool calls an outside AI provider, the text it sends is seen by that provider's systems. Ask which provider, under which terms, and whether those terms allow training on your content.
What does "data stored in the UK" actually mean?
Usually that the main database is in a UK region. It does not by itself say where the AI provider, error logs, email service or backups are. Ask for the full provider list, not the headline.
Who inside my own organisation can see what I upload?
Whoever the tool lets into your workspace. Check how members are added, whether there are roles, and whether a published report can be read by people who were not in the workspace when it was made.
Where does my data go with PMOpack?
The database is hosted in London, UK. Text needed for drafting is sent to Anthropic, whose Commercial Terms say it may not train on customer content. Draft files are removed after 7 days. Published packs and their record are kept permanently. The full provider list is on the privacy notice.

Sources

Last checked 29 October 2026. This article is general information, not legal advice. Your data protection officer or solicitor decides what applies to your organisation.

  1. Information Commissioner’s Office, “What are ‘controllers’ and ‘processors’?”: “Controllers make decisions about processing activities”; “Processors act on behalf of the relevant controller and under their authority.”ico.org.uk
  2. Information Commissioner’s Office, “What does it mean if you are a controller?”: “you can only use a processor that provides sufficient guarantees”; “You are ultimately accountable for your own compliance and the compliance of your processors.”ico.org.uk
  3. Information Commissioner’s Office, “A brief guide to international transfers”: a restricted transfer must be covered by UK adequacy regulations, an appropriate safeguard such as the IDTA or the Addendum, or an exception.ico.org.uk
  4. Information Commissioner’s Office, “A guide to the data protection principles”: data minimisation means personal data is “adequate, relevant and limited to what is necessary in relation to the purposes for which they are processed”.ico.org.uk
  5. Anthropic, Commercial Terms of Service (effective 17 June 2025): “Anthropic may not train models on Customer Content from Services.”anthropic.com/legal/commercial-terms
  6. PMOpack data handling statements are drawn from PMOpack’s own privacy notice.

See the checks on your own pack.

We are working with a small group of delivery professionals to prove the reporting journey on real work. One active workspace per person.

Or email [email protected]

For people who run project reporting for a living. Not for students, personal projects or coursework. We read every request and reply to those who fit.

Want to know where your data goes and who can see it? Read the Trust page.