Due diligence
Data
What is kept, what is never kept, and where a borrower’s data goes.
What we keep, and for how long
| What | Kept by Creditcrest |
|---|---|
| Bank statements and transactions | Never. Read while the request is open, then gone |
| Applications, loans, documents, identity results | Never. Kept in the lender’s own database |
| Counts of what a lender used, for invoicing | Seven years, as tax records. They name the lender, never a borrower |
| Request logs: time, address, status | No more than 30 days. Never a request’s body |
| Calls made with a sandbox key: endpoint, status, error code, time | 35 days. Never a request’s body |
| Sandbox entries | Cleared at least once a day. Invented details only |
No borrower’s data is used to train or tune anything for anyone else, and no hosted AI model is called in any credit assessment. Where a lender asks for a model fitted to its own book — Score’s ratings, or a model built under AI and Data Advisory — it is built from that lender’s data, for that lender alone, and stays the lender’s. Nothing is sold.
Where a borrower’s data goes
Where it is processed
Cloudflare is a global network: a request is usually handled in Australia but may be handled elsewhere. A lender must say so in its own privacy policy (APP 8), and we give it the wording.
A breach
We tell an affected lender within 24 hours of becoming aware of a breach that touches its data, with what it needs for its own assessment and any notice to the OAIC. Every other notice, and when: Availability and incidents.