.png){kind=small}
Training-Data Opt-Out: Per-Repo and Per-Org
Opt out of training — org-level, repo-level, verification.
What You Will Learn
- Opt out of training at org level.
- Opt out per repo.
- Verify opt-out is effective.
- Audit compliance.
- Document for privacy team.
Why This Matters
Free/Pro plans may use prompts for training unless opted out. Org-level enforcement ensures compliance.
Concept Explained
Training opt-out: org level (Business/Enterprise: not used by default) and per-repo (Pro: opt-out per repo). Verify effective via audit.
How It Works
Business/Enterprise: verify org-level opt-out is enabled. Free/Pro: opt-out per repo. Audit periodically.
Step-by-Step Tutorial
1. Check plan
Business/Enterprise: not used for training. Free/Pro: opt-out required.2. Org-level opt-out
Business/Enterprise: verify enabled in org settings.3. Repo-level opt-out
Free/Pro: opt-out per repo via settings.4. Verify
Audit via API or settings review.5. Document
For privacy team.Real-World Example
A company discovered their Pro plan was using prompts for training. Org-wide opt-out wasn't a Pro feature — had to opt out per repo. Wrote script to opt out all repos. Audited monthly.
Example Prompts / Commands / Code
"""# For Business/Enterprise:
GET /orgs/{org}/copilot/policy
# Verify: training_opt_out = true
# For Free/Pro (per-repo):
# Check each repo's settings:
for repo in org_repos:
settings = get_repo_settings(repo)
if not settings['copilot_training_opt_out']:
print(f'{repo} needs opt-out')
set_repo_opt_out(repo, true)
# Audit script (monthly):
for repo in org_repos:
if not is_opted_out(repo):
alert(f'{repo} not opted out')
""""""Plan Training opt-out How
-----------------------------------------------------
Free Per-repo Repo settings
Pro Per-repo Repo settings
Business Org-level (default) Org settings
Enterprise Org-level (default) Org settings
Business/Enterprise: not used for training (contractual).
Free/Pro: must opt out per repo.
"""Common Mistakes
- Assuming opt-out when not verified.
- Not auditing — drift undetected.
- Opting out per repo when org-level available.
- Not documenting for privacy team.
Best Practices
- Business/Enterprise: verify org-level opt-out.
- Free/Pro: opt-out per repo.
- Audit monthly.
- Document for privacy team.
- Use Business seats for compliance-sensitive work.
Troubleshooting
| Problem | How to Fix |
|---|---|
| Can't opt out | Upgrade plan. Or opt-out per repo if Pro. |
| Opt-out reverts | Audit script. Re-apply. Report to GitHub if persistent. |
Practical Exercise
Your Turn
Verify your org's training opt-out status. Audit all repos. Document for privacy.
Professional Challenge
Build a monthly audit: verify all repos opted out. Alert on drift.
Key Takeaways
- Training opt-out: org-level (Business/Enterprise) or per-repo (Free/Pro).
- Business/Enterprise: not used for training.
- Free/Pro: opt-out per repo.
- Audit monthly.
- Document for privacy team.
Frequently Asked Questions
Does opt-out affect quality?
Can I verify opt-out is effective?
Further Reading
Official References
SEO Metadata
SEO title: Training-Data Opt-Out: Per-Repo and Per-Org
Meta description: Opt out of training — org-level, repo-level, verification.
Primary keyword: training-data opt-out
Secondary keywords: training-data opt-out: per-repo and per-org
Search intent: Informational
URL slug: /training-data-opt-out-per-repo-per-org
Categories: AI Tools, GitHub Copilot
Tags: GitHub Copilot, Professional, Privacy, Training Data, Opt-Out, Governance, IMCSEIAN, Tutorial, IMCSEIAN
Featured image concept: IMCSEIAN lesson card for Training-Data Opt-Out: Per-Repo and Per-Org
Comments
Comments
Post a Comment