Data Policy
The operational side of data handling — where it is stored, who can reach it, how it is backed up, and what happens when a project ends.
Last updated: 8 August 2026
Scope
This document covers data held inside systems we build and operate. It sits alongside the Privacy Policy, which covers personal data specifically; where the two overlap, the Privacy Policy governs.
Controller and processor
- Our own applications — we are the controller. We decide what is collected and why, and the Privacy Policy applies directly.
- Software built for a client — the client is the controller. We are the processor and act only on their documented instructions.
Where data lives
Deployment is the client’s choice, and it determines where the data physically sits:
- On-premise — on the client’s own Windows Server. The data never leaves their building.
- Cloud — Microsoft Azure or a comparable provider, in an Indian region unless the client asks otherwise.
- Managed VPS — a server we operate for the client, again in an Indian region by default.
Who can access it
- Access is granted per person, per system — never a shared login.
- Only engineers assigned to that project hold production credentials.
- Access is logged, and reviewed when someone joins or leaves the project.
- Support staff work from anonymised copies wherever the issue allows it.
Backups and recovery
- Automated daily backups, encrypted at rest, with a retention window agreed per client.
- Restores are tested on a schedule — a backup nobody has restored is not a backup.
- Recovery objectives are written into the AMC rather than left to good intentions.
If something goes wrong
On discovering a breach we contain it first, then notify the affected client without undue delay and in any case within 72 hours, with what we know: what happened, what data was involved, what we have done and what we recommend. A written post-mortem follows once the incident is closed.
Sub-processors
We use a small number of infrastructure providers — hosting, SMS and email delivery, payment gateways, and crash reporting. Each is bound by contract to process data only for the service they provide. The current list is available to any client on request.
Client-owned systems and exit
- The database and the data in it belong to the client, not to us.
- On request — or when an engagement ends — we hand over a complete export in a documented format, plus the source code where the contract includes it.
- After handover and a confirmation period, we delete our working copies and confirm the deletion in writing.
Contact us
Questions about this document, or a request relating to your data, go to the same place:
- info@keycodetech.com
- keycodetechnology@gmail.com
- KeyCode Technology Pvt. Ltd. · Gorakhpur, Uttar Pradesh, India