Skip to main content

Consent Store

HaaS follows a secure and Personally Identifiable Information (PII) minimised approach when handling CDR data. This page describes how it works.

HaaS discloses data to the CDR via realtime calls to the Data Adapter as the ADR collects CDR data, and does not store the CDR data that is disclosed. HaaS avoids storing any PII and only stores the minimum anonymous data needed to deliver its functionality. Namely:

  • Consumer consent to authorise CDR data disclosure to ADRs
  • Arrangement Amendment History
  • Disclosure Options Management Settings
  • Secondary User Instructions
  • Account Notification Settings

CDR Arrangements / Consent Data Points

Data PointFurther Information
Arrangement IdentifierA UUID generated on setup in accordance with the Standards
Sharing DurationAn integer representing the number of seconds of the arrangement specifically the start and end epochs
Principal IDThe Principal ID supplied by the Data Adapter identifier the Consumer being shared to the CDR
Principal TypeStores whether this Principal is an Individual or Non-Individual.
User IDThe User ID supplied by the Data Adapter for the User that gave consent
ATO User ID (Optional)If this arrangement was created by a User with Authority to Operate over another User, then this optional User ID captures the original consenting User that acted on the User's behalf.
ATO Type (Optional)If this arrangement was created by a User that can act on another User's behalf, then this records the type of ATO that authorised the arrangement (as returned by the Data Adapter in getUser)
Account IDs SharedThe Account IDs as returned by the Data Adapter for the Principal and whether the were authorised for this arrangement
Scopes GrantedThe scopes agreed by the consumer as outlined in the Standards
Claims GrantedThe claims agreed by the consumer as outlined in the Standards
Private ArrangementIn the event that the arrangement was created by a vulnerable User, this arrangement is marked as private and permanently exempt from notifications to protect the vulnerable User.
Other permission detailsIf agreed during the authorisation flow (if any). Currently there are no other permission details agreed although this may change in future dependent on the Standards

Amendment History​

As part of the July 2024 CDR FDO to show historical amendments, HaaS also collects these data points for all arrangements created or amended after the Vega Release.

Data PointFurther Information
Scopes Added/RemovedThe scopes removed/added as part of this amendment
Claims Added/RemovedThe claims removed/added as part of this amendment
Account IDs Added/RemovedThe account IDs (as per the Data Adapter) removed/added as part of this amendment
Account Numbers Added/RemovedTo present the a Consumer identifiable but non-PII account identifier of historical arrangements where the account might no longer be returned by the data adapter. The data stored per industry is limited to:
  • Banking: Masked Account Number
  • Energy: Account Number

Disclosure Options Management and Secondary User Instructions

Data PointFurther Information
Account IDs and relationships to User IDs and Principal IDsTo manage DOMS, HaaS needs to store the full relationship of Accounts to the Users and Principals involved including the User's relationship to the account (OWNER, SECONDARY_USER, NOMINATED_REPRESENTATIVE)
Disclosure Status of this AccountThis defaults to PRE_APPROVAL but can be elected to NON_DISCLOSURE by an account owner in their dashboard
Requests to change the disclosure optionWhich User requested it, the date requested, date of approval/expiry and the approval status from each account owner
Secondary User Instruction On/OffFor each account and secondary User, the secondary User relationship is stored and there is an on/off for the SUI being active (defaults to off)

Notification Settings

Data PointFurther Information
Account IDsAs returned by the data adapter for the User and Principal
Event Notification PreferencesOptions for that User and Account of EVENT, WEEKLY or MONTHLY or NONE depending on the event

Other Data Stored

Data PointFurther Information
ADR Client RegistrationsA copy of the client metadata registered with its CDR standardised Dynamic Client Registration
Register Metadata CacheA cache of the Data Recipient Brands & Software Product Statuses register API data polled every 3 minutes
ADR Authorisation RequestsThe PAR requests sent by the ADR to initiate consent flow, including tracking of Consumer progress through a high watermark step for metrics collection purposes
Aggregate CDR MetricsHaaS collects aggregate 1 minute sample counters and timers to enable the ACCC metrics require by the Data Standards

Special Cases for HaaS Authoritative Data Clusters

HaaS supports being authoritative for certain data points where the customer's source systems does not capture this data and requires the data to be managed in HaaS Manager instead of sourcing the data via the Data Adapter. These data clusters can be opted into individually based on customer requirements.

HaaS-Authoritative Nominated Representatives​

In the case where Nominated Representatives are set to a source of WIKKIT_GATE, HaaS also stores:

Data PointFurther Information
User IDThe User ID that will login to consent flow
Principal IDThe User's Individual Principal that will be the result of their successful Data Adapter authentication
Non-Individual PrincipalThe Non-Individual Principal that this User has authority to represent.
Non-Individual Account IDsThe Non-Individual Principal accounts that that this User has authority to share.

This powers the state capture by Haas Manager:Manage Nominated Representatives

HaaS-Authoritative Vulnerability​

In the case where Vulnerability is set to a source of WIKKIT_GATE, HaaS also stores:

Data PointFurther Information
User and Principal IDThe User and Principal that is considered vulnerable
Vulnerable StateTrue/False

This powers the state capture by Haas Manager:Manage Vulnerable State

HaaS-Authoritative ATOs​

In the case where Authority to Operate are set to a source of WIKKIT_GATE, HaaS also stores:

Data PointFurther Information
User IDThe User ID that will login to consent flow
Principal IDThe User's Individual Principal that will be the result of their successful Data Adapter authentication
ATO User and Principal IDThe User and Principal ID that this User can act on behalf of
ATO TypeThe ATO Type as defined by getUser

This powers the state capture by Haas Manager:Manage Authority to Operate.