Skip to main content

SOC2 Privacy (P) - Privacy Procedures

Control: Privacy Trust Service Criteria Status: Procedure template Last Updated: 2025-12-16 Owner: Privacy Officer / Data Protection Officer


Overview​

This document defines privacy procedures for organizations using CloudForge CI that have elected to include the Privacy category in their SOC2 examination. These procedures address the collection, use, retention, disclosure, and disposal of personal information. These procedures are a template for addressing SOC2 Privacy (P) requirements.


P1 - Notice and Communication of Objectives​

P1.1 - Privacy Notice​

Privacy Notice Requirements​

Organizations must provide privacy notices that include:

ElementDescriptionLocation
Data CollectedTypes of personal information collectedPrivacy Policy
Collection MethodsHow data is collected (forms, cookies, APIs)Privacy Policy
PurposeWhy data is collected and how it's usedPrivacy Policy
Third PartiesDisclosure to third partiesPrivacy Policy
RetentionHow long data is retainedPrivacy Policy
RightsIndividual rights (access, correction, deletion)Privacy Policy
ContactHow to contact for privacy inquiriesPrivacy Policy

Privacy Notice Template​

PRIVACY NOTICE
==============

INFORMATION WE COLLECT
----------------------
We collect the following types of personal information:
- Contact information (name, email, phone)
- Account credentials
- Usage data and analytics
- [Additional categories specific to application]

HOW WE USE YOUR INFORMATION
---------------------------
We use your information to:
- Provide and improve our services
- Communicate with you
- Comply with legal obligations
- [Additional purposes]

DATA SHARING
------------
We may share your information with:
- Service providers who assist our operations
- Legal authorities when required by law
- [Additional sharing scenarios]

DATA RETENTION
--------------
We retain your personal information for:
- Active accounts: Duration of account plus [X] years
- Inactive accounts: [X] years after last activity
- Legal requirements: As required by applicable law

YOUR RIGHTS
-----------
You have the right to:
- Access your personal information
- Correct inaccurate information
- Request deletion of your information
- Opt-out of marketing communications
- Data portability

CONTACT US
----------
Privacy inquiries: privacy@[company].com
Data Protection Officer: dpo@[company].com

Data TypeConsent TypeMechanism
Essential DataImplied (contractual necessity)Terms of Service
MarketingExplicit opt-inCheckbox (unchecked by default)
AnalyticsOpt-out availableCookie banner
Sensitive DataExplicit opt-inSeparate consent form
Third-Party SharingExplicit opt-inCheckbox with disclosure
# Example: Cognito user pool with consent attributes
# Note: Cognito custom attributes only support String, Number, DateTime (not Boolean)
UserPool:
Type: AWS::Cognito::UserPool
Properties:
Schema:
- Name: marketing_consent
AttributeDataType: String
Mutable: true
StringAttributeConstraints:
MinLength: "4"
MaxLength: "5"
- Name: analytics_consent
AttributeDataType: String
Mutable: true
StringAttributeConstraints:
MinLength: "4"
MaxLength: "5"
- Name: consent_timestamp
AttributeDataType: String
Mutable: true
# Values stored as "true" or "false" strings
FieldDescriptionRetention
User IDUnique identifierDuration of consent
Consent TypeWhat was consented toDuration of consent
Consent StatusGranted/WithdrawnDuration of consent
TimestampWhen consent was given/withdrawnDuration of consent
MethodHow consent was obtainedDuration of consent
VersionPrivacy policy version at consent timeDuration of consent

P3 - Collection​

P3.1 - Data Collection Principles​

Data Minimization​

PrincipleImplementation
Collect only what's neededReview data fields annually
Purpose limitationDocument purpose for each field
Storage limitationImplement retention policies
AccuracyProvide user correction mechanisms

Personal Data Inventory​

Data CategoryExamplesPurposeLegal BasisRetention
IdentityName, DOB, ID numbersAccount managementContractAccount lifetime
ContactEmail, phone, addressCommunicationContractAccount lifetime
FinancialPayment card, bank accountBillingContract7 years
TechnicalIP address, device IDSecurity, analyticsLegitimate interest90 days
UsageActivity logs, preferencesService improvementLegitimate interest1 year

P4 - Use, Retention, and Disposal​

P4.1 - Data Use Limitations​

Permitted Uses​

Use CategoryDescriptionRequires Additional Consent
Primary PurposeService deliveryNo
SecurityFraud prevention, threat detectionNo
Legal ComplianceRegulatory requirementsNo
MarketingPromotional communicationsYes
AnalyticsProduct improvementDepends on jurisdiction
Third-Party SharingPartner integrationsYes

P4.2 - Data Retention Schedule​

Data TypeActive RetentionArchive RetentionDisposal Method
User AccountsAccount lifetime3 years post-closureSecure deletion
Transaction Records1 year7 yearsSecure deletion
Support Tickets2 years5 yearsSecure deletion
Audit Logs1 year7 yearsSecure deletion
Marketing DataConsent durationNoneImmediate deletion
Analytics90 days1 year (aggregated)Secure deletion

P4.3 - CloudForge CI Retention Implementation​

# S3 Bucket with Lifecycle Policy for PII
PIIBucket:
Type: AWS::S3::Bucket
Properties:
BucketName: !Sub "${AWS::StackName}-pii-data"
BucketEncryption:
ServerSideEncryptionConfiguration:
- ServerSideEncryptionByDefault:
SSEAlgorithm: aws:kms
KMSMasterKeyID: !Ref DataEncryptionKey
LifecycleConfiguration:
Rules:
- Id: PIIRetention
Status: Enabled
Transitions:
- StorageClass: GLACIER
TransitionInDays: 365
ExpirationInDays: 2555 # 7 years
NoncurrentVersionExpiration:
NoncurrentDays: 90

