Study guide
9.3 Data Privacy, Confidentiality, and Access
PHR Study Guide Exam
Track your progress as you read
Finished sections get a check mark.
1 Orientation: PHR Eligibility, Format, Fees, Scoring, and Study Map
1.1 PHR Purpose and Operational Scope 1.2 Eligibility Pathways and Candidate Fit 1.3 Exam Format, Time, and Delivery 1.4 Fees, Refunds, and Application Planning 1.5 Scoring, Pass Rate, Retake, and Recertification 1.6 Seven-Domain Study Map
2 Business Management: HR Operations, Stakeholders, Culture, and Metrics
2.1 Business Management Domain Boundary 2.2 Organizational Context and Business Operations 2.3 Stakeholder Needs and HR Service Delivery 2.4 Culture, Values, and Ethics in HR Operations 2.5 Policies, Procedures, and Governance Controls 2.6 HR Metrics and Business Reporting
3 Workforce Planning, Job Analysis, Recruiting, Selection, and Onboarding
3.1 Operational Workforce Planning 3.2 Job Analysis and Job Documentation 3.3 Sourcing and Recruiting Pipeline 3.4 Screening, Interviewing, and Selection 3.5 Offers, Hiring, and Onboarding 3.6 Retention and Talent Acquisition Metrics
4 Learning and Development Needs Assessment, Training Design, and Evaluation
4.1 Training Needs Assessment 4.2 Learning Objectives and Instructional Design 4.3 Training Delivery and Implementation 4.4 Training Evaluation and Transfer 4.5 Career Development and Coaching 4.6 Succession Support and Capability Planning
5 Total Rewards: Compensation, Benefits, Leave, Pay Equity, and Recognition
5.1 Total Rewards Domain Scope and Answer Logic 5.2 Job Evaluation and Pay Structure Basics 5.3 Base Pay, Variable Pay, and Incentive Administration 5.4 Benefits Administration and ERISA Awareness 5.5 Leave Programs and Payroll-Adjacent Compliance 5.6 Pay Equity, Recognition, and Total Rewards Controls
6 Employee Engagement: Culture, Performance, Retention, and Wellbeing
6.1 Employee Engagement Domain Scope and Answer Logic 6.2 Culture, Values, and Workplace Climate 6.3 Engagement Surveys, Listening, and Action Planning 6.4 Performance Support, Feedback, and Coaching 6.5 Retention Drivers, Turnover, and Stay Conversations 6.6 Wellbeing, Recognition, and Sustainable Engagement
7 Employee Relations, Investigations, Discipline, Documentation, and Separations
7.1 Complaint Intake and Early Risk Triage 7.2 Investigation Planning and Neutral Fact-Finding 7.3 Documentation, Records, and Confidentiality 7.4 Corrective Action and Progressive Discipline 7.5 Grievance Handling, Conflict Resolution, and Employee Voice 7.6 Separations, Final Controls, and Retaliation Prevention
8 Labor Relations, NLRA, Collective Bargaining, and Workplace Rights
8.1 NLRA Foundations and Protected Concerted Activity 8.2 Organizing, Representation, and Election Readiness 8.3 Collective Bargaining Process and Good-Faith Conduct 8.4 Contract Administration, Management Rights, and Past Practice 8.5 Grievance-Arbitration and Unfair Labor Practice Risk 8.6 Strikes, Lockouts, and Contingency Planning
9 HR Information Management: HRIS, Records, Privacy, Reporting, and Metrics
9.1 HRIS Governance and Operational Ownership 9.2 Employee Records and Retention Controls 9.3 Data Privacy, Confidentiality, and Access 9.4 Reporting, Metrics, and HR Dashboards 9.5 Data Integrity, Audits, and System Controls 9.6 Compliance Workflows, Vendors, and Incident Response
10 PHR U.S. Employment Law Playbooks: FLSA, FMLA, ADA, Title VII, OSHA, and ERISA
10.1 Law Issue Spotting and HR Playbook Logic 10.2 FLSA Classification, Hours, and Overtime 10.3 FMLA, ADA, Leave, Accommodation, and Medical Confidentiality 10.4 Title VII, ADEA, EEO, Harassment, and Retaliation 10.5 OSHA, I-9, and Workplace Compliance Records 10.6 ERISA, Benefits Compliance, and Integrated Documentation
11 Timed Practice, Error Review, and Domain-Weighted Study Plan
11.1 Two-Hour Pacing and Question Triage 11.2 Domain-Weighted Practice Map 11.3 Wrong-Answer Taxonomy 11.4 Legal Versus Process Misses 11.5 Pretest Uncertainty and Confidence Scoring 11.6 Ninety-Day Retake Repair Plan
12 Final PHR Integrated Review, Exam Day, and Recertification Plan
12.1 Final Integrated Review Cycle 12.2 Exam-Day Logistics and Delivery 12.3 Last-Week Law and Domain Bridge 12.4 Operational HR Readiness Thresholds 12.5 Recertification Credit Plan 12.6 Post-Exam Results and Next Steps
9.3 Data Privacy, Confidentiality, and Access
Key Takeaways Explain This Topic AI
HR privacy starts with purpose limitation: collect only data needed for a legitimate HR or business purpose.
Confidentiality is enforced through role-based access control (RBAC), least privilege, secure storage, limited disclosure, and user training.
ADA requires medical and accommodation data be kept confidential; HIPAA may apply to group-health-plan PHI; multi-state employers may face the CCPA/CPRA and GDPR.
The best PHR answer balances business need against the minimum-necessary standard and applies policy consistently to every employee.
Last updated: June 2026
Privacy as an HR Operating Discipline
HR holds information employees rarely share with managers or coworkers: medical restrictions, benefit elections, Social Security numbers, pay data, complaints, investigation details, leave reasons, and family data. Privacy is not just an IT topic, it is an HR discipline shaping collection, access, reporting, storage, and disposal.
When a scenario asks whether HR should share employee information with a supervisor, executive, vendor, or coworker, start with business need and the minimum-necessary standard . HR shares only what the recipient needs to perform an authorized role. Curiosity, convenience, or organizational rank is never sufficient justification.
- Privacy Principle HR Question Example Control
- Purpose limitation Why is this data needed? Collect only job-related or compliance-related fields
- Minimum access Who truly needs to know? Role-based permissions, redacted reports
- Confidential handling How is it protected? Separate secure storage, encryption in transit
- Accountability Can access be reviewed? Audit logs and periodic access certification
- Role-Based Access and the Legal Backdrop
Role-based access control (RBAC) ties permissions to job duties. A recruiter needs applicant data but not employee medical records; a payroll specialist needs pay inputs but not investigation files; a supervisor may need a work restriction but not a diagnosis. The Americans with Disabilities Act (ADA) mandates confidential, separate handling of medical and accommodation data. The Health Insurance Portability and Accountability Act (HIPAA) can reach protected health information flowing through a group health plan.
Multi-state and global employers may also face the California Consumer Privacy Act / California Privacy Rights Act (CCPA/CPRA) and the EU General Data Protection Regulation (GDPR) , which add notice, access, and deletion obligations.
Periodic access review matters because roles change. Employees transfer, managers move teams, projects end, and vendors lose their need for access. HR and IT must add, change, and remove access promptly when responsibilities shift, ideally on a defined recertification cycle. The greatest exposure window is at offboarding: a terminated employee or ended vendor whose credentials remain live is a standing breach risk, so the separation workflow must revoke access on the effective date, not weeks later.
State and global rules raise the bar for employers operating across jurisdictions. The CCPA/CPRA grants California employees rights to know what personal information is collected and to request deletion within statutory windows. The GDPR adds lawful-basis, data-minimization, and cross-border-transfer requirements for EU personnel data. Illinois' Biometric Information Privacy Act (BIPA) regulates fingerprint and facial timekeeping data with consent and notice duties. HR does not need to memorize every clause, but should recognize that more locations mean more obligations and route novel situations to legal.
Confidentiality in Everyday Workflows
Most breaches happen during ordinary tasks: attaching the wrong file, sending a spreadsheet with hidden columns, leaving a report on a shared printer, discussing a complaint in an open area, or over-provisioning a manager. The fix is not "tell people to be careful", it is to design workflows that reduce accidental disclosure.
Use secure, approved channels for sensitive documents, not personal email or open shared folders.
Redact unnecessary fields before any report leaves HR.
Give managers functional information (restrictions, schedule limits) without the underlying diagnosis.
Train HR users on confidentiality expectations and escalation steps.
Revoke access promptly after transfers, separations, or vendor role changes.
Categories Needing Heightened Care
Not all employee data carries equal risk. The exam expects HR to treat certain categories with extra control regardless of who asks.
- Sensitive Category Heightened Control Disclosure Rule of Thumb
- Medical / disability (ADA) Separate file, restricted access Share functional restriction only, never diagnosis
- Genetic / family history (GINA) Siloed, never used in decisions Do not collect or disclose
- Social Security numbers Mask, encrypt, limit display Show last four only where possible
- Pay and compensation Role-based access, audit logs Need-to-know for the specific action
- Complaints / investigations Confidential file, limited circle Only those running or deciding the matter
- Worked Example
A recruiter asks for read access to the full employee module "to save time." Purpose limitation says no, the recruiter's role needs applicant and requisition data, not active-employee medical, pay history, or discipline. HR provisions a recruiter role scoped to the ATS and open requisitions, then recertifies it quarterly. When the recruiter later moves into an HRBP role, access is re-evaluated rather than simply stacked on top of the old permissions, avoiding privilege creep .
Privacy applies to analytics too. A dashboard with names removed can still identify a person through small cell sizes , a unique job title, or pinpoint location data; a survey result for a department of three can de-anonymize respondents. HR should suppress or aggregate metrics for very small groups, a common rule is to mask any cell below a minimum count such as five. PHR answer logic favors prevention and documentation: when a disclosure occurs, follow the incident process, preserve facts, notify the right owners, correct access, and record what happened.
Ignoring the issue, or blaming one user while leaving the control gap open, is rarely the best answer, the control, not just the person, must be fixed.