What we promise, in one place.
This page explains how your code and data are protected when you work with CODT Technologies. It also gathers the data-protection, residency, ownership and process commitments we make on other pages of this site. Each claim links to the page it comes from.
Your systems stay in your jurisdiction.
Before you let an offshore team near your product, you should know where the system runs, what leaves it, and who can get in. Our answer is the same on every project. We build and deploy in your region. Nothing moves to ours unless you allow it in writing. Engineers get in only through a route you control.
Built and deployed in your region
We build and deploy your system on infrastructure in your own jurisdiction. You pick the environment your product runs in, in the country your business and your regulator answer to. The region is settled during scoping as part of the architecture, so nothing has to move 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 allows it. If the contract is silent, the answer is no, and your material stays where your system lives. Any transfer you do allow is covered by standard contractual clauses.
Access only through a route you control
Engineers work in one of two ways. Either inside a virtual desktop that your team owns and runs, or from our Gurugram office over a single static IP address that your team allow-lists. We agree which one per engagement. In both cases your team set up the access, so your team can also shut it off.
An NDA first, then the standard contracts
We sign an NDA before any technical discussion begins. After that we sign a data processing agreement, plus standard contractual clauses for any transfer your contract allows.
Swiss law as governing law, if you need it
If you are a Swiss client, you can choose Swiss law, the Code of Obligations your own lawyers already work with, as the governing law for disputes. It is a contracting option we agree per engagement. It says nothing about where we are registered: CODT Technologies is an Indian private limited company.
At handover, everything is yours
100% of the code, IP and infrastructure transfers to you, including the setup of the environment running in your region. If the engagement ends or changes shape, what your product depends on stays with you.
Privacy built in, with your local law in view.
Every engagement is GDPR-aware by default, and privacy is part of the design from the first commit. If your country has its own data-protection law, we design with that law in view as well.
GDPR-aware by default
Privacy-first architecture is our engineering default. We decide it before the first database schema exists, and EU data residency is available on request. We have built this way for European clients for nearly a decade.
Switzerland — the nDSG
The nDSG is Switzerland's revised Federal Act on Data Protection. Our Swiss engagements are GDPR- and nDSG-aware by default and built privacy-first. 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 our decisions on consent, retention and data flows from the first architecture review, on top of the GDPR baseline every project gets.
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, in addition to GDPR.
Where your data lives is part of the scope.
We agree residency at the start of each engagement, and we already run it in production.
Delivered in production: AWS Sydney
LeadTrack AI, the multi-tenant voice-agent platform we built for a Melbourne-based client, keeps its data in AWS Sydney and has handled 100,000+ live calls. We can set up the same Australian residency for your build on request.
EU or Swiss residency on request
For European projects, EU or Swiss data residency can be written into the scope on request.
Who owns the code
You will find these ownership terms on our contact page and 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, with no lock-in and no per-seat licence on anything we build for you.
NDA on request
Ask for an NDA and we sign it before the detailed project talk starts.
How every engagement runs.
Each engagement starts with a paid discovery sprint and moves to a fixed-price build. After launch, we offer ongoing care.
Senior review on every change
Engineering is done by a senior team in Gurugram, India. Every change is reviewed by a senior engineer, and you get estimates you can hold us to.
Paid discovery sprint, fixed quote
Every engagement starts with a paid discovery sprint. It ends with a written scope and a fixed price before any code is written, so there are no open-ended day rates.
A senior engineer reads your brief
When you write to us, a senior engineer, not a sales rep, reads your brief and replies within one business day, before any engagement begins.
Questions clients ask about trust and ownership
Mettilo in un brief. Un ingegnere senior — non un commerciale — ti risponde entro un giorno lavorativo.
Where is our system actually built and deployed?
In your region. We build and deploy on infrastructure in your own jurisdiction and agree the details during scoping. No client code or data moves to India unless your contract allows it in writing.
How do your engineers access our environment?
Only through access your team sets up. Either our engineers work in a virtual desktop you own, or they connect from our Gurugram office over one static IP address that you allow-list. We agree the model per engagement, and you can close the access again.
What is signed before work starts?
An NDA before any technical discussion. After that come a data processing agreement and standard contractual clauses. Swiss clients can also pick Swiss law as the governing law for disputes; we agree that option per engagement.
How do you handle GDPR and EU data protection?
GDPR awareness is our default and costs nothing extra, and we can arrange EU data residency on request. Our longest-running European engagements have worked this way for years.
How do you handle Swiss data protection and the nDSG?
By default, every Swiss project is designed with both GDPR and the nDSG (the revised Federal Act on Data Protection) in mind. We build privacy-first, and on request your data can stay in Switzerland or the EU.
Can our data stay in our own region?
Yes, and that is the default. Your system runs on infrastructure in your own jurisdiction, and nothing moves to India unless the contract says so in writing. We already do this in production: LeadTrack AI keeps its data in AWS Sydney. For European projects, EU or Swiss residency is available on request.
Who owns the code and the intellectual property?
You do. All code, IP and infrastructure transfer to you, with no lock-in and no per-seat licence.
Will CODT Technologies sign an NDA?
Yes, on request. We sign it before any detailed project discussion, and every engagement gives you 100% of the IP.
How does an engagement start?
With a paid discovery sprint. We scope the product together, and you get a fixed quote in writing before the build starts. Before that, a senior engineer reads your brief and replies within one business day.
Hai un problema che
vale la pena risolvere bene?
Raccontaci il tuo prodotto, le tempistiche e i vincoli. Ti risponderemo entro un giorno lavorativo con una valutazione onesta su fit, scope e il team giusto da assegnarti.