Working draft

POL-02 Agent Data and Privacy Policy

Which data an agent may touch at each trust level, where it may go, how long anything is kept, and who answers for it under UK GDPR.

Working draft, published openly. This is the version Temei works to. You may read it in full, adapt it and use it in your own organisation. If you would like help fitting it to your tenant, book a call.

FieldValue
OwnerFounder, FIDEVO/AI LABS LIMITED (trading as Temei)
StatusWorking draft, published for open use
Version0.1 draft, 22 November 2026
Reviewyearly, after any incident, or when the law or Microsoft's data handling changes
Applies toevery AI agent Temei builds or runs in Microsoft Copilot Studio, and the data those agents read, write or keep
Sits underCHR-00 Temei AI Charter · works with POL-01 Agent Autonomy Policy

This policy is not legal advice. Where a client has its own data protection policy or a Data Protection Officer, their rules apply in their tenant and this policy fills gaps only.

1. Purpose

Agents read and write business data, sometimes personal data. This policy sets which data an agent may touch, where that data may go, how long anything is kept, and who answers for it, in line with UK GDPR and the Data Protection Act 2018.

2. Principles

  1. Least data. An agent reads only the lists, fields and sources written in its Registration Card, and nothing else.
  2. Data stays in the tenant. Agent data stays in the Microsoft 365 and Power Platform tenant it came from. It is not copied to other services, other tenants or personal storage.
  3. Client data is the client's. In a client tenant, the client is the controller. Temei acts as processor under a written agreement and only on documented instructions.
  4. No surprises for people. Anyone whose data an agent handles can find out, from a notice, that an agent is involved.
  5. Written outputs carry no personal data they do not need. Drafts, summaries and articles drop names, emails and phone numbers unless the purpose needs them.

3. Data classes and what each level may touch

ClassExamplesL1 SandboxL2L3L4–L5
Testsynthetic items on test sitesyesyesyesyes
Internaldelivery tracking, agent register, knowledge draftsno (test copies only)readread; write with approvalread; write via constrained tools
Personalnames, work emails, client contactsnoread, if the card lists it and a lawful basis is recordedas L2, writes approved one by oneas L2, plus a DPIA (data protection impact assessment) done
Special category / criminal / childrenhealth, ethnicity, convictions, anyone under 18neverneverneveronly with a DPIA, client DPO sign-off and a named legal basis
Secretspasswords, API keys, card or bank numbersnevernevernevernever

An agent that might meet a data class above its permission (for example, free-text fields where users type anything) must say so in its card, and its instructions must tell it to ignore and not repeat that data.

4. Rules

#RuleHow it is enforced
D1Each Registration Card lists the exact sources and fields the agent reads and writes, the data classes involved and the lawful basis for personal data.Gate document; register fields Reads and Writes
D2Agents connect only through connectors allowed by the data policy for their environment. HTTP, custom connectors, public websites and external channels stay blocked unless a gate approves them.Environment group connector rules; classic data policy
D3Agents in production use authenticated channels only. Unauthenticated chat is not allowed for agents that touch Internal or Personal data.Data policy blocks "Chat without Microsoft Entra ID authentication"
D4No agent sends data outside the tenant by email, message or web request unless its gate names the recipient type and the reason.Gate; data policy; agent tool list
D5Agents never store secrets in instructions, topics, variables or list items. Connections hold credentials; agents never see them.Build review; connection references
D6Transcripts and logs are kept only as long as set below, then deleted.Copilot Studio and Dataverse retention (section 5)
D7Agent outputs that will be read outside the team (articles, client reports) are checked for personal data before release.Human review before KBStatus moves past Draft
D8A personal data breach involving an agent is handled as an incident under POL-01 section 6: the agent is stopped, the data owner is told at once, and the controller decides on reporting to the ICO within 72 hours.PRO-05 Incident, Suspension and Retirement Procedure

5. Retention

DataWhere it livesKept for
Conversation and session dataCopilot Studio storageup to 28 days, deleted automatically by Microsoft
Conversation transcripts (agents on the standard harness)Dataverse ConversationTranscript table30 days by default (Microsoft's bulk delete job). Temei keeps the default unless a client needs longer and records why
Transcripts for agents on the Microsoft Copilot harnessnot written to the Dataverse transcript tableCopilot Studio storage only (28 days)
Items the agent writes (escalations, notes, drafts)the client's SharePoint liststhe client's own retention policy for that site
Audit of agent and admin activityMicrosoft Purview auditthe tenant's audit retention (licence dependent)
Gates, Registration Cards, Logos entriesTemei project (Temei work) or client site (client work)life of the agent plus 6 years

6. People's rights

When someone asks to see, correct or delete their data, the controller handles it. For agents, Temei will:

  • say which agents could hold that person's data, using the register;
  • find it in the lists the agent writes to and in transcripts still kept;
  • delete or correct it where the controller decides, within one month of the request.

7. Temei and client data

  • Temei builds client agents in the client's tenant, not Temei's.
  • Temei staff use client accounts the client issues, with the least admin rights needed, removed when the work ends.
  • Client data is never used to train or tune models, never copied to Temei systems, and never used in Temei articles. Lessons become anonymised knowledge articles only after the client agrees.

8. Roles

RoleResponsibility
Controller (Temei for Temei work; client for client work)decides purpose and lawful basis; answers to people and the ICO
Processor (Temei, for client work)acts on documented instructions; keeps records; reports breaches without delay
Agent ownerkeeps the card and register accurate; first contact for questions about the agent's data
Platform adminkeeps data policies, retention settings and audit on

9. Exceptions

Written in Logos with rule, reason, owner, compensating control and an end date of no more than 90 days. No exceptions to the never cells in section 3 or to D5.

11. Approval

When you adopt this document, record who approved it, their role and the date, and keep that record with your other governance records.