SOC 2 (2017 TSC) P2.1 — Communication of Data Subject Choices and Consequences

What this control requires

The entity communicates choices available regarding the collection, use, retention, disclosure, and disposal of personal information to the data subjects and the consequences, if any, of each choice. Explicit consent for the collection, use, retention, disclosure, and disposal of personal information is obtained from data subjects or other authorized persons, if required. Such consent is obtained only for the intended purpose of the information to meet the entity's objectives related to privacy. The entity's basis for determining implicit consent for the collection, use, retention, disclosure, and disposal of personal information is documented.

In plain English

The entity communicates choices available regarding the collection, use, retention, disclosure, and disposal of personal information to the data subjects and the consequences, if any, of each choice. In practice, this means you can prove you information objectives-level controls on a defined cadence.

Why it matters

Every SOC 2 audit opinion is built control-by-control from the Trust Services Criteria. A missing or failing criterion produces an exception in the report, which buyers, partners and procurement teams read line-by-line during vendor reviews.

This control is rated high. Auditors expect a named owner, a remediation SLA, and a tooling artefact that evidences continuous operation.

What an auditor looks for

A SOC 2 auditor (under AT-C §§ 105/205) tests both design and operating effectiveness over the audit window. For each criterion they expect a written control, a control owner, a population of events, and a sample tested against the population — including remediation tickets for exceptions.

Within Privacy, the assessor will trace your implementation back to the catalogue reference (Criterion P2.1) and look for objective evidence on the latest two assessment cycles.

How to implement

Policy Management

Docs. Keep each policy in version-controlled Markdown alongside the code that implements it; ship a signed PDF snapshot at each annual review and link the SHA into the SoA.

Operational checklist

• Information. Document the trigger, the owner and the cadence.
• Risk. Document the trigger, the owner and the cadence.
• Management. Document the trigger, the owner and the cadence.
• Privacy. Document the trigger, the owner and the cadence.
• Communication. Document the trigger, the owner and the cadence.
• Scope: objectives, disposal, protection, management.

Evidence to collect

• Policy Document. A signed and version-controlled policy / standard / procedure document.

Signed policy or standard documents the safeguard. Focus: Communication of Data Subject Choices and Consequences (Original component: Privacy).

Common pitfalls

• Policies that no engineer has read; the version in Confluence drifts from the version that's actually being enforced.

How it maps to other frameworks

Computed from shared tags, control component and key-operation subjects — handy when you are reconciling controls across an audit.

• India DPDP Act 2023 LB-001 — Consent Quality & Management
• NIST SP 800-53 Rev. 5 CM-13 — Data Action Mapping
• GDPR Article 1 — Subject-matter and objectives
• NIST SP 800-171 Rev. 3 3.13.15 — Session Authenticity
• ISO/IEC 27701:2025 A.1.3.2 — Comply with obligations

Related controls in SOC 2 (2017 TSC)

• Criterion P4.2 — Personal Information Retention Aligned with Privacy Objectives
• Criterion P1.1 — Privacy Notice to Data Subjects
• Criterion P6.2 — Recordkeeping of Authorized Personal Information Disclosures
• Criterion P3.1 — Personal Information Collection Aligned with Privacy Objectives
• Criterion P4.3 — Secure Disposal of Personal Information
• Criterion P3.2 — Consent Management for Personal Information Collection

References

• AICPA / ASEC — SOC 2 (2017 TSC)
• Catalogue identifier: Criterion P2.1

Topics: governance riskdata protectionprivacy managementlogging retentionpolicy management