Checklist · Technology, Media & Telecommunications / IT Contracts
Consumer Data Right: data holder obligations on the CDR site
Checklist of data holder obligations as the Consumer Data Right site states them, including authorisation, the 12-month maximum, withdrawal within two business days, and twice-yearly reports. The Rules were not opened. The page says it is general guidance.
- Kind
- Checklist. Steps or checks to work through and tick off.
- Where it applies
- Australia, Commonwealth
- AI use
- Yellow You and the tool draft together, with you directing. You check every statement you rely on.
- Law stated as at
- 22 October 2026
- Status
- Maintained. Checked on 22 October 2026 against the authority it cites, for Australia and Commonwealth.
- Version
- 1
- Source
- Written for this library
When to use it
Use when reviewing a data holder's Consumer Data Right participation, including banking or energy. It is not an accredited data recipient agreement and it is not a privacy-policy draft.
Used for these tasks
Each task page says how far AI may help with the task and what the lawyer must review.
How AI may be used
AI may list the obligations the CDR page names and note which internal document the lawyer points to. The lawyer decides whether the data holder complies.
AI may
- Build a row for each obligation on the page and name the policy or log the lawyer identifies
- Flag a row with no document
- Record that an authorisation states a period no longer than 12 months, if the screen shows a period
AI must not
- Must not say the data holder complies with the Rules
- Must not treat this page as a statement of the law. The page says it is general guidance
- Must not draft the Consumer Data Right policy. The OAIC guide was not opened
The lawyer checks
- The entity is a data holder, and any exemption is on the ACCC register. That register was not opened
- Withdrawal of authorisation is actioned within two business days, and the accredited data recipient is notified
- The twice-yearly report includes the counts the page lists
Method: how the Green, Yellow and Red levels are decided. This is guidance for planning, not legal advice.
Read the full text
The full text is available after you log in. It is free. When you log in you can:
- read the whole precedent, with its drafting notes beside it;
- copy it, or download it as a Word file or Markdown;
- add it to your firm’s knowledge base, so colleagues can find it;
- let the AI tools you connect read it from that knowledge base.
The summary, the law it rests on and the AI-use guidance above stay public. Privacy.
More in Technology, Media & Telecommunications / IT Contracts
- IT services statement of work template (under a master services agreement)
- Ransomware or cyber extortion payment report: fields on the ACSC form
- SaaS / cloud services agreement (Australian law, business customers)
- CCPA service provider and contractor addendum
- SaaS subscription and negative-option checklist
- Website and online platform terms of use (Australian business, with Australian Consumer Law carve-outs)
- AI standard clauses for AI features in cloud services (Bonterms AI Standard Clauses v1.0, CC0)
- Deed of assignment of intellectual property and moral rights consent (contractor or developer software)
- Service level schedule with service credits (SaaS, managed or hosted services)
- Register of Critical Infrastructure Assets: what the CISC page asks for
- Checklist for electronic consumer records
- SaaS subscription agreement
- AI addendum: ownership of AI-generated output, training-data rights and AI-specific warranties (customer-side)
- Email and SMS marketing campaign checklist (Spam Act consent, sender identification and unsubscribe)
- SOCI Act cyber incident report: 12-hour and 72-hour clocks
- Software source code escrow agreement (three-party: supplier, customer and escrow agent)
- AI vendor terms review checklist
- Statement of work
- Cross-border disclosure assessment for a technology vendor (APP 8 and s 16C checklist and record)
- Critical infrastructure risk management program: annual report contents
- Australian Government AI model clauses (DTA, BuyICT ClauseBank): use guide for agencies and suppliers
- Open source licence compliance review checklist (technology transactions and product releases)
- Security incident clause
- Data protection, security and breach-notification schedule (processor terms)
- Software development agreement with AI coding-assistant and open-source terms
- Checklist: reviewing a vendor SaaS or technology contract (customer side, including AI terms)
All precedents for Technology, Media & Telecommunications / IT Contracts · Tasks and AI use in this area