01Our approach
Clients trust us with source code, customer data, credentials and business plans. This page explains, in plain English, how we look after them. It describes our standard practice; where your contract or a signed data processing agreement says something more specific, that document takes priority.
We do not claim certifications we do not hold. If your organisation requires a specific standard or a completed security questionnaire, tell us before the project starts and we will respond honestly about what we can meet.
02Ownership and accounts
Wherever possible, the systems that hold your work are created in accounts that you own:
- Code repositories (GitHub, GitLab or Bitbucket) under your organisation.
- Cloud hosting, domains and databases under your billing and root access.
- App Store, Play Store and Shopify Partner accounts registered to you.
- Design files in a workspace you control.
We work through invitations and roles that you can remove at any time. This means you are never locked out of your own product.
03Access control
- Need to know: only team members assigned to your project are given access.
- Individual logins: we ask for named accounts rather than shared passwords, so access can be traced and removed person by person.
- Two-factor authentication: we enable it on the accounts we use for client work wherever the service supports it.
- Credentials: passwords, API keys and tokens are shared through a password manager or the platform's secret store, not through chat or email.
- Offboarding: when a team member leaves a project, or the project ends, their access is removed and we ask you to confirm.
04Secure development
- Secrets are kept in environment variables or a secret manager and are not committed to repositories.
- Changes go through pull requests and review before they reach the main branch.
- Separate environments are used for development, staging and production. Real customer data is not copied into development unless you approve it and it is masked where practical.
- Dependencies are kept up to date and known vulnerabilities are addressed as part of ongoing work.
- Applications use encrypted connections (HTTPS/TLS), hashed passwords and role-based permissions by default.
- Input validation and protection against common web risks, such as injection and cross-site scripting, are part of our normal build and review checklist.
05Data handling
We only access personal or business data when the work requires it, and we use it only for that work.
- Data stays in the systems you have chosen; we avoid downloading it to personal devices.
- Sample or anonymised data is preferred for development and demos.
- When we act as a processor of personal data on your behalf, the terms are set out in our Data Processing Addendum.
- How we treat personal data collected through this website is described in our Privacy Policy.
06Backups and continuity
For products we host or maintain under a Care plan, we configure automated backups using the hosting provider's tools and agree the schedule and retention with you. Restores are tested when the backup is first set up and periodically afterwards. For products you host yourself, we will recommend a backup plan, and running it remains your responsibility unless your contract says otherwise.
07Our people
- Team members and contractors are bound by written confidentiality obligations.
- Client work is carried out on password-protected devices.
- Confidentiality continues after a team member stops working with us.
08Third-party tools and AI
We use well-known tools for communication, project tracking, design, code hosting and deployment. We choose your preferred tools when you have them.
Our team may use AI coding and writing assistants to work more efficiently. We do not put your confidential information, credentials or personal data into AI tools that would use it to train public models. If you prefer that no AI assistance is used on your project, tell us and we will record that in the contract.
09Incidents
If we become aware of unauthorised access to, or loss of, your data in systems we manage, we will:
- Act to contain the problem.
- Notify your named contact without undue delay, with what we know at that point.
- Share what happened, what was affected and what we have done once the facts are established.
- Help you meet any notification duties you may have.
10End of a project
At handover you receive the code, documentation and a list of every account and credential involved. On request we delete local copies of your confidential material and confirm in writing. We recommend that you rotate passwords and keys once handover is complete, and we will guide you through it.
11Reporting a security concern
If you believe you have found a security issue in this website or in something we built, please email ronak@divygfx.com with the details. Please give us reasonable time to investigate and fix the issue before sharing it publicly. We appreciate responsible reports and will keep you informed.
Questions about this page?
Write to ronak@divygfx.com. We reply within a business day.
This page is a plain-English summary of our standard practice. Where a signed contract between you and DivyGfx says something different, the contract applies.
