IP Protection in Nearshoring: Access, Repositories, Offboarding

IP Protection in Nearshoring: Access, Repositories, Offboarding

Anyone who has software built by an external team wants to be sure of two things: that code and know-how stay where they belong, and that the result is available to the client at the end. The NDA is usually the first document to be signed. How well intellectual property is protected day to day, however, depends on other questions: Who can access which repository, where are credentials stored, and what happens when someone leaves the team?

We organize this in a Nearshore Team with three locations according to fixed rules. Where technology reaches its limits is covered at the end.

Short answer

An NDA imposes a duty of confidentiality. Who receives which rights to the resulting code is set out in the development contract. On the technical side, the code is protected by time-limited access rights, a defined offboarding process, centralized secrets management, separate repositories and logging. Clients clarify the contractual side with their legal department or law firm.

What an NDA Covers

An NDA specifies who is permitted to disclose information to third parties. It does not specify who is permitted to use, modify, or resell the code. That is covered in the development agreement.

A rule in the German Copyright Act shows why this distinction matters for external teams. Under § 69b of the German Copyright Act (UrhG) the economic rights to software that employees write in the course of their duties belong to the employer. This rule does not apply to external service providers. For them, the grant of rights of use is governed by the contract (Section 31 UrhG). What such a clause must look like in an individual case is for a legal department or law firm to assess. Here we stay with the part we are responsible for as developers.

Where Intellectual Property Gets Lost in Day-to-Day Work

Deliberate theft is rare. The typical gaps are organizational:

  • A repository containing code from multiple clients, or private accounts through which developers access client code
  • Access rights that are granted generously at the start of a project and are never adjusted afterward
  • API keys and passwords in configuration files, tickets, or chat histories
  • Accounts of former team members that are still active weeks after they left

An NDA does not prevent any of these situations. All four can be resolved through technical and organizational measures.

The Measures, in the Order We Tackle Them

  1. Need-based access rights. Each person is granted access to the systems they need for their current task, limited to the duration of that task. Overly broad permissions are the greatest risk in day-to-day work, and restricting them is also the measure that requires the least effort.
  2. Offboarding as a standard process. If someone leaves the project, all access privileges are revoked on the same day, following a checklist rather than relying on memory.
  3. Centralized secrets management. Login credentials are stored in a system designed for that purpose, not in files or chats.
  4. Separate repositories for each client. We believe the best solution is for the code to be stored in a repository owned by the client from the very beginning. That way, there will be no issue regarding the handover of the code when the project ends.
  5. Logging. Access is logged so that it can later be traced who accessed what and when.

How This Is Organized at torck

In every project, the contracting party is torck GmbH in Germany, even if developers from Vienna or Rabat are involved. The company in Morocco, with an office in Rabat (registered office in Casablanca), is a separate torck company and not a brokered partner. Clients therefore have one contract and one point of contact, without a chain of subcontractors through which access is passed along.

Reviews, the CI/CD pipeline, and access rules are the same at all three locations. The time difference between Maxhütte-Haidhof and Rabat is one to two hours. As a result, access approvals and revocations take place on the same business day. For teams in Asia, however, these matters often remain unresolved overnight.

Where Technology Reaches Its Limits
Access rules do not prevent leaks by someone with authorized access. They make such a leak traceable and limit how much can be affected at once. None of these measures settles which rights to the code are contractually held by whom. That is for the client's legal department or law firm to assess.

Access and Offboarding in Your Own Project
We'd be happy to demonstrate how we set up repositories, access, and offboarding for a nearshore team using a specific project as an example. Initial consultation: 30 minutes, free of charge, response within one business day.

Get in touch

Frequently Asked Questions

Is an NDA enough to protect the code?

It is the basis for confidentiality. It does not govern who receives which rights to the code; that is set out in the development contract. In day-to-day work, it does little against an account that stays active after a developer leaves. That takes access rules and a defined offboarding process.

Where should the code be located?

Ideally in a repository owned by the client, where the external team works with its own personal accounts. The client can then see the current state at any time and revoke access directly. At the end of the project, nothing needs to be handed over.

Which technical measures should be implemented first?

Access rights first, then the offboarding process. Accounts that nobody revokes are the most common gap in an otherwise well-organized project. Secrets management, separate repositories and logging follow once these two are in place.

IP Protection in torck's Contract Structure

At torck, the contracting party is always the German torck GmbH, and the same access rules apply at all three locations. We discuss what this looks like for a specific project in an Initial Consultation.

Schedule a meeting

Legal note
This article refers to laws and regulations to put technical decisions in context. It is not legal advice. Whether and how a rule applies to your company is a question for your legal department or a law firm.

Questions about this post?

Just a couple of sentences about your situation will suffice. The person responding builds these kinds of systems himself.

We'll respond within one business day.torck · Code mit Drehmoment
Florian Blischke
Managing Director at torck · Over 20 years of software development experience
Florian Blischke is the managing director of torck, based in Maxhütte-Haidhof near Regensburg. He has been working in software development for over 20 years. His focus is custom software, data and AI for industry and retail, ranging from the integration of physical processes and IoT to cloud architecture and data- and AI-driven systems. torck works with its own nearshore team in Rabat. At torck, he oversees projects including the Jouvoli energy platform and the KVM Fleet fleet management product. torck develops software at its locations in Maxhütte-Haidhof, Vienna and Rabat and focuses on software that actually works in operation.

Are you facing the same question?

Since 2017, we have been building software for industry and retail from Maxhütte-Haidhof near Regensburg, with teams in Vienna and Rabat. An initial consultation takes 30 minutes and costs nothing. Afterwards you will know whether the project is worth pursuing, even if the answer is no.

More Articles