# Compliance Policy - Source: https://support.icompaas.com/compliance/policy-docs/compliance-policy - Section: [Compliance](https://support.icompaas.com/compliance) › [Policy Documents](https://support.icompaas.com/compliance/policy-docs) › All policy documents - Last updated: 2026-06-05 - Publisher: iCompaas, Inc. (https://www.icompaas.com) **Policy Document**·14 mapped controls ## What this policy is States the organization's commitment to comply with applicable laws, regulations, contractual obligations, and industry standards — and defines how compliance status is tracked and reported. ## Why every organization needs one Boards and large customers expect a documented compliance posture. The policy is the artefact that makes that posture defensible. ## What a competent Compliance Policy typically contains - Purpose and scope - Roles and responsibilities - Definitions - Applicable-obligation register ownership - Compliance-monitoring cadence - Non-compliance escalation path - External-reporting obligations - 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_compliance_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](https://support.icompaas.com/compliance) 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.6](https://support.icompaas.com/compliance/iso-27001-2022/a-5-6-contact-with-special-interest-groups) | [Contact with special interest groups](https://support.icompaas.com/compliance/iso-27001-2022/a-5-6-contact-with-special-interest-groups) | Organizational controls | | ISO/IEC 27001:2022 | [A.5.31](https://support.icompaas.com/compliance/iso-27001-2022/a-5-31-legal-statutory-regulatory-and-contractual-requirements) | [Legal, statutory, regulatory and contractual requirements](https://support.icompaas.com/compliance/iso-27001-2022/a-5-31-legal-statutory-regulatory-and-contractual-requirements) | Organizational controls | | ISO/IEC 27001:2022 | [A.5.36](https://support.icompaas.com/compliance/iso-27001-2022/a-5-36-compliance-with-policies-rules-and-standards-for-information-security) | [Compliance with policies, rules and standards for information security](https://support.icompaas.com/compliance/iso-27001-2022/a-5-36-compliance-with-policies-rules-and-standards-for-information-security) | Organizational controls | | ISO/IEC 27701:2025 | [A.1.3.2](https://support.icompaas.com/compliance/iso-27701-2025/a-1-3-2-comply-with-obligations) | [Comply with obligations](https://support.icompaas.com/compliance/iso-27701-2025/a-1-3-2-comply-with-obligations) | Obligations to PII principals | | ISO/IEC 27701:2025 | [A.1.4.3](https://support.icompaas.com/compliance/iso-27701-2025/a-1-4-3-limit-processing) | [Limit processing](https://support.icompaas.com/compliance/iso-27701-2025/a-1-4-3-limit-processing) | Privacy by design / default | | ISO/IEC 27701:2025 | [A.1.4.8](https://support.icompaas.com/compliance/iso-27701-2025/a-1-4-8-retention-schedule) | [Retention schedule](https://support.icompaas.com/compliance/iso-27701-2025/a-1-4-8-retention-schedule) | Privacy by design / default | | ISO/IEC 27701:2025 | [A.1.5.2](https://support.icompaas.com/compliance/iso-27701-2025/a-1-5-2-basis-for-transfer) | [Basis for transfer](https://support.icompaas.com/compliance/iso-27701-2025/a-1-5-2-basis-for-transfer) | PII sharing, transfer & disclosure | | ISO/IEC 27701:2025 | [A.2.2.6](https://support.icompaas.com/compliance/iso-27701-2025/a-2-2-6-customer-obligations) | [Customer obligations](https://support.icompaas.com/compliance/iso-27701-2025/a-2-2-6-customer-obligations) | Conditions for collection and processing (processors) | | ISO/IEC 27701:2025 | [A.2.2.7](https://support.icompaas.com/compliance/iso-27701-2025/a-2-2-7-records-related-to-processing-pii) | [Records related to processing PII](https://support.icompaas.com/compliance/iso-27701-2025/a-2-2-7-records-related-to-processing-pii) | Conditions for collection and processing (processors) | | ISO/IEC 27701:2025 | [A.2.5.4](https://support.icompaas.com/compliance/iso-27701-2025/a-2-5-4-records-of-pii-disclosures) | [Records of PII disclosures](https://support.icompaas.com/compliance/iso-27701-2025/a-2-5-4-records-of-pii-disclosures) | PII sharing, transfer & disclosure (processors) | | ISO/IEC 27701:2025 | [A.2.5.6](https://support.icompaas.com/compliance/iso-27701-2025/a-2-5-6-legally-binding-disclosures) | [Legally binding disclosures](https://support.icompaas.com/compliance/iso-27701-2025/a-2-5-6-legally-binding-disclosures) | PII sharing, transfer & disclosure (processors) | | ISO/IEC 27701:2025 | [A.2.5.7](https://support.icompaas.com/compliance/iso-27701-2025/a-2-5-7-disclosure-of-subcontractors) | [Disclosure of subcontractors](https://support.icompaas.com/compliance/iso-27701-2025/a-2-5-7-disclosure-of-subcontractors) | PII sharing, transfer & disclosure (processors) | | ISO/IEC 27701:2025 | [A.2.5.8](https://support.icompaas.com/compliance/iso-27701-2025/a-2-5-8-engagement-of-subcontractor) | [Engagement of subcontractor](https://support.icompaas.com/compliance/iso-27701-2025/a-2-5-8-engagement-of-subcontractor) | PII sharing, transfer & disclosure (processors) | | ISO/IEC 27701:2025 | [A.3.13](https://support.icompaas.com/compliance/iso-27701-2025/a-3-13-legal-statutory-regulatory-contractual-reqs) | [Legal, statutory, regulatory & contractual reqs](https://support.icompaas.com/compliance/iso-27701-2025/a-3-13-legal-statutory-regulatory-contractual-reqs) | Security considerations | 14 controls across 2 frameworks reference this policy. ## About this page This article is part of the iCompaas [Policy Documents](https://support.icompaas.com/compliance/policy-docs) 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. ## Related compliance guidance - [SOC 2 compliance: a practical implementation guide for cloud-native SaaS teams](https://support.icompaas.com/compliance/soc-2-trust-services-criteria): SOC 2 auditors test that policies like this one exist, are approved, and are reviewed on schedule; the guide lists the full set. - [ISO/IEC 27001:2022 compliance: a practical implementation guide](https://support.icompaas.com/compliance/iso-27001-2022): ISO 27001 clause 5.2 and Annex A.5.1 require a documented, approved policy set; the guide shows how it fits the ISMS.