What this policy is
The customer- / data-subject-facing statement of how personal data is collected, used, shared, retained, and protected — covering lawful basis, data-subject rights, and contact for privacy inquiries.
Why every organization needs one
Privacy laws (GDPR, CCPA, DPDP) require a published privacy notice as a baseline obligation. This is also the document customer counsel reads before signing a DPA.
What a competent Privacy Policy typically contains
- Purpose and scope
- Roles and responsibilities
- Definitions
- Categories of personal data collected
- Purposes and lawful basis per category
- Data-subject rights + how to exercise them
- Retention + cross-border transfer disclosures
- 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_privacy_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.34 | Privacy and protection of personal identifiable information (PII) | Organizational controls |
| ISO/IEC 27701:2025 | A.1.2.2 | Identify and document purpose | Conditions for collection and processing |
| ISO/IEC 27701:2025 | A.1.2.3 | Identify lawful basis | Conditions for collection and processing |
| ISO/IEC 27701:2025 | A.1.2.4 | Determine when/how consent obtained | Conditions for collection and processing |
| ISO/IEC 27701:2025 | A.1.2.5 | Obtain & record consent | Conditions for collection and processing |
| ISO/IEC 27701:2025 | A.1.2.7 | Contracts with PII processors | Conditions for collection and processing |
| 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.3 | Information for PII principals | Obligations to PII principals |
| ISO/IEC 27701:2025 | A.1.3.4 | Providing info to PII principals | Obligations to PII principals |
| ISO/IEC 27701:2025 | A.1.3.5 | Modify/withdraw consent | Obligations to PII principals |
| ISO/IEC 27701:2025 | A.1.3.6 | Mechanism to object | Obligations to PII principals |
| ISO/IEC 27701:2025 | A.1.3.7 | Access / correction / erasure | Obligations to PII principals |
| ISO/IEC 27701:2025 | A.1.3.10 | Handling requests | Obligations to PII principals |
| ISO/IEC 27701:2025 | A.1.4.4 | Accuracy & quality | Privacy by design / default |
| ISO/IEC 27701:2025 | A.1.4.5 | PII minimization objectives | Privacy by design / default |
| ISO/IEC 27701:2025 | A.1.4.10 | PII transmission controls | Privacy by design / default |
| ISO/IEC 27701:2025 | A.1.5.3 | Countries to which PII transferred | PII sharing, transfer & disclosure |
| ISO/IEC 27701:2025 | A.1.5.5 | Records of disclosures | PII sharing, transfer & disclosure |
| ISO/IEC 27701:2025 | A.2.2.3 | Organization's purposes | Conditions for collection and processing (processors) |
| ISO/IEC 27701:2025 | A.2.2.4 | Marketing & advertising use | Conditions for collection and processing (processors) |
| ISO/IEC 27701:2025 | A.2.4.4 | PII transmission controls | Privacy by design / default (processors) |
| ISO/IEC 27701:2025 | A.2.5.3 | Countries to which PII transferred | PII sharing, transfer & disclosure (processors) |
| ISO/IEC 27701:2025 | A.2.5.4 | Records of PII disclosures | PII sharing, transfer & disclosure (processors) |
| ISO/IEC 27701:2025 | A.2.5.5 | Notification of requests | PII sharing, transfer & disclosure (processors) |
| ISO/IEC 27701:2025 | A.2.5.7 | Disclosure of subcontractors | PII sharing, transfer & disclosure (processors) |
| ISO/IEC 27701:2025 | A.3.3 | Information security policies | Security considerations (controllers/processors) |
| ISO/IEC 27701:2025 | A.3.7 | Information transfer | Security considerations |
| ISO/IEC 27701:2025 | A.3.9 | Access rights | Security considerations |
| ISO/IEC 27701:2025 | A.3.14 | Protection of records | Security considerations |
| ISO/IEC 27701:2025 | A.3.22 | User endpoint devices | Security considerations |
| ISO/IEC 27701:2025 | A.3.24 | Information backup | Security considerations |
| ISO/IEC 27701:2025 | A.3.25 | Logging | Security considerations |
| ISO/IEC 27701:2025 | A.3.26 | Use of cryptography | Security considerations |
| ISO/IEC 27701:2025 | A.3.29 | Secure system architecture | Security considerations |
| ISO/IEC 27701:2025 | A.3.30 | Outsourced development | Security considerations |
| ISO/IEC 27701:2025 | A.3.31 | Test information | Security considerations |
36 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.