SOC 2 P3.2: explicit consent, explained for startups

What usually proves it

An auditor wants records from the period being examined, pulled from the systems that hold them rather than written up afterwards. Dates matter. A record with a date and a named owner carries more weight than a screenshot with neither. For P3.2, the usual records are these.

• Explicit consent screens
• Consent records with timestamps
• A list of data types that need explicit consent

What Polara asks about it

The free readiness assessment asks one question that bear on P3.2. A yes becomes a task to show the proof. A no becomes a task to fix the gap, with the steps written out.

• Do you collect only the personal information your stated purposes need, and get explicit consent before collecting sensitive information? If yes, show it: a design review recording why each personal field is needed, a sign up form with only required fields, or an explicit consent screen for sensitive information. If no, the fix: review each form and data feed against the purposes in your notice, remove fields you do not need, and require explicit consent for sensitive information.

Policies, templates and connected evidence

A policy states the rule, a template gives you the record to keep, and a connected system pulls the proof from the source. An auditor checks that the three agree: the cadence in the policy, the dates in the record and what the system shows.

In the policy pack, the Privacy Program Policy covers P3.2.

Is it in your scope?

Only if you add Privacy. How you handle personal information across its life: notice, consent, collection, use, retention, access requests, disclosure and complaints. It is the heaviest category and assumes a privacy program already runs.

The scoping tool decides it with one question: Add it when you collect personal information about individuals and run a privacy program with a notice, consent and requests from the people it describes. When personal information is incidental to your service, Confidentiality is often the closer fit. Privacy notice, consent, collection and use limits, retention and deletion, access and correction requests, disclosures, breach notification and complaints.

Security is the default and always in scope. Adding Privacy in the assessment puts its 18 criteria into the report and the examination, and adds 14 questions to the assessment.

Polara Labs is not a CPA firm. SOC 2 examinations are performed by independent licensed U.S. CPA firms.

Collection: the criteria around it

P3.2 is one of 2 criteria in collection, P3.1 to P3.2. Reading a group together shows how its outcomes fit, and one record often serves more than one of them.

• P3.1, collection limits
• P3.2, this page

Before it: P3.1, collection limits. After it: P4.1, use limits. All the criteria, Security first, are on the Trust Services Criteria page, grouped by category.