Netherlands GDPR Implementation Act (UAVG — Uitvoeringswet AVG, 2018)vsJordan Draft Personal Data Protection Law (2022)
See exactly how Netherlands GDPR Implementation Act (UAVG — Uitvoeringswet AVG, 2018) controls map to Jordan Draft Personal Data Protection Law (2022). Pre-computed mappings, identified gaps, and coverage analysis.
According to the TheArtOfService Compliance Knowledge Graph:
Netherlands GDPR Implementation Act (UAVG — Uitvoeringswet AVG, 2018) maps to Jordan Draft Personal Data Protection Law (2022) with 52% coverage across 17 directly mapped controls. Analysis of 33 Netherlands GDPR Implementation Act (UAVG — Uitvoeringswet AVG, 2018) controls identifies 16 compliance gaps — primarily concentrated in Chapter 1 — General Provisions.
Source: TheArtOfService Knowledge Graph | 33 controls analysed | 693 frameworks | 819K+ cross-framework mappings
Control Mappings
Showing 20 of 63 mapped controls across 5 domains. Sign up to explore all 819K+ mappings across 693 frameworks.
Chapter 1 — General Provisions(20 mappings)
+43 more mappings
Plus AI-powered gap analysis, compliance advisory, PDF exports, and cross-mapping for all 693 frameworks.
Create Free Account →Free forever — no credit card required
Related Comparisons
Other Netherlands GDPR Implementation Act (UAVG — Uitvoeringswet AVG, 2018) comparisons
Other Jordan Draft Personal Data Protection Law (2022) comparisons
Stop Paying Consultants to Read Spreadsheets
AI-powered compliance intelligence across 693 frameworks — at a fraction of consulting costs.
Free
- ✓ 693 framework browser
- ✓ Cross-framework mappings (819K+)
- ✓ 824 compliance assessments
- ✓ 3 AI queries & searches per day
Professional
- ✓ Unlimited AI Compliance Advisory
- ✓ Unlimited full-text search
- ✓ Framework self-assessment
- ✓ PDF, Excel & CSV exports
What are the key differences between Netherlands GDPR Implementation Act (UAVG — Uitvoeringswet AVG, 2018) and Jordan Draft Personal Data Protection Law (2022)?
Netherlands GDPR Implementation Act (UAVG — Uitvoeringswet AVG, 2018) has 33 controls across its framework, while Jordan Draft Personal Data Protection Law (2022) covers 40 controls. Direct mapping analysis identifies 17 overlapping controls (52% coverage). The frameworks diverge most significantly in Chapter 1 — General Provisions, where 9 Netherlands GDPR Implementation Act (UAVG — Uitvoeringswet AVG, 2018) controls have no direct Jordan Draft Personal Data Protection Law (2022) equivalent.
How many controls map between Netherlands GDPR Implementation Act (UAVG — Uitvoeringswet AVG, 2018) and Jordan Draft Personal Data Protection Law (2022)?
Of 33 total Netherlands GDPR Implementation Act (UAVG — Uitvoeringswet AVG, 2018) controls, 17 map directly to Jordan Draft Personal Data Protection Law (2022) controls — representing 52% coverage. The remaining 16 controls represent compliance gaps requiring additional documentation or compensating controls to satisfy both frameworks simultaneously.
What are the compliance gaps when mapping Netherlands GDPR Implementation Act (UAVG — Uitvoeringswet AVG, 2018) to Jordan Draft Personal Data Protection Law (2022)?
16 Netherlands GDPR Implementation Act (UAVG — Uitvoeringswet AVG, 2018) controls have no direct equivalent in Jordan Draft Personal Data Protection Law (2022). The highest concentration of gaps is in Chapter 1 — General Provisions with 9 unmapped controls. These gaps represent areas where additional controls, policies, or documentation must be created to achieve compliance with both frameworks.
Which control domains have the most gaps between Netherlands GDPR Implementation Act (UAVG — Uitvoeringswet AVG, 2018) and Jordan Draft Personal Data Protection Law (2022)?
The domain with the highest gap count is Chapter 1 — General Provisions (9 gaps). Export the full domain-by-domain gap breakdown via the Professional tier to generate a prioritised remediation roadmap.
Related Resources
This platform provides educational compliance tools, not legal, regulatory, or professional compliance advice. Cross-framework mappings are AI-assisted interpretations and do not reproduce or replace official standards. Framework names and trademarks belong to their respective owners. Consult qualified professionals for your specific compliance requirements. See our Terms of Service.