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
Live Consent Storeβ
| Data Point | Further Information |
|---|---|
| Arrangement Identifier | A UUID generated on setup in accordance with the Standards |
| Sharing Duration | An integer representing the number of seconds of the arrangement specifically the start and end epochs |
| Principal ID | The Principal ID supplied by the Data Adapter identifier the Consumer being shared to the CDR |
| Principal Type | Stores whether this Principal is an Individual or Non-Individual. |
| User ID | The 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 Shared | The Account IDs as returned by the Data Adapter for the Principal and whether the were authorised for this arrangement |
| Scopes Granted | The scopes agreed by the consumer as outlined in the Standards |
| Claims Granted | The claims agreed by the consumer as outlined in the Standards |
| Private Arrangement | In 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 details | If 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 Point | Further Information |
|---|---|
| Scopes Added/Removed | The scopes removed/added as part of this amendment |
| Claims Added/Removed | The claims removed/added as part of this amendment |
| Account IDs Added/Removed | The account IDs (as per the Data Adapter) removed/added as part of this amendment |
| Account Numbers Added/Removed | To 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:
|
Disclosure Options Management and Secondary User Instructions
| Data Point | Further Information |
|---|---|
| Account IDs and relationships to User IDs and Principal IDs | To 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 Account | This defaults to PRE_APPROVAL but can be elected to NON_DISCLOSURE by an account owner in their dashboard |
| Requests to change the disclosure option | Which User requested it, the date requested, date of approval/expiry and the approval status from each account owner |
| Secondary User Instruction On/Off | For 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 Point | Further Information |
|---|---|
| Account IDs | As returned by the data adapter for the User and Principal |
| Event Notification Preferences | Options for that User and Account of EVENT, WEEKLY or MONTHLY or NONE depending on the event |
Other Data Stored
| Data Point | Further Information |
|---|---|
| ADR Client Registrations | A copy of the client metadata registered with its CDR standardised Dynamic Client Registration |
| Register Metadata Cache | A cache of the Data Recipient Brands & Software Product Statuses register API data polled every 3 minutes |
| ADR Authorisation Requests | The 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 Metrics | HaaS 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 Point | Further Information |
|---|---|
| User ID | The User ID that will login to consent flow |
| Principal ID | The User's Individual Principal that will be the result of their successful Data Adapter authentication |
| Non-Individual Principal | The Non-Individual Principal that this User has authority to represent. |
| Non-Individual Account IDs | The 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 Point | Further Information |
|---|---|
| User and Principal ID | The User and Principal that is considered vulnerable |
| Vulnerable State | True/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 Point | Further Information |
|---|---|
| User ID | The User ID that will login to consent flow |
| Principal ID | The User's Individual Principal that will be the result of their successful Data Adapter authentication |
| ATO User and Principal ID | The User and Principal ID that this User can act on behalf of |
| ATO Type | The ATO Type as defined by getUser |
This powers the state capture by Haas Manager:Manage Authority to Operate.