How Volge handles personal and enterprise data, and why the standard matters.
The obligation is architectural, not just legal
Volge handles enterprise data that, in aggregate, touches the records of millions of people: patients, account holders, citizens, employees. The data we process in the course of a financial-services transformation or a healthcare platform build is not abstract. It describes real individuals whose access to services, credit, and care depends on how that data is handled. The obligation this creates is not discharged by ticking a compliance checkbox. It is architectural: built into how we design systems, how we configure access controls, and how we advise clients on their own data governance.
We operate on the principle that personal data should do the minimum necessary work to achieve a defined purpose, and then stop. It should not accumulate, migrate to secondary uses, or persist beyond its utility. These are design constraints, not aspirations. When we build systems that cannot meet these constraints, we say so, and we redesign before deployment, not after.
Five constraints that apply to every engagement
Data minimisation
We collect and process only the personal data that is strictly necessary for the defined purpose of the engagement. Data fields that are available but not required are not ingested. Schema design is reviewed against purpose statements before any data pipeline goes live.
Purpose limitation
Data collected for one purpose is not processed for a different purpose without documented client authorisation and, where required by law, individual consent. This applies to analytics, model training, and any secondary processing that was not specified in the original data processing agreement.
No secondary use without consent
Client data processed during an engagement is never used to train general-purpose models, benchmarked against other clients' data, or repurposed for Volge's own research or product development without explicit, written, revocable consent from the data controller.
Encryption at rest and in transit
All personal data handled by Volge-managed infrastructure is encrypted at rest using AES-256 and in transit using TLS 1.3 minimum. Key management follows NIST SP 800-57 guidelines. Encryption requirements are applied to client environments during technical architecture engagements.
Right to erasure
Where applicable under relevant law, individuals whose data is processed by systems Volge has built have the right to request erasure. We design systems with erasure capability from the outset, not as a retrofit. Erasure requests routed to Volge are processed within 30 days and confirmed in writing.
Frameworks Volge complies with
GDPR: General Data Protection Regulation
European Union and European Economic Area
Compliant
UAE Federal Decree-Law No. 45 of 2021
United Arab Emirates. Personal Data Protection
Compliant
PDPL: Personal Data Protection Law
Kingdom of Saudi Arabia
Compliant
DPDP Act 2023: Digital Personal Data Protection Act
India
Compliant
US State Privacy Laws
California CPRA, Virginia CDPA, and applicable state laws where Volge operates or serves clients
Aligned
What happens to data within an engagement
Client data is never used to train AI or ML models that serve other clients or that form part of Volge's general-purpose tooling. Each engagement operates within an isolated data environment. Cross-engagement data access is technically blocked at the infrastructure level, not managed by policy alone.
Data environments are isolated per-client using dedicated storage accounts, separate encryption keys, and role-based access controls scoped to the specific engagement team. Data is not commingled with other client environments at any infrastructure layer.
Data is deleted on contract end within 30 days of engagement closure unless the client explicitly elects retention and signs a post-engagement data agreement. Deletion is cryptographically verified and a deletion certificate is issued. Where regulatory obligations require Volge to retain records, the minimum required scope is retained and documented.
Data transfer outside the contractually agreed jurisdiction is not permitted without client authorisation and a transfer mechanism compliant with the applicable privacy framework: Standard Contractual Clauses, adequacy decisions, or equivalent.
Data breach response protocol
72-hour notification commitment
0–4h
Incident detection and initial triage by the on-call security team. Containment measures initiated. Incident Commander assigned. Internal escalation to Chief Information Security Officer and General Counsel.
4–24h
Scope determination: which data categories are affected, how many individuals, which clients. Forensic preservation of evidence. Affected client primary contacts notified with preliminary findings and a confirmed timeline for full notification.
24–72h
Formal notification to affected clients with full incident report: root cause (if determined), affected data scope, remediation steps taken, and recommended actions for clients. Regulatory notification filed where legally required within the applicable window.
Post-72h
Root cause analysis completed within 14 days. Post-incident review with affected clients. Remediation roadmap delivered. Independent audit commissioned where appropriate. Findings incorporated into security architecture reviews.
Privacy enquiries and rights requests
Data rights requests, privacy policy questions, and concerns about how Volge or a Volge-built system has handled personal data should be addressed to the Privacy Office. All requests receive an acknowledgement within two business days.