Medicaldesknet • Updated November 2026
📝 Compliance • 10 min read

A 10-Step HR Data Protection Audit for Employers Under GDPR, DPDP and PDPL

Your payroll, HRIS, benefits broker and Slack all hold staff data. This 10-step audit maps retention, consent, transfers and vendor contracts to GDPR, India's DPDP Act and Saudi PDPL.

SPONSORED CONTEXTUAL PLACEMENT
💼
Evaluating Enterprise Deployments in 2026?

Request our confidential total cost of ownership matrix and vendor RFP templates.

Launch Calculator →

Set the audit scope across three regimes before you open any system

Most employers find their data protection exposure the hard way. An ex-employee files an access request, a payroll vendor reports a breach, or a new benefits platform turns out to host data in a country nobody checked. This playbook gives HR and finance one audit that covers every system holding staff data. It uses three regimes as reference points: the EU's GDPR, India's Digital Personal Data Protection Act 2023 (DPDP) and Saudi Arabia's Personal Data Protection Law (PDPL). They're useful even if you operate in only one of these places. Between them they cover the main models of employee data protection compliance, and frameworks in the UK, Brazil, the UAE, Singapore and South Africa follow similar logic.

Start by deciding which regimes apply. GDPR applies to staff in the EU and EEA. Separate UK GDPR rules apply to UK staff. DPDP applies to personal data processed in India, and to processing outside India connected with offering goods or services there. If you have an Indian entity or Indian contractors, assume it applies. PDPL applies to processing in Saudi Arabia and to the data of Saudi residents processed abroad.

Advertisement
Audit areaGDPR (EU)DPDP Act (India)PDPL (Saudi Arabia)
Basis for routine HR processingContract, legal obligation, legitimate interests; consent rarely valid for staffEmployment purposes are a listed "legitimate use"; consent for anything beyondContract, legal obligation, legitimate interest (not for sensitive data), consent
Breach notice to regulator72 hours where risk existsTo the Data Protection Board and affected individuals; detailed report within 72 hours under the RulesGenerally 72 hours to SDAIA where harm is likely
Cross-border transfer modelAdequacy, SCCs or other safeguardsPermitted unless the destination is restricted by government notificationAdequacy or safeguards such as SDAIA standard clauses, plus a risk assessment in some cases
Maximum penaltyEUR 20m or 4% of global turnoverUp to INR 250 crore for the most serious breachesFines up to SAR 5m (doubled for repeats); criminal penalties for some sensitive-data disclosures
Status in late 2026Fully in forceRules notified Nov 2025; most duties phase in by around May 2027Enforced since September 2024

Give one person ownership of the audit, usually the HR operations lead or the DPO where one exists. Then book four to eight weeks. A 50-person single-country company can finish faster. A 600-person company in three regimes should plan for the full eight.

RECOMMENDED SOLUTION

Looking to streamline vendor RFP selection?

Access pre-negotiated tier discounts through our independent institutional network.

Compare Pricing →

Inventory every system and map where staff data actually flows

Step 1: List every system, including the shadow ones

The obvious entries are the HRIS, payroll, the applicant tracking system, benefits administration and time-and-attendance. The ones that cause trouble are usually elsewhere:

  • Spreadsheets of salary reviews and disciplinary notes on shared drives
  • Insurance broker portals and occupational health providers
  • Background-check, e-signature and learning platforms
  • Collaboration tools where managers discuss performance or sick leave
  • Expense tools, corporate card platforms and travel booking systems
  • Badge access, CCTV and device-monitoring software

Ask finance for the list of vendors you pay. Ask IT for the list of single sign-on applications. Compare both against HR's list. The gaps are your shadow systems.

Step 2: Map the data, the location and the people with access

For each system, record what data categories it holds, where the vendor hosts and supports it, who has admin access, and which other systems it feeds. This becomes your record of processing activities. GDPR Article 30 requires one, and PDPL's implementing regulations expect something equivalent. The fields that matter most are hosting country, sub-processor locations and whether the system holds sensitive data. Without those three, Steps 3 to 9 can't be done.

