Security and confidentiality
Working with a remote team works best when everyone agrees early on who can see what, and how sensitive material is kept safe.
Handing part of your software work to a team in another country means sharing information you would rather keep close: product plans, source code, customer data structures and access to systems. This page explains, in plain terms, the practices that keep that information protected throughout a project.
Confidentiality agreements come first
A non-disclosure agreement (NDA) is a simple contract in which both sides agree not to pass on what they learn from each other. We suggest signing one before any detailed discussion of your product, so that early conversations about architecture, roadmap or business rules are covered from the start.
A good NDA is short and readable. It should say what counts as confidential, how long the obligation lasts, and what happens to material when the project ends. If you already have your own template, bring it along. Reviewing yours is often quicker than drafting a new one.
Least-privilege access
Least privilege means each person gets only the access they need for their current task, and nothing more. A front-end developer rarely needs database admin rights. A tester does not need to deploy to production.
- Accounts are personal, never shared between people.
- Permissions are granted per project and per role.
- Access is reviewed when someone changes tasks and removed promptly when they leave the project.
- Two-factor authentication is switched on wherever a tool supports it.
Separate environments
Development, testing and production should live apart from each other. Developers work in a development environment, changes are checked in a staging area, and only reviewed releases reach production.
Real customer data should stay out of the non-production environments. Where realistic data is needed for testing, use anonymised or generated samples. This reduces risk for everyone and makes it easier to answer questions about where personal data lives.
Handling credentials and secrets
Passwords, API keys and certificates are the most common way sensitive systems are exposed, usually through carelessness rather than attack. Sensible habits include:
- Keeping secrets in a password manager or a dedicated secrets store, not in chat messages, emails or spreadsheets.
- Never committing keys to the code repository, and scanning for accidental commits.
- Using separate credentials for each environment so a leaked test key opens nothing important.
- Rotating keys when team members change or when anything looks doubtful.
Code and data at the end of a project
Agree in advance what happens when work finishes: repositories handed over, accounts closed, local copies deleted. Ownership of what was built is covered on our code ownership page.
What you can do on your side
- Decide which systems the team truly needs, and create accounts for them rather than sharing your own.
- Write down who approves access requests.
- Include security expectations in your project brief. Our guide to briefing a project shows where.
For an overview of how a project runs day to day, see how we work. If you want to talk through your requirements or request an NDA, reach us through the contact page.