Short answer: Microsoft Copilot privacy depends heavily on how you sign in and where you use it. A personal Microsoft account uses the consumer Copilot privacy model, which can save conversation activity and may use eligible conversations for model training unless the user is excluded or opts out. A work or school account protected by Microsoft’s enterprise data protection uses organisational terms: prompts, responses and Microsoft Graph data are not used to train foundation models, but interactions may be logged, retained and available to authorised administrators for compliance.
Table of contents
- Why the account type matters
- Personal Copilot data handling
- Work and school account protections
- Web-search queries and uploaded files
- History, deletion and training controls
- What employers may audit
- Safe-use checklist
- Example and FAQs
Why Microsoft Copilot privacy changes with the account
“Copilot” is a family name used across consumer apps, Microsoft 365 services, Edge, Windows and organisational products. Two people can see a similar chat box while receiving different privacy commitments. The decisive questions are: which account is signed in, which product surface is open, whether enterprise data protection is indicated, and which organisation policies apply.
Microsoft’s consumer support page specifically separates people signed in with a personal Microsoft account from people signed in with a work, school or organisational Microsoft Entra account. Microsoft also distinguishes the standalone Copilot app from Copilot inside Microsoft 365 consumer applications. Do not assume that a setting described for one surface automatically governs every other Copilot experience.
This guide focuses on reader decisions, not on comparing answer quality. If you are choosing among tools for work, see CheckMatter’s ChatGPT vs Gemini vs Copilot work guide. Privacy still needs a separate product-and-account check.
Microsoft Copilot privacy for a personal account
When a person signs in to the consumer Copilot app with a personal Microsoft account, conversation activity is normally saved and can be revisited. Microsoft’s privacy FAQ says the default conversation-activity retention period is 18 months. A user can delete individual conversations or the entire history, subject to the current controls and privacy statement.
Microsoft says consumer conversations can be used for limited operational purposes such as troubleshooting, diagnosing bugs, preventing abuse and monitoring performance. It also offers controls for personalisation and for whether eligible conversation activity may be used to train generative AI models. Personalisation and model-training controls are separate ideas: turning off training does not necessarily turn off personalisation, and vice versa.
Consumer model-training exclusions are important. Microsoft’s FAQ says training does not apply to users signed in with an organisational Entra ID account, Copilot conversations inside Microsoft 365 consumer apps, unsigned users, users under 18, people who opt out, and certain locations identified in the policy. Availability and the exact control names can change, so check the current privacy page in the specific app.
How to review personal Copilot privacy controls
- Confirm the account. Open the profile menu and verify whether the address is personal or organisational. Do not rely only on the app icon.
- Open the privacy or account settings. Look for conversation history, personalisation and model-training controls.
- Decide whether history is useful. Keeping history improves continuity but leaves more content associated with the account.
- Review training preference. If the setting is available, turn off use of conversation activity for generative-AI training when that matches your preference.
- Delete conversations you no longer need. Deletion may be subject to safety, legal or operational retention described in Microsoft’s policies.
- Minimise future prompts. Settings reduce some uses; they do not make it wise to paste secrets, identity documents, health records or confidential client material.
A deletion control is not a promise that every copy disappears instantly from every backup or legally required system. Read the current official statement. Treat history deletion as an account-hygiene tool, not as permission to upload data that should never have been shared.
Work or school accounts: enterprise data protection
When an eligible organisation user signs in with a Microsoft Entra account, Microsoft describes enterprise data protection, or EDP, for Copilot and Copilot Chat. Under the Data Protection Addendum and Product Terms, Microsoft acts as a data processor for customer data. The product may display a shield or other indication that the protected work experience is active.
Microsoft states that prompts, responses and data accessed through Microsoft Graph under EDP are not used to train foundation models. The service uses encryption in transit and at rest, tenant isolation, and Microsoft 365 access controls. Copilot respects the permissions a user already has; it does not grant a person access to a file merely because they ask for it in a prompt.
That protection does not mean “nobody can see anything.” Organisational interactions can be logged, retained, audited, searched in eDiscovery and governed through Microsoft Purview, depending on licences and policy. An authorised administrator or compliance team may therefore have legitimate visibility that a consumer user would not expect. Employees should follow their organisation’s acceptable-use and data-classification rules.
Personal versus work Copilot: practical comparison
| Question | Personal account | Work or school account with EDP |
|---|---|---|
| Foundation-model training | Eligible conversation activity may be used unless excluded or opted out | Prompts, responses and Microsoft Graph data are not used to train foundation models |
| Conversation history | Normally saved; consumer FAQ states 18 months by default | Logged and retained according to Microsoft 365 and organisation policies |
| Administrative access | No employer administrator for the personal account | Authorised organisation teams may audit, retain or discover interactions |
| Data permissions | Based on the consumer account and connected features | Existing Microsoft 365 identity, permissions, sensitivity labels and policies apply |
| Best use | Low-sensitivity personal tasks after checking controls | Approved organisational tasks within employer policy |
This table is a decision aid, not a substitute for the contract or privacy statement. Organisations can configure controls differently, and consumer product versions can change.
What happens to generated web-search queries
Copilot can generate a short web-search query to ground an answer in current public information. Microsoft says Bing search is handled separately from the Microsoft 365 service boundary. For enterprise use, generated queries are designed to omit user and tenant identifiers, entire uploaded files, and usually the full original prompt. Microsoft also says those generated search queries are not shared with advertisers and do not train its foundation models.
However, a generated query can still contain the topic or keywords needed to search the web. Do not put a client name, unpublished project codename, health condition, or other unnecessary secret into a prompt and assume that query generation will always remove it. Use generic descriptions when web grounding is not essential, and follow organisation policy.
Uploaded files and connected organisational data
In the enterprise experience, entire files uploaded to Copilot Chat can be stored in the user’s OneDrive for Business as part of the protected Microsoft 365 environment. Retention, sharing permissions, sensitivity labels and eDiscovery can apply. Deleting the visible chat may not be the only lifecycle action needed for the file.
Microsoft Copilot with organisational grounding can use data the user is authorised to access from Microsoft 365. That is powerful but introduces an oversharing risk: if a SharePoint site or file is broadly accessible, Copilot may help an authorised user discover it more easily. The privacy control is therefore not just inside Copilot. SharePoint permissions, group memberships, sharing links, sensitivity labels and retention policies must also be governed.
For personal Copilot, treat every upload as a disclosure to the service under the consumer terms. Remove account numbers, signatures, resumes containing unnecessary identifiers, confidential contracts and unreleased business information unless the official policy and your authority clearly permit processing.
Can Microsoft or a human reviewer see conversations?
The consumer privacy FAQ says some conversations can be reviewed through automated and human processes for product improvement and digital safety, and suspected policy violations may receive limited human review. The policy states there is no general opt-out from review needed to investigate suspected violations.
For organisations, authorised personnel may access records through compliance, audit or investigation tools. This is not the same as conversations being public or shared with other random users. Microsoft says consumer conversations are not made visible to other users. Still, workplace users should assume that retention and lawful administrative review are possible.
What settings do not guarantee
- Turning off model training does not make a prompt invisible to safety systems.
- Deleting chat history does not cancel copies you exported, pasted elsewhere or saved in a document.
- Enterprise data protection does not fix overly broad SharePoint permissions.
- A personal account is not an approved place for employer confidential data.
- A work account does not make every prompt appropriate; company policy still applies.
- Private or temporary modes in another AI product do not define Microsoft Copilot’s behaviour.
Example: the same prompt in two accounts
Anita wants help summarising meeting notes. In personal Copilot, she would be placing workplace information into a consumer account governed by consumer settings. Even if she disabled model training, the upload could violate her employer’s rules. In the approved work account with EDP, the content stays within the organisation’s Microsoft 365 protections, is not used to train foundation models, and can be subject to retention and audit.
The correct choice is therefore not “which account promises absolute secrecy.” It is the authorised work account, with only the minimum necessary content and the correct document permissions. If the employer has not approved Copilot for the data, Anita should not upload the notes at all.
Safe-use checklist for individuals
- Verify whether the signed-in account is personal or organisational.
- Read the privacy page for the exact Copilot surface.
- Review history, personalisation and training preferences.
- Remove unnecessary personal and financial data from prompts.
- Delete old consumer conversations you no longer need.
- Do not paste employer or client secrets into a personal account.
Safe-use checklist for work
- Use only the organisation-approved account and Copilot surface.
- Look for the enterprise-data-protection indicator.
- Follow sensitivity labels and acceptable-use policy.
- Check document permissions before asking Copilot to summarise shared content.
- Assume prompts can be retained and audited.
- Avoid unnecessary web grounding for confidential topics.
- Report overshared content to the data owner or administrator.
Freelancers using AI across client projects should also separate accounts and permissions. CheckMatter’s AI features for Indian freelancers guide includes practical workflow boundaries.
Frequently asked questions
Does Microsoft use personal Copilot chats for AI training?
Eligible consumer conversation activity may be used unless the user is excluded or opts out. Check the current training preference and Microsoft’s official privacy FAQ for your account and location.
Are work Copilot prompts used to train foundation models?
Microsoft says prompts, responses and Microsoft Graph data under enterprise data protection are not used to train foundation models.
Can my employer see my Copilot chats?
Authorised organisation teams may be able to audit, retain or discover interactions through Microsoft 365 compliance tools, subject to licences and policy. Treat work chats as organisational records.
How long are personal conversations kept?
Microsoft’s consumer privacy FAQ states that conversation activity is stored for 18 months by default. Users can delete individual conversations or history, while other policy-based retention may apply.
Does deleting a chat delete an uploaded work file?
Not necessarily. In enterprise Copilot Chat, uploaded files can be stored in OneDrive for Business. Check the file location, retention policy and organisation guidance.
Is a work account always safer?
It offers enterprise contractual and technical protections, but safety also depends on correct permissions, approved use, minimal data and organisational governance.
Conclusion
Microsoft Copilot privacy is not one universal setting. Personal accounts use consumer history, personalisation and training controls, while work or school accounts with enterprise data protection exclude prompts and organisational data from foundation-model training but may retain interactions for authorised compliance. Before sharing anything, identify the account, verify the protection indicator, minimise the prompt, and follow the policy that governs the data.
Author: CheckMatter Editorial Desk
Publication date: Proposed; not published
Updated date: 30 September 2026
Last verified: 30 September 2026
Correction history: No corrections; original draft.
Primary authority: Microsoft Support and Microsoft Learn
Official consumer source: Microsoft Copilot for individuals: data and privacy
Official enterprise source: Microsoft Copilot Chat privacy and protections
Official enterprise-data source: Enterprise data protection in Microsoft Copilot
Verification metadata:
_cm_verified_source_url: https://support.microsoft.com/en-us/privacy/microsoft-copilot/overview
_cm_source_authority: Microsoft Support and Microsoft Learn
_cm_effective_date: Product documentation verified 2026-09-30
Feature-availability disclaimer: Microsoft changes product names, settings and availability. Account type, location, licence and administrator policy can alter the controls shown. Verify the current official documentation before handling sensitive data.
Schema: Article; FAQPage markup is eligible if the visible FAQs are retained. Canonical recommendation: https://checkmatter.in/microsoft-copilot-privacy-personal-work-account/
Leave a Reply