2: Privacy Program Framework: Privacy Governance Flashcards
Components of “Privacy Governance” (5)
- create org privacy vision and mission statement
- define the scope of the privacy program
- select appropriate privacy framework
- develop the organizational privacy strategy
- structure the privacy team
What does a Privacy Vision and Mission Statement do?
- lays the groundwork for the rest of the privacy program.
- the vision should align with the organization’s broader purpose and objectives
Privacy Program Scope
- organizational legal and regulatory compliance obligations
1. identify the PI collected & processed
2. identify the privacy and data protection laws and regulations
Things to consider about PI collected and processed
- who collects, uses and discloses/maintains PI?
- what type of PI
- reasons for collection
- data storage
- transferred to whom
- access
- when is the data collected
- storage/retention
- security protocols to protect
What if data is cross-jurisdictional?
use the most restrictive regulations
Scope challenges
Consider:
- domestic laws
- state/regional laws
- industry specific
- global differences and approaches
US vs EU Privacy Protection approaches
US - limited sectoral approach, laws apply to specific industry sectors or categories of data, or to specific states
EU - more comprehensive approach that applies to all personal data, regardless of sector or location
Protection Models (4)
Sectoral laws/state specific (US) Comprehensive laws (EU) Co-regulatory model (AUS) Self-regulated model (US, Japan, Singapore)
Sectoral/State specific laws
Laws that specifically address a particular industry sector, or apply to residents of a specific state
US
Comprehensive laws
Apply to the collection, use and disclosure of PI in public and private sectors with an official oversight agency (to review concerns and provide guidance to businesses and individuals)
EU, CAN, UK
Co-regulatory Model
Similar to comprehensive model, industry develops enforcement standards that are overseen by privacy agency
AUS
Self-regulated Model
Companies use a code of practice by an industry body, i.e. OPA, TrustArc, WebTrust, PCI DSS (some states have adopted as law)
US, Japan, Singapore
Privacy Program Scope requires:
- end to end of data lifecycle
- considerations to meet legal, cultural, and personal expectations
- customize approach from global and local perspective
- aware of privacy challenges, incl laws/regs and enforcement activities and processes
- monitoring for compliance
Developing a Privacy Strategy
Need organizational support to implement and for accountability, every individual contributes.
Identify stakeholders and internal partnerships.
Privacy Strategy - challenges
gaining consensus from organization management, look for privacy sponsors / champions for support.
Privacy Champions
A privacy champion at the executive level acts as an advocate and sponsor to further foster privacy as a core organization concept.
- keep champions informed so the can advocate and privacy becomes embedded
Best Practices for Internal Partnerships?
- how do others treat and view PI?
- use of data in their business context
- build privacy requirements into their ongoing projects to help reduce risk
- offer to help meet objectives with solutions to reduce risk
- invite staff to a privacy advocate group
Stakeholder Privacy Workshop
Conduct a privacy workshop for stakeholders to level the privacy playing field by defining privacy for the organization, explaining the market expectations, answering questions, and reducing confusion.
Program Ownership
- ensure clear ownership of assets and responsibilities
- record using agendas, minutes and actions (also helps with audits and accountability requirements)
Develop and Implement Framework
manageable approach to operationalizing the controls to protect and handle PI
- reach compliance
- competitive advantage, engendering trust
- support business commitment and objectives