Organizations may collect consumer PI for many purposes and may disclose information to service providers, affiliates, business partners and government agencies for a wide range of purposes.
Perception of acceptable privacy practices vary, creating challenges for privacy professionals
“Privacy Fundamentalists”
“Privacy Unconcerned”
“Privacy Pragmatists”
One role for privacy professionals is to alert their organizations to these often divergent perspectives.
Privacy professionals also help their organization manage a range of risks that can arise from processing personal information, and do so in a manner consistent with meeting the organization’s growth, profitability and other goals.
Legal Risks
Comply with applicable state, federal, and international laws regarding the use of information or potentially face litigation or regulatory sanctions such as consent decrees.
Comply with its contractual commitments, privacy promises and commitments to follow industry standards, such as Payment Card Data Security Standard (PCI DSS).
Reputational Risks
Reputational harm if you announce privacy policies but does not carry them out. You may also face enforcement actions – from FTC.
Operational Risks –
Must ensure that your privacy program is administratively efficient. If its too heavy-handed, it may interfere with relationships and inhibit uses of PI that benefit the organization and its customers, such as for personalization or risk management.
Investment Risks –
Must be able to receive an appropriate return on its investments in information, IT and information-processing programs in light of evolving privacy regulations, enforcement and expectations.
Privacy leaders help their organizations develop privacy policies in an organized way, meeting goals as as well as preserving business flexibility.
Discover
Issue identification and self-assessment
Learn privacy regulations for your organization
Understand the company's privacy risk posture.
Determination of best practices
Sample Organization Chart for Privacy and Data Protection Activities
Build
Procedure development and verification
When developing procedures, verify with those who will implement
Full implementation
Communicate
Documentation
Ensure properly documented to those in the organization
Education
Evolve
Affirmation and monitoring
Adaptation
Data Inventory
Organization’s inventory (collect, store, use, disclose) should include both customer and employee data records. It should document data location and flow as well as evaluate how, when and with whom the organization shares such information – and the means for data transfer used.
This is legally required for some institutions, such as those covered by the Gramm-Leach-Bliley Act (GLBA) Safeguard Rule.
Review and update it on a regular basis
Data Classification
Classify data according to its level of sensitivity.
Level defines the clearance of individuals who can access or handle that data.
Why classify - for the purpose of meeting compliance
Document Data Flows
Use Org Chart to document flows
Document the mapping of systems, applications and processes for handling data
Determining Data Accountability
Data flows should be examined and documented.
How sensitive is the information
Should the information be encrypted.
Will the information be transferred to or from other countries and how will it be transferred?
Who determines the rules that apply to the information.
Where, how, and for what length of time is the data stored.
How is the information to be processed, and how will these processes be maintained?
Is the use of such data dependent upon other systems?
Documenting data flows helps identify areas for compliance attention.
How they inform relevant employees about how PI must be handled, and in some cases made public, in the form of a privacy notice for the purpose of transparency.
If a promise made in privacy policy is violated, FTC/state attorney general may bring enforcement action for deceptive practice.
Decision:
One or Multiple Privacy Policy
One
One policy will work if an organization has a consistent set of values and practices for all its operations.
Multiple
Multiple policies may make sense for a company that has well-defined divisions of lines of business, especially if each division uses customer data in very different ways, does not typically share PI with other divisions, and is perceived in the marketplace as a different business.
Policy Review and Approval
Approval from the legal and executive team
Communication of Privacy Policy Through Notice
Make the notice accessible online
Make the notice accessible in place of business
Provide updates and revisions
Ensure that the appropriate personnel are knowledgeable about the policy.
Policy Version Control
An organization’s privacy policy will need to be updated as its information collection, use and transfer needs evolve.
Opt-in, Opt-out, and No Option
Opt-in – Some US privacy laws require affirmative consumer consent (opt-in) before data collection.
COPPA express from parents. COPPA requires express consent from a parent before a child’s PI is collected.
HIPAA before disclosure to 3rd parties, with exceptions.
HIPAA requires opt-in consent before personal health information is disclosed to third parties, subject to important exceptions.
FCRA before credit report may be provided to employer, lender or other authorized recipient.
Fair Credit Reporting Act (FCRA) requires opt-in before a consumer’s credit report may be provided to an employer, lender or other authorized recipient.
No Consumer Choice / No Option – implied authority to share
Amazon customer expects PI to be shared with shipper, credit card processors, and others for delivery fulfillment.
Commonly Accepted Practices
Opt-Out / Consumer Choice – creates an enforceable promise.
FTC/state enforcers may bring suit under unfair/deceptive practice.
GLBA requires opt-out before transferring PI of of financial institution customers to unaffiliated 3rd party for latter’s own use.
Video Privacy Protection Act requires opt-out before movie and other rental data is provided to 3rd party.
CAN SPAM email marketers must provide opt out.
DO NOT CALL rules provide the opportunity to opt out of telemarketing phone calls, both in general or on a company-by-company basis.
Opt out is required for companies that subscribe to any of a number of self-regulatory systems.
Managing User Preference (challenges)
Scope of user preference can vary.
Mechanism can vary (rule of thumb is how you market user preference should be same – opt out through email not phone/mail)
Linking a user’s interaction through multiple channels (person, phone/ email / web)
Good practice is for the organization to implement the opt-out or other user preference across channels and platforms.
Time period for implementing user preference is sometimes provided by law.
CAN-SPAM Act and Telemarketing Sales Rules mandate specific time periods for processing customer preferences
3rd Party Vendors often process PI on behalf of the company that has the customer relationship.
Customer Access and Redress
FCRA – individuals have the right to access their credit reports under FCRA and rectify incorrect data.
HIPAA – medical records - Patients can access their medical records under HIPAA, with records that the patient believes are incorrect noted as such in the patient files
OECD / APEC / EU-US Shield – Access in included in statements of fair information practices
Vendor Contracts
Confidentiality provision
No further use of shared information
Use of subcontractors-
If vendor intends to use subcontractors in the collection, use, or processing of personal information, the contractor organization should require all subcontractors to follow the privacy and security protection terms in the vendor’s contract
Requirement to notify and to disclose breach
Information security provisions
Contracts may include provisions concerning specific security controls; encryption of data in transit, on media and on portable devices; network security; access controls; segregation of data; employee background checks; audit rights
Vendor Due Diligence
Reputation
Financial condition and insurance
The vendor should have sufficient resources in the case of a security breach and subsequent litigation.
A current and sufficient insurance policy can protect the procuring organization in the event of a breach.
Information security controls
Point of transfer
point of transfer between the procuring organization and the vendor is a potential security vulnerability.
Disposal of information
Employee training and user awareness -
a vendor should have an established system for training its employees about its responsibilities in managing personal or sensitive information.
Vendor incident response
Audit rights
Organizations should be able to monitor the vendor’s activities to ensure it is complying with contractual obligations.
General Data Protection Regulation (GDPR)
applies to companies with assets and employees in the EU, sell to EU residence, and data that is stored in EU.
Key provisions
Notification of security breach
New requirements for processors (contractors who act on behalf of data controllers)
Designation of data protection officers (DPO requirement)
Accountability obligations
Rule for international transfers
Sanctions of up to 4% of worldwide revenues
GDPR provides extensions of individual rights, including the right to be forgotten, the right to data portability, and implementation of principles of data protection by design and data protection by default.
Privacy Shield and Other Lawful Bases for Data Transfer
Data Transfer from EU to States was US-EU Safe Harbor Program, now:
Privacy Shield Framework
Standard Contract Clauses (SCC)
Company contractually promises to comply with EU law and submit to the supervision of an EU privacy supervisor agency.
Binding Corporate Rules (BCR)
Multinational company can transfer data between countries after certification of its practices by an EU privacy supervisory agency.