# RDS with Backup Retention
Database:
Type: AWS::RDS::DBInstance
Properties:
DBInstanceClass: db.t3.medium
Engine: postgres
BackupRetentionPeriod: 35
DeleteAutomatedBackups: true
StorageEncrypted: true
KmsKeyId: !Ref DataEncryptionKey

P4.4 - Data Disposal Procedures​

See SOC2_C1.2_DATA_DISPOSAL_PROCEDURES.md for detailed disposal procedures.


P5 - Access​

P5.1 - Individual Access Rights​

Access Request Process​

┌─────────────────┐ ┌─────────────────┐ ┌─────────────────┐
│ Request │────>│ Identity │────>│ Data │
│ Received │ │ Verification │ │ Compilation │
└─────────────────┘ └─────────────────┘ └─────────────────┘
│
┌─────────────────┐ ┌─────────────────┐ │
│ Request │<────│ Response │<───────────┘
│ Closed │ │ Delivery │
└─────────────────┘ └─────────────────┘

Response Timelines​

JurisdictionResponse DeadlineExtension Available
GDPR (EU)30 days+60 days with notification
CCPA (California)45 days+45 days with notification
Default30 daysCase-by-case

Data Subject Request Template​

DATA SUBJECT ACCESS REQUEST RESPONSE
====================================
Request ID: [ID]
Date Received: [Date]
Response Date: [Date]
Requestor: [Name/Email]

IDENTITY VERIFICATION
---------------------
Method: [Email verification / ID document / Account login]
Verified: [Yes/No]
Verified By: [Name]

DATA PROVIDED
-------------
Category: [Identity Data]
- Name: [Value]
- Email: [Value]
- [Additional fields]

Category: [Usage Data]
- Last login: [Value]
- [Additional fields]

PROCESSING ACTIVITIES
---------------------
Your data is processed for:
1. [Purpose]
2. [Purpose]

THIRD-PARTY DISCLOSURES
-----------------------
Your data has been shared with:
- [Third party] for [purpose]

If you have questions about this response, contact: privacy@[company].com

P6 - Disclosure and Notification​

P6.1 - Third-Party Disclosure​

Third-Party Data Sharing Registry​

Third PartyData SharedPurposeSafeguardsAgreement
AWSAll infrastructure dataHostingBAA, DPAIn place
[Payment Processor]Payment dataBillingPCI-DSSIn place
[Analytics Provider]Usage dataAnalyticsDPAIn place
[Support Tool]Support ticketsCustomer supportDPAIn place

Due Diligence Requirements​

RequirementVerification
Security AssessmentSOC2 report or security questionnaire
Data Processing AgreementSigned DPA with privacy clauses
Sub-processor ListDocumented and reviewed
Breach NotificationContractual obligation to notify
Audit RightsRight to audit security controls

P6.2 - Breach Notification​

Notification Requirements by Jurisdiction​

JurisdictionAuthority NotificationIndividual NotificationTimeline
GDPRRequired (supervisory authority)If high risk to individuals72 hours
CCPANot requiredRequired if unencrypted PIWithout unreasonable delay
HIPAARequired (HHS)Required60 days
DefaultAs requiredIf risk of harm72 hours

P7 - Quality​

P7.1 - Data Accuracy​

Data Quality Controls​

ControlImplementationFrequency
User Self-ServiceProfile update capabilityContinuous
Validation RulesInput validation on formsReal-time
Duplicate DetectionAutomated matchingDaily
Decay ManagementEmail verification, re-confirmationAnnual

Correction Request Process​

  1. User submits correction request
  2. Verify user identity
  3. Validate correction request
  4. Update records
  5. Notify user of completion
  6. Update downstream systems

P8 - Monitoring and Enforcement​

P8.1 - Privacy Compliance Monitoring​

Monitoring Activities​

ActivityFrequencyOwner
Privacy Impact AssessmentPer new projectPrivacy Officer
Data Inventory ReviewQuarterlyPrivacy Officer
Consent AuditQuarterlyPrivacy Officer
Third-Party ReviewAnnualProcurement/Privacy
Policy ReviewAnnualPrivacy Officer
Training CompletionAnnualHR/Privacy

P8.2 - Privacy Training​

Training Requirements​

AudienceTrainingFrequency
All StaffPrivacy awarenessAnnual
DevelopmentPrivacy by designAnnual
Customer SupportData subject requestsAnnual
MarketingConsent and preferencesAnnual
LeadershipPrivacy governanceAnnual

CloudForge CI Privacy Controls​

ControlImplementationSOC2 Privacy Mapping
Encryption at RestKMS encryption for all data storesP4.3
Encryption in TransitTLS 1.2+ enforcedP4.3
Access LoggingCloudTrail for all API accessP5.2
Data IsolationVPC isolation, security groupsP4.1
Backup EncryptionEncrypted backups with KMSP4.3
Retention PoliciesS3 lifecycle, RDS retentionP4.2

Audit Checklist​

  • Privacy notice published and current
  • Consent mechanisms implemented and documented
  • Personal data inventory maintained
  • Retention schedules documented and automated
  • Data subject request process operational
  • Third-party agreements include privacy clauses
  • Breach notification procedures documented
  • Privacy training completed by all staff
  • Privacy impact assessments conducted for new projects
  • Privacy policy reviewed annually