Test the lawful basis for each use and stop over-relying on consent

Step 3: Assign a lawful basis to every processing purpose

Many HR teams still put a blanket consent clause in the employment contract. Under GDPR that's a weak position. European regulators generally take the view that employee consent is rarely freely given, because of the imbalance of power. Payroll should rest on contract, statutory reporting on legal obligation, and things like fraud monitoring on legitimate interests with a documented balancing test. Some EU member states also add employment-specific rules under GDPR Article 88. Germany is the best-known example, so check national law.

DPDP is friendlier to employers. Section 7 lists processing for employment purposes, and for protecting the employer from loss or liability, as a legitimate use that doesn't need consent. That covers core HR. It doesn't obviously cover optional extras, such as sharing data with a wellness app vendor for marketing or using staff photos in recruitment ads. Those need consent, and under DPDP that consent must be specific, informed and as easy to withdraw as to give. PDPL accepts legitimate interest as a basis, but not for sensitive data.

Step 4: Isolate sensitive data and run impact assessments

Health and disability information, biometric time clocks, union membership, religion (often collected for Gulf payroll or holiday calendars) and criminal records all need extra handling. Where you use biometrics, systematic monitoring or health data at scale, run a data protection impact assessment. GDPR Article 35 mandates one in these cases, and PDPL expects one for high-risk processing. One red flag to look for: benefits enrollment forms that send medical questionnaires through the HRIS instead of straight to the insurer. Redesign that flow so HR never sees the answers.

Build a retention schedule that people actually follow

Step 5: Set retention periods per data category and country

None of the three regimes sets a single retention period for HR files. All three require you to keep data only as long as the purpose needs, while employment, tax and social security laws set minimum periods that differ by country. Payroll records may need to be kept for many years in parts of the EU. Gratuity and provident fund records in India, and end-of-service records in Saudi Arabia, have their own requirements. Take the local statutory minimum and add a defined limitation-period buffer. Don't use "forever." Under DPDP, also plan for the Rules' requirement to retain certain processing logs for a minimum period, which the Rules currently put at one year; confirm with Indian counsel.

Unsuccessful candidates' data is where many employers fail. A common position is six to twelve months unless the candidate agrees to join a talent pool. Confirm the right figure locally.

Step 6: Prove deletion actually happens

A retention policy without automation is a document, not a control. Check whether each system can auto-delete or anonymize records on a schedule. Major HR platforms such as Workday, SAP SuccessFactors, Personio, HiBob and Darwinbox generally offer retention or purge settings, but they often aren't switched on by default, and availability varies by plan. Then run a test: pick five people who left well beyond your retention period and see if their records still exist in payroll, the ATS and backups. If they do, raise it as a finding with an owner and a deadline.

RECOMMENDED SOLUTION

Looking to streamline vendor RFP selection?

Access pre-negotiated tier discounts through our independent institutional network.

Compare Pricing →

Lock down cross-border transfers for a distributed workforce

Step 7: Document a transfer mechanism for every flow out of each jurisdiction

This step usually turns up the most findings, because global HR stacks often route data through the US, Ireland, India and Singapore by default. For each flow in your Step 2 map, record the exporting country, the importing country and the legal mechanism you rely on.

Under GDPR, transfers need an adequacy decision or a safeguard. For US vendors, the main options are the EU-US Data Privacy Framework (only if the vendor is certified) or the 2021 Standard Contractual Clauses plus a transfer impact assessment. DPDP uses a negative-list model: transfers are allowed unless the government restricts a destination. Sector rules, such as those for financial firms regulated by the RBI, can still require localization. PDPL is arguably the strictest of the three in practice. It allows transfers to jurisdictions with adequate protection or under safeguards such as SDAIA's standard contractual clauses or binding corporate rules, and in some cases it requires a documented risk assessment.

