The short answer
We sign an NDA before kickoff. All code and IP created for you are assigned to you. We prefer to work inside your repositories and accounts, we give people only the access their role needs, and we remove it when they leave. We do not currently hold ISO 27001 or SOC 2 certification, and we say so up front so you can decide whether that matters for your project.
NDA before kickoff
Our standard terms state that all code and IP are assigned to you; we sign an NDA before kickoff. The agreement is signed before any confidential information changes hands in earnest, which means before the project starts and before your specifications, data or credentials are shared.
We will sign your NDA if you have one. If you want it in place before an early scoping call, tell us when you first get in touch and we will arrange that. The same confidentiality obligations apply to every engineer and manager who works on your account.
Who owns what
Everything we write for you belongs to you: source code, designs, documentation and anything else created for your project. That is part of the written agreement, not a verbal promise. You do not need our permission to move the work to another vendor or bring it in-house.
Two practical points follow from this. First, we use third-party and open-source components, which keep their own licences, and we tell you what we use. Second, tools and libraries that we built before your project and use across clients are not ours to give away, but we license anything of that kind to you so the product keeps working. If any of this is relevant to your project, raise it during discovery and we will put it in writing.
Access control
| Practice | What it means in a project |
|---|---|
| Least privilege | People get the access their role needs and nothing more. A front-end developer does not need production database access. |
| Role-based access | Repositories, task boards and cloud consoles use roles, not shared logins. |
| Individual accounts | Each engineer uses their own account, so activity can be traced and revoked one person at a time. |
| Client-owned accounts | Where possible, source control, hosting and third-party services are in accounts you own, and we are invited in. |
| Separate environments | Development, staging and production are kept apart, with production access limited and reviewed. |
Repositories and code
Work happens in private repositories. Where you want us to, we use your own organisation on GitHub or the platform you prefer, so you hold the complete history from the first commit. Changes go through pull requests and peer review. That is our standard practice and is described on How We Work. Code is never posted to public repositories or to public code-sharing sites without your agreement.
Credentials and secrets
- Secrets such as API keys and database passwords are kept out of source code.
- They are stored in environment configuration or a secrets manager, not in chat messages or tickets.
- We ask you to share credentials through a password manager or equivalent, not by email.
- Credentials are rotated when people leave a project and when anything is exposed by mistake.
- Where a service supports it, we ask for scoped or temporary access instead of full admin credentials.
Data protection practices
We try to avoid handling real customer data at all. Development and testing use synthetic or anonymised data wherever possible. When real data is needed, we agree with you what is required, where it may be stored and when it will be deleted. Data is processed on your infrastructure where that is practical, and we do not copy it to personal devices or personal accounts.
We can sign a data processing agreement (DPA) when you need one, for example under GDPR, and we can follow data-residency or handling rules that you set. We will tell you early if a requirement is something we cannot meet.
Offboarding
When a developer leaves a project, whether by replacement, a reduction in team size or the end of the engagement, offboarding happens with the handover. Access to repositories, task boards, cloud accounts and communication channels is removed, credentials that person had access to are rotated where needed, and you receive confirmation. Local copies of your code and data are deleted from our side at the end of the engagement, on request.
What we do not have
We are open about this because security pages often are not.
- We do not currently hold ISO 27001 certification.
- We do not currently hold SOC 2 certification.
- We do not claim HIPAA, PCI DSS or any other compliance status.
That does not mean we ignore security. It means we have not completed those audits. If your project needs a vendor with a specific certification, we are probably not the right choice today, and we would rather tell you that now. If your requirement is that the work meets certain controls, such as access rules, logging, encryption or regional data storage, we can often work within that, usually inside your cloud environment and your policies. Talk to us during discovery and we will say plainly what we can and cannot do.
How to raise a question
Ask before you sign, not after. Send your security questionnaire or requirements through our contact page, and we will answer them in writing. For the working model around this, including trial periods, replacement and billing, see How We Work. For how we are set up as a company, see About.
