What this policy is
Sets the organization's overarching privacy commitments under applicable laws (GDPR, CCPA, India DPDP, etc.) — the policy a Data Protection Officer authors and a privacy auditor reads.
Why every organization needs one
Privacy regulators expect a written policy that articulates how the org meets every principle (lawful basis, minimisation, accuracy, storage limitation, etc.). This is that document.
What a competent Data Protection Policy typically contains
- Purpose and scope
- Roles and responsibilities
- Definitions
- Lawful-basis framework
- Data-subject-rights handling
- DPIA threshold and process
- Cross-border-transfer mechanism
- Review cadence (typically annual) and version control
- Approval, sign-off and effective date
How iCompaas tracks this policy
The icompaas policy-doc producer manages this document through an 8-state lifecycle: draft → generated → internal_qa → customer_review → in_review → approved → signed (with rejected as a terminal side-state). The producer publishes a policy_doc_data_protection_policy_signed compliance finding once at least one document of this kind reaches the signed state for the account being assessed; the finding then rolls up into every compliance framework that references this policy (see the table below).
Compliance frameworks that reference this policy
The icompaas compliance controls library links every policy document to the controls in each framework that require, evidence, or otherwise rely on it. Below: every control across every framework in the iCompaas catalogue that names this policy as part of its evidence base. Each control links to its own dedicated page with auditor-view content + implementation guidance.
| Framework | Control | Title | Component |
|---|---|---|---|
| ISO/IEC 27001:2022 | A.5.14 | Information transfer | Organizational controls |
| ISO/IEC 27001:2022 | A.5.34 | Privacy and protection of personal identifiable information (PII) | Organizational controls |
| ISO/IEC 27001:2022 | A.8.24 | Use of cryptography | Technological controls |
| ISO/IEC 27001:2022 | A.8.33 | Test information | Technological controls |
| ISO/IEC 27701:2025 | A.1.2.9 | Records related to processing PII | Conditions for collection and processing |
| ISO/IEC 27701:2025 | A.1.3.6 | Mechanism to object | Obligations to PII principals |
| ISO/IEC 27701:2025 | A.1.4.3 | Limit processing | Privacy by design / default |
| ISO/IEC 27701:2025 | A.2.2.5 | Infringing instruction | Conditions for collection and processing (processors) |
| ISO/IEC 27701:2025 | A.3.31 | Test information | Security considerations |
9 controls across 2 frameworks reference this policy.
About this page
This article is part of the iCompaas Policy Documents library — one page per signed-document type the icompaas policy-doc producer tracks for customer accounts. The article is intentionally framework-agnostic: a customer signing a policy of this kind gets the same regulatory benefit across every framework that references it.