Due diligence
Security
How the software is hosted, who can reach what, and how it is built and released.
0third-party packages in the running software: every line is ours, and the tool that deploys it is pinned
0hosted AI models in a credit decision: no borrower’s data is sent to one
11,000+automated tests on every push; one failure stops the deploy
Independently rated A+
A+from Qualys SSL Labs, for the encrypted connection. Check it yourself: this website, the software
A+from securityheaders.com, for the browser security headers. Check it yourself: this website, the software
Independent ratings of this website and of the software, checked 11 November 2026. Each link runs the check again.
Hosting
- The software runs on Cloudflare’s network. There is no server of our own to patch or lose.
- The shared sandbox and our invoicing counts are held in Cloudflare storage placed in Oceania.
- A lender’s records live in the lender’s own database, in its own account, reached over signed HTTPS. We hold no copy.
Encryption
- HTTPS only, over TLS 1.2 or newer. Plain HTTP is redirected, and browsers are told to use HTTPS only (HSTS), on this website and in the software.
- Data at rest is encrypted by the platform it sits on: Cloudflare for ours, the lender’s own provider for its records.
- Each lender’s records carry a hash chain, so a record changed afterwards fails verification when it is read.
Access
- API keys are signed (HMAC-SHA256), scoped to one lender and to live or test, expire, and can be revoked. No table of keys exists to steal.
- Every member of a lender’s staff signs in with two factors: a passkey, which can’t be phished, or a single-use link to their work address and a code from an authenticator app. A lender can require passkeys of the staff who record funding. Borrowers sign in with a one-time code or a passkey.
- Sessions are HttpOnly, Secure and SameSite=Strict cookies. Deactivating a member of staff ends their sessions.
- Changes to a lender’s controls need a requester and a different approver.
- Rate limits on every keyed call, lower for test keys and the sandbox.
Pages and browsers
- A strict content security policy on every page: no inline script, no third-party script except Cloudflare’s cookieless visit counter, no framing.
- Nothing about a person is ever put in an address, so no link can leak one.
How it is built and released
- Every figure the software produces carries the evidence it came from, so a wrong one can be traced.
Reporting a vulnerability
Write to security@creditcresttechnologies.com.au, as security.txt says, with the address, the steps and what you saw.
- Test only in the sandbox, with invented people. A sandbox key comes from
POST /v1/keys/sandbox. - Do not open, change or keep anyone else’s data. No denial of service and no social engineering.
- Give us time to fix it before you publish.
We acknowledge within one business day and tell you what we found and what we changed. There is no bug bounty.