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.
| Field | Value |
|---|---|
| Owner | Founder, FIDEVO/AI LABS LIMITED (trading as Temei) |
| Status | Working draft, published for open use |
| Version | 0.1 draft, 22 November 2026 |
| Review | yearly, after any incident, or when the law or Microsoft's data handling changes |
| Applies to | every AI agent Temei builds or runs in Microsoft Copilot Studio, and the data those agents read, write or keep |
| Sits under | CHR-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
- Least data. An agent reads only the lists, fields and sources written in its Registration Card, and nothing else.
- 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.
- 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.
- No surprises for people. Anyone whose data an agent handles can find out, from a notice, that an agent is involved.
- 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
| Class | Examples | L1 Sandbox | L2 | L3 | L4–L5 |
|---|---|---|---|---|---|
| Test | synthetic items on test sites | yes | yes | yes | yes |
| Internal | delivery tracking, agent register, knowledge drafts | no (test copies only) | read | read; write with approval | read; write via constrained tools |
| Personal | names, work emails, client contacts | no | read, if the card lists it and a lawful basis is recorded | as L2, writes approved one by one | as L2, plus a DPIA (data protection impact assessment) done |
| Special category / criminal / children | health, ethnicity, convictions, anyone under 18 | never | never | never | only with a DPIA, client DPO sign-off and a named legal basis |
| Secrets | passwords, API keys, card or bank numbers | never | never | never | never |
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
| # | Rule | How it is enforced |
|---|---|---|
| D1 | Each 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 |
| D2 | Agents 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 |
| D3 | Agents 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" |
| D4 | No 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 |
| D5 | Agents never store secrets in instructions, topics, variables or list items. Connections hold credentials; agents never see them. | Build review; connection references |
| D6 | Transcripts and logs are kept only as long as set below, then deleted. | Copilot Studio and Dataverse retention (section 5) |
| D7 | Agent 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 |
| D8 | A 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
| Data | Where it lives | Kept for |
|---|---|---|
| Conversation and session data | Copilot Studio storage | up to 28 days, deleted automatically by Microsoft |
| Conversation transcripts (agents on the standard harness) | Dataverse ConversationTranscript table | 30 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 harness | not written to the Dataverse transcript table | Copilot Studio storage only (28 days) |
| Items the agent writes (escalations, notes, drafts) | the client's SharePoint lists | the client's own retention policy for that site |
| Audit of agent and admin activity | Microsoft Purview audit | the tenant's audit retention (licence dependent) |
| Gates, Registration Cards, Logos entries | Temei 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
| Role | Responsibility |
|---|---|
| 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 owner | keeps the card and register accurate; first contact for questions about the agent's data |
| Platform admin | keeps 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.
10. Related documents
- POL-01 Agent Autonomy Policy
- Why DLP blocks your Copilot Studio agents (environments and data policies)
- The governance pyramid for Copilot Studio agents (where this document sits)
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.