Confidentiality & Intellectual Property ยท Lesson 1 of 3
A former employer's code
Study notesAbout 3 minutes. A full lesson with quick checks is on its way.
In short
Code and confidential material from a former employer or client aren't yours to reuse. Don't bring them, use them or have an AI rewrite them.
In your work
An old laptop still holds a former employer's invoicing module that would solve a new client's problem in an afternoon. You leave it alone, build the solution from your own skills and public sources, and ask how to return or delete the old copy.
What the UK rules say
- Under the Copyright, Designs and Patents Act 1988, code an employee writes in the course of their job belongs to the employer, unless agreed otherwise.
- Freelancers and contractors usually own what they write unless their contract assigns it, so check the contract before reusing anything.
- The BCS Code of Conduct says not to use confidential information for personal gain or to benefit a third party without permission.
What to do
- Don't bring old code, documents or data into a new job or project.
- Reuse your skills, open-source code and public knowledge, not someone else's material.
- Ask your manager if you're unsure whether something is yours to use.
Watch out for
- Thinking an AI rewrite makes copied code yours.
- Keeping copies of client repositories after a project ends.
In your organisation
What does your contract say about who owns the code you write, and about confidential information?
Your employer's own policies come first.
Sources
- legislation.gov.uk, Copyright, Designs and Patents Act 1988, section 11 (opens in a new tab), checked 6 October 2026.
- BCS, BCS Code of Conduct (opens in a new tab), checked 6 October 2026.
UK law and guidance, explained for learning. Not legal advice.
