SOC 2 P6.3: unauthorized disclosures, explained for startups
What P6.3 asks you to show about unauthorized disclosures, and what proves it.

When personal information is shared without authorization, whether by mistake or in a breach, you record it. The record captures what happened, what data and whose. It feeds your incident and notification process.1
P6.3 belongs to Privacy, an optional category: it is in your report only when you add Privacy to the scope.
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 P6.3, the usual records are these.
- An incident log that flags personal data
- Breach records with affected data and people
- Investigation notes
What Polara asks about it
The free readiness assessment asks one question that bear on P6.3. 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 have a written procedure for telling affected people and regulators about a breach of personal information, and a record of every breach? If yes, show it: written breach notification procedure, a breach register, notification letter templates, or an incident record showing the notification decision. If no, the fix: write a breach notification procedure that names who decides, the deadlines that apply and how notice is given, and keep a breach register.
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 P6.3.
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.
Disclosure and notification: the criteria around it
P6.3 is one of 7 criteria in disclosure and notification, P6.1 to P6.7. Reading a group together shows how its outcomes fit, and one record often serves more than one of them.
- P6.1, third party disclosures
- P6.2, disclosure records
- P6.3, this page
- P6.4, processor commitments
- P6.5, processor breach notice
- P6.6, breach notification
- P6.7, disclosure reports
Before it: P6.2, disclosure records. After it: P6.4, processor commitments. All the criteria, Security first, are on the Trust Services Criteria page, grouped by category.
Questions
What does SOC 2 P6.3 ask a startup to show?
Is P6.3 required in every SOC 2 report?
Sources
Get audit-ready without a compliance team.
The readiness assessment is free, with no payment and no card. Star is $2,000 one time to get on the platform and close your gaps. Orbit is $7,800 a year, and your SOC 2 Type 2 audit is included in every contract year. You can be audit-ready starting at about a week.
Take the free assessmentPolara Labs is not a CPA firm. SOC 2 examinations are performed by independent licensed U.S. CPA firms.