Which entity signs, where delivery happens, how data is handled, what subcontracting is disclosed, and how an engagement ends.
01Who signs
02Where we deliver from
03Data
04Subcontracting
05How an engagement ends
06Insurance and liability
01
Who signs
One agreement with the group entity, with delivery responsibilities per company set out in the schedule. You hold one commercial relationship regardless of how many of the four companies are involved, and one escalation path.
Where a single company is doing all the work, contracting directly with that company is also available and is sometimes simpler. We will say which we think fits at proposal stage.
02
Where we deliver from
The group delivers from competence centres across the DACH region and Central and Eastern Europe: Switzerland, Germany, Austria, Poland, Czechia, Slovakia, Slovenia, Croatia, Serbia, North Macedonia, Romania, Lithuania and Turkey, with more than one location in some of them. Two are the group's own companies, in Skopje, North Macedonia (since 2017) and in Romania (since 2020). Project work reaches almost every European country.
Nearshore delivery is stated rather than implied. Procurement establishes this in due diligence in any case; all concealment buys is a worse conversation later. The engagement schedule names the delivery locations for your work specifically, and they do not change without notice to you.
Competence centres
Project work across almost all of Europe
03
Data
Personal data is processed under the GDPR ↗, and for Swiss-domiciled clients under the revised Federal Act on Data Protection ↗, which has applied since 1 September 2023. Processing locations are named in the engagement schedule and are contractually binding.
Access control and information security management follow ISO/IEC 27001 ↗. Current certification status per group entity is being confirmed and will be published here with the certificate scope and expiry rather than as a claim. We would rather this section say "being confirmed" than assert something a buyer can check.
For financial entities in scope of the Digital Operational Resilience Act ↗, we can supply the information your register of ICT third-party arrangements requires, as part of onboarding.
04
Subcontracting
Work delivered by another company within the group is not subcontracting and is named in the schedule. Work delivered by a party outside the group requires your prior written agreement.
There is no standing right to subcontract in our template terms, and we do not ask for one.
05
How an engagement ends
Handover documentation is maintained from the start of the engagement rather than produced at termination. The version written under notice is always the worse one.
Exit obligations are reciprocal: the same duties we ask of a client apply to us. Where we operate a system, exit includes a defined transition period, current runbooks, and knowledge transfer to whoever takes over, including a competitor.
06
Insurance and liability
Professional indemnity and liability terms are provided with every proposal.
Specific cover and limits per entity are being confirmed for publication here.
You have read the terms. The next step is a conversation about which of the four companies your work sits with, and what the schedule would actually say.