.png){kind=small}
Privacy Settings You Should Know Before Using Copilot at Work
Telemetry, prompt retention, training-data opt-out, plan-level guarantees.
What You Will Learn
- Locate all privacy settings.
- Understand plan-level data guarantees.
- Opt out of training data.
- Configure telemetry appropriately.
- Document your privacy posture.
Why This Matters
Using Copilot at work without configuring privacy is a compliance risk. Free/Pro plans may use your prompts for training; Business/Enterprise do not. Knowing the settings and the plan differences prevents accidental exposure.
Concept Explained
Copilot privacy has three layers: telemetry (usage data sent to GitHub), prompt retention (how long prompts are stored), and training-data use (whether your prompts improve the model). Each is configured separately.
How It Works
Telemetry is editor-level. Prompt retention and training-data use are account-level (github.com/settings/copilot). Business/Enterprise customers get explicit contractual guarantees that prompts are not used for training.
Step-by-Step Tutorial
1. Visit account settings
github.com/settings/copilot — see all privacy toggles.2. Check plan
Free/Pro: prompts may be used for training unless you opt out. Business/Enterprise: prompts are not used for training.3. Toggle training opt-out
If on Free/Pro: toggle 'Allow GitHub to use my snippets for model training' to OFF.4. Disable telemetry
In VS Code: Settings → 'GitHub Copilot Telemetry' → disable.5. Document
Screenshot your settings. Re-verify quarterly.Real-World Example
A fintech engineer used a personal Pro account for work code. Privacy default was 'training allowed'. Their snippets (including internal API patterns) had been contributing to model training for 3 months. The fix was 30 seconds; the audit took 2 weeks. Lesson: use Business seats for work, or at minimum opt out.
Example Prompts / Commands / Code
Plan Training opt-out Prompt retention
Free Available Short
Pro Available Short
Business Not used (default) Short, encrypted
Enterprise Not used (default) Short, encrypted + audit
# Account level (github.com/settings/copilot):
- Allow snippets for training: OFF (recommended for work)
- Prompt retention: as plan allows
# Editor level (VS Code):
- GitHub Copilot Telemetry: OFF (if you don't want usage data)
- Duplication filter: Block (for work code)
# Org level (Business/Enterprise):
- Training opt-out enforced org-wide
- Content filter policy
Common Mistakes
- Using personal Pro for work code — no contractual training opt-out.
- Forgetting editor telemetry is separate from account training opt-out.
- Not re-verifying settings after plan changes or extension updates.
- Assuming 'default' means 'safe for work'.
Best Practices
- Use Business/Enterprise seats for work — contractual training opt-out.
- On Free/Pro, explicitly opt out of training data.
- Disable telemetry if you don't want usage data sent.
- Screenshot settings quarterly to verify no changes.
- Document your privacy posture in your team's wiki.
Troubleshooting
| Problem | How to Fix |
|---|---|
| Setting reverts after update | Re-verify after any Copilot extension update. Open a GitHub support ticket if persistent. |
| Can't change setting | Org policy may enforce it. Contact your GitHub admin. |
Practical Exercise
Your Turn
Visit github.com/settings/copilot. Screenshot every privacy setting. For each, note: current value, recommended value, action needed. Apply any changes.
Key Takeaways
- Three privacy layers: telemetry, prompt retention, training opt-out.
- Free/Pro: opt out of training explicitly.
- Business/Enterprise: not used for training (contractual).
- Disable editor telemetry separately.
- Document and re-verify quarterly.
Frequently Asked Questions
Does opting out reduce quality?
What if my org has Business but I use personal Pro?
Further Reading
Official References
Related lessons: BE-03, BE-32, BE-33
SEO Metadata
SEO title: Privacy Settings You Should Know Before Using Copilot at Work
Meta description: Telemetry, prompt retention, training-data opt-out, plan-level guarantees.
Primary keyword: privacy settings you should know before using copilot at work
Secondary keywords: privacy settings you should know before using copilot at work
Search intent: Informational
URL slug: /copilot-privacy-settings-before-using-at-work
Categories: AI Tools, GitHub Copilot
Tags: GitHub Copilot, Beginner, Privacy, Data Protection, Enterprise, IMCSEIAN, Tutorial, IMCSEIAN
Featured image concept: IMCSEIAN lesson card for Privacy Settings You Should Know Before Using Copilot at Work
Comments
Comments
Post a Comment