Worked example (hypothetical): Say a 120-person software company has 70 staff in Germany, 35 in Bengaluru and 15 in Riyadh, all on one US-hosted HRIS with an Indian payroll bureau. The audit needs three sets of paperwork: SCCs or DPF reliance for Germany to the US, SDAIA-compliant safeguards and a risk assessment for Riyadh to the US, and a check that no Indian sector rule restricts the Bengaluru data. It should also check whether the Indian payroll bureau ever receives German or Saudi data. If it does, that flow needs its own mechanism.

Fix vendor contracts and breach readiness before an incident tests them

Step 8: Review every HR vendor data processing agreement

The HR vendor data processing agreement is where many audits find the biggest gap. Old payroll bureaus and local benefits brokers often work under contracts that say nothing about data. GDPR Article 28 sets out mandatory processor terms. DPDP lets data fiduciaries engage processors only under a valid contract and keeps the fiduciary accountable for what the processor does. PDPL similarly requires controllers to choose processors that provide sufficient guarantees.

Check each agreement for:

  • Processing only on your documented instructions
  • A sub-processor list, with notice of changes and a right to object
  • Named hosting and support locations, plus the transfer mechanism from Step 7
  • Breach notice to you within 24 to 48 hours, so you can meet 72-hour regulator deadlines
  • Deletion or return of data at contract end, with certification
  • Audit rights, or acceptance of SOC 2 Type II or ISO 27001 reports

Red flags include a vendor that won't name its sub-processors, breach notice "without undue delay" with no hour limit, or a liability cap set at one month's fees. Push hardest on payroll and benefits vendors, because they hold bank details, national ID numbers and health data.

Step 9: Test access controls and the breach playbook

Pull admin user lists from the HRIS and payroll and remove leavers and role-changers. Then run a one-hour tabletop exercise: the payroll vendor reports a ransomware incident on a Friday afternoon. Who decides whether to notify the EU authority, India's Data Protection Board and SDAIA, and who drafts the message to employees? If nobody can answer in the room, that's your finding.

Close the loop on employee rights, budget and audit cadence

Step 10: Rehearse rights requests and lock in a review cycle

Employees can ask to access, correct and in some cases erase their data under all three regimes. Access requests from departing staff in a dispute are the most common, and they get expensive if you have to search email by hand. GDPR generally gives one month to respond. Set up an intake route, an identity check, a search procedure covering the systems from Step 1, and a template response. DPDP also requires a grievance mechanism, and staff can escalate to the Data Protection Board. Run one test request a year from start to finish.

On budget, typical 2026 market ranges, which vary by scope and contract, look like this: roughly USD 5,000 to 15,000 for an external privacy consultant to run a single-country audit for a company under 200 staff, and USD 15,000 to 50,000 for a multi-jurisdiction audit with legal review of vendor agreements. Privacy management platforms such as OneTrust, TrustArc, Securiti or Osano commonly run USD 5,000 to 40,000 a year, depending on modules and headcount. Local pricing varies a lot, so get quotes. The main cost drivers are the number of jurisdictions, the number of vendors needing contract renegotiation, and whether you hold biometric or health data.

For most employers under 300 staff, a spreadsheet register plus an external legal review of transfers and vendor agreements is the better buy than a platform. A platform starts to pay off once you're managing dozens of vendors or several jurisdictions, when manual tracking breaks down. Repeat the full audit every year, and do a light review whenever you add a country or an HR vendor. This article describes general practice, so have a licensed data protection lawyer in each jurisdiction sign off on lawful bases, retention periods and transfer mechanisms before you rely on them.

Your next step this week is Step 1: get the vendor payment list from finance and the single sign-on app list from IT. The audit can't start properly until you know which systems hold staff data.

Questions Buyers Ask

Can we rely on employee consent for HR data processing? +
When do India's DPDP obligations actually apply to employers? +
What should an HR vendor data processing agreement include at minimum? +
ME
Medicaldesknet Editorial Team
Independent research desk
Guides on Medicaldesknet are produced by our editorial team. Pricing, features and regulations change often - confirm details with the vendor or a licensed professional before making decisions.
SPONSORED 2026 Vendor Pricing Benchmarks: Model exact seat pricing, setup fees, and ROI across our verified database.
Launch Calculator →