UNCITRAL Model Law on Electronic Commerce (1996, updated 2005)vsPrivacy Act 1988 (Australia)
See exactly how UNCITRAL Model Law on Electronic Commerce (1996, updated 2005) controls map to Privacy Act 1988 (Australia). Pre-computed mappings, identified gaps, and coverage analysis.
According to the TheArtOfService Compliance Knowledge Graph:
UNCITRAL Model Law on Electronic Commerce (1996, updated 2005) maps to Privacy Act 1988 (Australia) with 19% coverage across 7 directly mapped controls. Analysis of 36 UNCITRAL Model Law on Electronic Commerce (1996, updated 2005) controls identifies 29 compliance gaps — primarily concentrated in Part I, Chapter III - Communication of Data Messages.
Source: TheArtOfService Knowledge Graph | 36 controls analysed | 701 frameworks | 337K+ cross-framework mappings
Control Mappings
Showing 13 of 13 mapped controls across 4 domains. Sign up to explore all 337K+ mappings across 701 frameworks.
Part I, Chapter II - Application of Legal Requirements to Data Messages(6 mappings)
Part I, Chapter III - Communication of Data Messages(3 mappings)
Part II - Electronic Commerce in Specific Areas (Carriage of Goods)(3 mappings)
Part I, Chapter I - General Provisions(1 mappings)
Related Comparisons
Other UNCITRAL Model Law on Electronic Commerce (1996, updated 2005) comparisons
Other Privacy Act 1988 (Australia) comparisons
Stop Paying Consultants to Read Spreadsheets
AI-powered compliance intelligence across 701 frameworks — at a fraction of consulting costs.
Free
- ✓ 701 framework browser
- ✓ Cross-framework mappings (337K+)
- ✓ 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 UNCITRAL Model Law on Electronic Commerce (1996, updated 2005) and Privacy Act 1988 (Australia)?
UNCITRAL Model Law on Electronic Commerce (1996, updated 2005) has 36 controls across its framework, while Privacy Act 1988 (Australia) covers 48 controls. Direct mapping analysis identifies 7 overlapping controls (19% coverage). The frameworks diverge most significantly in Part I, Chapter III - Communication of Data Messages, where 4 UNCITRAL Model Law on Electronic Commerce (1996, updated 2005) controls have no direct Privacy Act 1988 (Australia) equivalent.
How many controls map between UNCITRAL Model Law on Electronic Commerce (1996, updated 2005) and Privacy Act 1988 (Australia)?
Of 36 total UNCITRAL Model Law on Electronic Commerce (1996, updated 2005) controls, 7 map directly to Privacy Act 1988 (Australia) controls — representing 19% coverage. The remaining 29 controls represent compliance gaps requiring additional documentation or compensating controls to satisfy both frameworks simultaneously.
What are the compliance gaps when mapping UNCITRAL Model Law on Electronic Commerce (1996, updated 2005) to Privacy Act 1988 (Australia)?
29 UNCITRAL Model Law on Electronic Commerce (1996, updated 2005) controls have no direct equivalent in Privacy Act 1988 (Australia). The highest concentration of gaps is in Part I, Chapter III - Communication of Data Messages with 4 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 UNCITRAL Model Law on Electronic Commerce (1996, updated 2005) and Privacy Act 1988 (Australia)?
The domain with the highest gap count is Part I, Chapter III - Communication of Data Messages (4 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.