Security, NDA and data protection
Security, NDAs and data protection: how we look after your code and data
Clients trust Zero One Creation with source code, customer records and access to live systems. This page sets out what we sign, how we access your systems, how we build, and where your data lives.
It describes our working practices. It is not a certification.
At a glance
- NDA before detailed requirements
- Code and IP in your name
- Individual, least-privilege access
- No credentials over email or chat
- Code review on every change
- Hosting in your own accounts
- Backups, with a restore check
- Personal data handled with care
Before any detail is shared
NDA first, and everything in your name
Confidentiality and ownership are settled in writing at the start, not negotiated at the end. The same terms apply in every engagement model.
- 01
An NDA before detailed requirements
We sign a non-disclosure agreement before you share specifications, data or system access. We can sign yours or share ours. The data you share is used only for your project, by the people working on it.
- 02
Code and IP assigned to you
Our contract assigns the intellectual property in the work we build for you to your company. Source code lives in a repository your organisation owns, with its full history.
- 03
Accounts that were always yours
Cloud hosting, domains, app store listings, email services and payment gateways are set up in your accounts, so there is nothing to recover if you change teams.
Least privilege
How we access your systems
Working on your product often means access to your servers, databases, cloud console, CMS or CRM. We ask for the least access the work needs, for as long as it needs it, and in a way you can see and control.
Individual accounts
Each person gets their own login to your systems. No shared passwords, so every action can be traced to someone.
The lowest role that does the job
Read-only where reading is enough, and production access only for the people who deploy or support it.
Two-factor sign-in
Turned on for every account we use, wherever the platform supports it.
You stay the owner
Your organisation holds the owner or admin role. We are invited users you can see, limit or remove at any time.
Reviewed and removed
Access is removed when someone leaves the project, and reduced or removed at the end of the engagement, as you prefer.
Credentials and secrets
Passwords and API keys never travel in plain text
Most leaks are not clever attacks. They are a password pasted into a chat or an API key committed to a repository. These rules close those gaps.
- Never sent in plain text by email, chat or messaging apps
- Shared through a password manager or the platform's own invite system
- Kept in environment variables or the host's secret store, never committed to the repository
- Separate keys for development, staging and production
- Rotated at handover, and whenever someone with access leaves the project
Secure development
Security built into how we write code
Security is cheapest when it is part of the everyday routine rather than an audit at the end. These practices apply to every product we build and maintain. For the common weaknesses on websites, see our guide to website security vulnerabilities and how to prevent them.
Code review on every change
Every change goes through a pull request and is reviewed by another engineer before it is merged.
Dependency updates
Libraries and frameworks are kept current, and security advisories are checked and acted on.
Validation at every boundary
Input is validated on the server, database queries are parameterised, and public endpoints are rate limited.
Proven authentication
Sign-in, sessions and role-based access built on established libraries rather than home-made code.
Secrets kept out of code
API keys and passwords live in environment settings, and repositories are kept free of them.
Separate environments
Development, staging and production are kept apart, and we use test data in development wherever we can.
Encrypted connections
HTTPS everywhere, for the application, its APIs and the admin screens.
Audit logs where they matter
Products that handle money, approvals or personal data record who changed what, and when.
Hosting and backups
Hosted in your accounts, backed up and watched
Your own cloud accounts
Applications run in hosting accounts your organisation owns, such as AWS or Vercel. We help you pick a region that suits your users and any data requirements, and you hold the billing relationship.
AWS cloud servicesBackups that restore
Automated backups of databases and stored files, with frequency and retention agreed with you. A backup only counts if it restores, so we check a restore before launch.
Monitoring and alerts
Error monitoring and uptime checks, so problems reach us before they reach your customers, and logs to investigate them when they do.
Personal data
Data protection and India's DPDP Act
India's Digital Personal Data Protection Act, 2023 sets out how organisations must handle the personal data of people in India. When we build a product that collects personal data, we design with it in mind.
Your organisation is usually the Data Fiduciary, deciding why and how data is processed. We process it on your instructions. We are engineers, not lawyers, so we work alongside your legal adviser. If you also serve users in other countries, tell us early so their rules shape the design too. More in our article on data privacy regulations for business apps.
- 01.
Collect only what is needed
Forms and databases are designed around the data the product actually uses, not everything that might be useful one day.
- 02.
Clear notice and consent
Where consent is the basis for processing, we build notice and consent into the user journey, and record it.
- 03.
Rights users can exercise
Ways for people to see, correct and ask for deletion of their data, built in rather than handled by email.
- 04.
Retention and deletion
Data that is no longer needed can be deleted on a schedule you set, including from backups over time.
- 05.
Planned breach response
Logs, contacts and a plan in place, so a suspected breach can be investigated and reported without delay.
When things change
If something goes wrong, and when the work ends
If there is a security incident
If we find or suspect a security problem in something we built or look after, we tell you straight away, work to contain it, and help you investigate and meet any duty you have to notify users or regulators.
When the engagement ends
Credentials are handed back and rotated, our access is removed or reduced as you prefer, and copies of your data used during the project are deleted from our working environments. Documentation stays with you.
Practices, not certificates
Everything on this page describes how we work. If your organisation needs vendors to hold specific certifications or to complete a security questionnaire, raise it on the first call and we will answer plainly. For the data you share with us through this website, see our privacy policy.
Have security or compliance requirements? Bring them to the first call.
Share your policies, questionnaire or NDA early. We'll tell you how we would meet them, in writing, before any work starts.
Security questions
Frequently asked questions
Will you sign an NDA before we share details?
Who owns the code and intellectual property?
How do you access our systems?
How do you handle passwords and API keys?
Where will our application and data be hosted?
Do you follow India's DPDP Act?
Do you hold security certifications?
What happens to our data when the engagement ends?
What if there is a security incident?
Related pages
- CompanyHow we workOur delivery process, weekly cadence and handover.
- CompanyEngagement modelsHow projects are scoped, changed and billed.
- PolicyPrivacy policyHow we handle data you share with us through this website.
- ServiceAWS cloud servicesHosting, backups and monitoring in your own AWS account.
- GuideWebsite security vulnerabilitiesThe common weaknesses, and how to prevent them.
- GuideData privacy rules for business appsWhat privacy regulation means for the apps you build.
Talk to us
Tell us what you need to protect.
A short note about your product, the data it handles and any requirements from your organisation is enough to start. We'll suggest how to handle access, hosting and data from the outset.
- +91 95683 56730
- Chat on WhatsApp
- contact@zeroonecreation.com
- 3rd Floor, 113 Double Phatak, Meerut Road, Roorkee, Uttarakhand 247667
- Monday – Saturday, 9 AM – 5 PM