What we promise, in one place.
This Trust Center sets out how your code and your data are protected when you build with CODT Technologies — where your systems are deployed, who can reach them, and on what paperwork — alongside the data-protection, residency, ownership and process commitments we make across the site. Every claim names where it comes from, and none of them is written stronger than what we can stand behind.
Your systems stay in your jurisdiction.
The offshore question that matters is not where our engineers sit — it is where your system runs, what leaves it, and who can reach it. Our answer is the same on every engagement: build and deploy in your region, move nothing to ours without written authorisation, and let engineers in only through a route you control.
Built and deployed in your region
Your system is built and deployed on infrastructure in your own jurisdiction — the environment your product runs in is one you choose, in the country your business and your regulator answer to. The region is settled during scoping, as part of the architecture, not retrofitted after launch.
Nothing comes to our region unless you put it in writing
No client code and no client data moves to India unless your contract explicitly authorises it. If the agreement is silent, the answer is no — your material stays where your system lives, and any transfer that is authorised is covered by standard contractual clauses.
Access through a door you hold the key to
Engineers work either inside a virtual desktop your team owns and administers, or from our Gurugram office over a single static IP address your team allow-lists. Either way the access route belongs to you — you granted it, you can see it, and you can close it. Which of the two applies is agreed per engagement.
The paperwork comes before the technical conversation
An NDA is signed before any technical discussion begins — not after a proposal, not once a project is underway. From there the engagement stack is standard: a data processing agreement, and standard contractual clauses for any transfer the contract does authorise.
Swiss law, where that is what you need
For Swiss clients, engagements can be contracted with Swiss law as the governing law for disputes — the Code of Obligations, the frame your own counsel already works in. That is a contracting option agreed per engagement, not a statement about where we are incorporated: CODT Technologies is an Indian private limited company.
And at the end of it, all of it is yours
The chain ends where it should: 100% of the code, IP and infrastructure transfers to you — including the configuration of the environment running in your own region — so what your product depends on stays with you when the engagement changes shape.
Privacy-first by default, jurisdiction-aware by design.
Every engagement is GDPR-aware by default — privacy-first engineering from the first commit, not a compliance add-on. Where a client's jurisdiction has its own data-protection law, the engagement is designed with that law in view.
GDPR-aware by default
Every engagement is GDPR-aware from day one — privacy-first architecture as the engineering default, decided before the first schema — and EU data residency is available on request. We have built this way for European clients for nearly a decade.
Switzerland — the nDSG
Engagements are GDPR- and nDSG-aware by default — the nDSG being Switzerland's revised Federal Act on Data Protection. Projects are built privacy-first, and EU or Swiss data residency is available on request.
UAE — the PDPL
For UAE clients we design PDPL-aware: the UAE Personal Data Protection Law shapes consent, retention and data-flow decisions from the first architecture review, on top of our GDPR-by-default baseline.
Australia — the Privacy Act 1988 and the APPs
Australian engagements are designed with the Privacy Act 1988 and the Australian Privacy Principles (APPs) in view, on top of our GDPR-by-default baseline.
Where your data lives is part of the scope.
Residency is agreed per engagement, not bolted on afterwards — and we have already delivered it in production.
Delivered in production: AWS Sydney
LeadTrack AI — the multi-tenant voice-agent platform we engineered for a Melbourne-based client — runs with data resident in AWS Sydney, hardened across 100,000+ live calls. The same Australian data residency can be arranged for your build on request.
EU or Swiss residency on request
For European engagements, EU or Swiss data residency is available on request as part of the engagement scope — builds are privacy-first from the first commit either way.
You own the work. All of it.
Ownership terms are the same on every engagement — stated on our contact page and repeated on every regional page.
100% transfer of code, IP and infrastructure
You own what we build. 100% of the code, IP and infrastructure transfers to you — no lock-in, and no per-seat licence on what we build for you.
NDA on request
An NDA on request is standard before any detailed project discussion, and every engagement includes 100% IP ownership — the code, the product, and the intellectual property are yours.
Discipline you can hold us to.
The same delivery discipline applies to every engagement, in every region: paid discovery sprint, fixed-price build, ongoing care.
Senior review on every change
Engineering is delivered by a senior team across Silicon Valley and Gurugram — senior review on every change, honest scope, and estimates you can hold us to.
Paid discovery sprint, fixed quote
Every engagement starts with a paid discovery sprint that ends in a fixed, transparent quote — a written scope and a fixed price before any code, no open-ended day rates.
A senior engineer reads your brief
When you write to us, a senior engineer — not a sales rep — reviews your brief and replies within one business day, before any engagement begins.
Questions clients ask about trust and ownership
Zet het in een briefing. Een senior engineer — geen verkoper — reageert binnen één werkdag.
Q.01Where is our system actually built and deployed?
In your region. Systems are built and deployed on infrastructure in your own jurisdiction, agreed during scoping as part of the architecture — and no client code or data moves to India unless your contract explicitly authorises it in writing.
Q.02How do your engineers access our environment?
Through a route you control. Engineers work either inside a virtual desktop your team owns and administers, or from our Gurugram office over a single static IP address your team allow-lists. Which model applies is agreed per engagement, so the access you grant is access you can also close.
Q.03What is signed before work starts?
An NDA before any technical discussion, then a data processing agreement and standard contractual clauses as standard. For Swiss clients, engagements can also be contracted with Swiss law as the governing law for disputes — a contracting option, agreed per engagement.
Q.04How do you handle GDPR and EU data protection?
GDPR awareness is the engineering default, not a paid extra: builds are privacy-first from the first commit, and EU data residency can be arranged on request. Our longest-running European engagements have operated this way for years.
Q.05How do you handle Swiss data protection and the nDSG?
Engagements are GDPR- and nDSG-aware by default — the nDSG being Switzerland's revised Federal Act on Data Protection. Projects are built privacy-first, and EU or Swiss data residency is available on request.
Q.06Can our data stay in our own region?
Yes — it is the default, not the exception: your system is built and deployed on infrastructure in your own jurisdiction, and nothing moves to India unless the contract says so in writing. We have already delivered this in production — LeadTrack AI runs with data resident in AWS Sydney — and for European engagements EU or Swiss data residency is available on request.
Q.07Who owns the code and the intellectual property?
You do. 100% of the code, IP and infrastructure transfers to you — no lock-in, and no per-seat licence on what we build for you.
Q.08Will CODT Technologies sign an NDA?
Yes. An NDA on request is standard before any detailed project discussion, and every engagement includes 100% IP ownership — the code, the product, and the intellectual property are yours.
Q.09How does an engagement start?
With a paid discovery sprint: we scope the product together and you receive a fixed, transparent quote before any build begins. A senior engineer reviews your brief and replies within one business day.
Een probleem dat het waard is om
goed op te lossen?
Vertel ons over uw product, uw planning en uw randvoorwaarden. We reageren binnen één werkdag met een eerlijke inschatting van fit, scope en het juiste team ervoor.