Current status
Moolah's existing connected-finance service uses Basiq Pty Ltd, an Accredited Data Recipient, for secure read-only Open Banking. Basiq's current published CDR policy identifies Moolah as a CDR representative.
The replacement Supabase-based app keeps new production bank connections disabled until the executed representative agreement/Register confirmation and the exact Basiq production application, credential, consent, callback, receipt and signed-webhook configuration are confirmed.
What you choose
The Open Banking consent flow must show:
- The banks, accounts and banking products included.
- The account, balance and transaction data requested.
- The purposes for which Moolah will use that data.
- The consent duration and how to manage or withdraw consent.
How connected data is used
- Cashflow tracking, categorisation and transaction review.
- Forecast suggestions and comparisons.
- Goals, net-worth and planning views that you choose to use.
- Reconciliation of an approved migration from the existing Moolah service.
Moolah cannot move money or change your accounts. CDR data and applicable derived data are not used for direct marketing.
Consent receipts and control
The provider flow supplies the required consent information and receipt channels. Moolah's settings provide a privacy-minimised consent dashboard and a path to manage or withdraw an active consent when the production boundary is enabled.
A Moolah security or webhook record is operational evidence only; it is not represented as the formal CDR consent receipt.
Withdrawal, deletion and de-identification
- Collection stops before a provider deletion or de-identification operation begins.
- Withdrawal remains available even when new collection is paused.
- Moolah records your eligible deletion or de-identification election and reconciles completion with Basiq.
- Raw CDR payloads are not retained in operational webhook or security logs.
- Privacy-minimised signed-webhook and security evidence is retained for 400 days, then removed by a bounded retention job.
Service providers and overseas processing
Basiq is the CDR principal and Open Banking provider for this service. Moolah's primary replacement database is configured in Australia.
Any other provider that can process CDR or derived CDR data must be included in the approved CDR data map, outsourced-service-provider assessment and customer disclosure before that processing is enabled.
Complaints and incidents
For a Moolah privacy or CDR concern, contact ryan@moolah.so. Do not email bank credentials or unnecessary account information.
You can also use the complaint channels in Basiq's current CDR policy. Moolah will coordinate with Basiq on consent, receipt, collection, withdrawal, deletion and incident issues that cross the representative boundary.
This page is a site-friendly summary. The current source policy is maintained at docs.basiq.io/en/articles/5088017-consumer-data-right-cdr-policy.