Module · Copilot Engineer
Privacy, Licensing & Attribution
What the assistant may read, what it may keep, and how to credit a machine-written line.
TOPIC 01
Licensing & Attribution
The rules about what a suggestion can become, and what the history has to say.
What you'll practice
- Check the Licensing Rules — guided · beginner
- Attribute What Was Machine-Written — practice · intermediate
A command you'll meet
cat ~/copilot/legal/licensing.mdThe licence of the code and the licence of the suggestion are different questions. Open the task below for the full walkthrough.
Hands-On Tasks in This Topic (2)
Check the Licensing Rules
The suggestion is a starting point, not an answer - it may reproduce something you cannot ship. Write the rule your team follows.
Attribute What Was Machine-Written
Some licences and some policies require that machine-written code be declared. Write the attribution rule for your repository.
TOPIC 02
Data Handling
What the assistant may read, and what must never leave the repository.
What you'll practice
- Know What Gets Indexed — practice · intermediate
- Keep Sensitive Data Out — challenge · advanced
A command you'll meet
cat ~/copilot/legal/data-handling.mdThe repository is the payload. Open the task below for the full walkthrough.
Hands-On Tasks in This Topic (2)
Know What Gets Indexed
An assistant that knows your repository also knows your secrets, if they are in it. Write the rule for what the repository may contain.
Keep Sensitive Data Out
Not every repository may be used with an assistant. Write the classification that decides which data the team may share and which stays local.