These guidelines provide examples for how to implement the data recipient withdrawal process.
Overview
The withdrawal journey for a consumer contains several steps, including:
- Identifying a data sharing arrangement they wish to withdraw
- Reviewing the implications and confirming withdrawal
- Receiving a final notification of success
The consumer must be able to review their data sharing arrangement from the consumer dashboard.
The consumer will be advised of potential consequences of withdrawal before they stop sharing. This should nudge the consumer to review how withdrawal may impact their service and the handling of their data.
The consumer may receive confirmation that they have successfully withdrawn their consent, and be provided with an updated view of their expired consent on their dashboard.
Wireframes and guidelines
Note: The wireframes shown are examples of how to implement key rules, standards, and guidelines. Use the on-screen functions to adjust zoom level or expand the wireframes to be viewed at full screen.
Default example
The following wireframes show a basic example of the consent withdrawal process. Variations can be found in the below sections.
AP Disclosure consent withdrawal
The following wireframes show examples of the AP disclosure consent withdrawal process.
Holding data as a data holder
Under the CDR Rules Clause 7.2 of Schedule 3 (Conditions for accredited person to be data holder), an authorised deposit‑taking institution (ADI) or non-bank lender who is an accredited data recipient can hold CDR data as a data holder, provided the conditions of the clause are met.
Collection consent withdrawal - AP holding collected data as a data holder
The following wireframes show examples to reflect requirements for collection consent withdrawal where subclause 7.2(2) of Schedule 3 applies, Conditions involving notification prior to first collection.
CDR consent withdrawal - Permission to hold collected data as a data holder
The following wireframes show examples for consent withdrawal where consumers have granted permission for the recipient to become a data holder of collected CDR data per subclause 7.2(2A) of Schedule 3.
Download open source asset
Open source design assets are created in Figma for the purposes of assisting implementation. This Figma file contains annotated wireframes and working prototypes for Withdrawal, including:
- Default example
- AP Disclosure consent withdrawal
- Holding data as a data holder
- Collection consent withdrawal - AP holding collected data as a data holder
- CDR consent withdrawal - Permission to hold collected data as a data holder
Item | File | Date released | Version introduced |
|---|---|---|---|
September 17, 2025 | 1.35.0 |
For past versions, refer to Change log.
About this page
References
The artefacts on this page were informed by the following sources.
Title | Author | Date published | URL | Type |
|---|---|---|---|---|
The Treasury | August 9, 2024 | Consultations | ||
Data Standards Body (DSB) | May 21, 2021 | Consultations | ||
Data Standards Body (DSB) | February 26, 2021 | Consultations | ||
GippsTech | July 31, 2019 | Research | ||
Greater than X | July 31, 2019 | Research | ||
Tobias | July 31, 2019 | Research | ||
Nielsen Norman Group (NNG) | April 24, 1994 | Other | ||
Nielsen Norman Group (NNG) | April 24, 1994 | Other |
Last updated
This page was updated @September 17, 2025
Have your say
Community consultations and maintenance are part of our ongoing process. Here’s how you can get involved:
- Request new Guidelines or changes to existing Guidelines through the CX Guidelines Consultation process
- Request new Standards or changes to existing Standards through the Standards Maintenance process
- Log a ticket for any questions about the rules, standards, or guidelines through the CDR Support Portal
- Email your feedback to cx@dsb.gov.au
Quick links to CX Guidelines: