SOC 2 Confidentiality and Privacy Evidence — Data Flows, Access, Retention and Disposal
A customer record can pass through a production database, support export, monitoring log and backup. Its handling may differ at each point. A privacy notice or retention policy needs to be considered alongside those actual flows.
For SOC 2 preparation, trace relevant information through the service and identify the commitments and responsibilities that affect it. Confidentiality and privacy concerns can intersect, but they should not be treated as interchangeable labels. The proposed category coverage and control arrangements need review in the context of the actual engagement.
Use the SOC 2 evidence checklist for general preparation. This article concentrates on a defined information lifecycle and the records that make it explainable.
Start with information and its use
Identify important information types, their origin and the purposes for which the service handles them. Record relevant confidentiality commitments and personal-information roles. Avoid assuming that the same responsibility applies to every dataset or customer relationship.
The NIST Privacy Framework provides a risk-management reference for considering privacy concerns. It is not a replacement for applicable legal analysis or the SOC 2 engagement criteria.
For an enquiry, a useful data-flow record identifies collection, processing, storage, access, transfer, retention and disposal. Include support tools and external providers where they materially affect the described service.
Follow one information lifecycle
|
Stage |
Record to connect |
Question to investigate |
|
Collection |
Source, purpose and relevant notice or agreement |
Is the actual use consistent with the stated arrangement? |
|
Processing |
Responsible functions, permissions and handling |
Who can use the information and for what activity? |
|
Transfer |
Recipient, purpose and relevant approval |
What responsibilities follow the information? |
|
Retention |
Policy basis and implemented settings |
Do different stores follow the intended arrangement? |
|
Deletion or return |
Request, action and verification |
What was completed and what limitations remain? |
This is an illustrative review record. It is not a universal retention schedule or a determination of legal compliance.
Separate confidentiality from personal-information duties
Confidential information can include commercial documents, credentials or business records as well as personal information. Personal-information handling may introduce further questions about roles, transparency, requests and processing responsibilities.
Record which commitments apply to each information type. Where the customer and provider have different responsibilities, show the interface and relevant agreements. Do not assume that all information held by the company is subject to identical handling requirements.
AICPA's Trust Services Criteria resource provides the relevant professional framework. Use the actual criteria and engagement scope rather than treating a policy title as proof of coverage.
Connect protection statements to operating records
If encryption or restricted access is part of the described arrangement, identify the systems, responsible roles and records supporting those statements. Explain key-management responsibilities, supplier involvement and relevant exceptions at the level needed for assessment.
Avoid placing secrets, full production datasets or unnecessary personal information in a general enquiry. Agree secure review arrangements and the minimum information needed to explain the control.
When a credential or confidential record appears in an inappropriate location, retain the relevant investigation and response. A cleaned repository alone may not explain exposure, affected access or management decisions.
Reconcile retention and disposal across systems
Compare policy expectations with production, support, log and backup arrangements. Explain where deletion, access restriction, retention or return activities differ and why. A deletion request should have an owner, relevant authority, action record and clear status.
Do not promise immediate deletion from every copy if that is inconsistent with actual architecture or obligations. Identify limitations and agreed treatment rather than hiding them behind a completed ticket.
For a privacy-related request, record receipt, verification, routing, decisions and completion under the organisation's applicable arrangements. The article sets no universal legal response deadline; jurisdiction and facts require separate review.
Review external sharing and cross-border flows
Describe the information sent to another provider, the service purpose and the relevant responsibilities. Check that the flow shown in the data map is consistent with operational practice and customer-facing information.
The location of a recipient does not alone determine whether the arrangement is acceptable. Identify applicable obligations and contractual conditions through the appropriate legal and business review. SOC 2 reporting does not itself authorise a transfer or replace those obligations.
An illustrative support-export discrepancy
A fictional Canadian SaaS supplier retains customer information in its main platform under a defined arrangement. A support team also exports selected records to investigate cases, but those exports are absent from the data map.
Management identifies the exports, evaluates access and retention, and records the decisions and actions. It updates the service information and checks whether relevant communications and provider arrangements need review. The original omission and follow-up remain visible to the assessment.
This example is not a legal conclusion or a client case. For country enquiry context, refer to the Canada SOC 2 guide.
Prepare a focused information-handling enquiry
Bring the service description, information-flow map, role allocation, relevant commitments and evidence status. Identify unresolved issues and where sensitive records can be reviewed securely.
If the customer separately requests a privacy management-system certificate, use the established ISO 27701 service page for that route. Keep its purpose distinct from a SOC 2 examination.
Contact SCS with the requirement and current arrangements to discuss the scope, requested support and independent reporting responsibilities.
Need ISO Certification for Your Business?
Speak with our certification specialists to understand certification requirements, audit process, implementation timelines and accredited certification services.