Founding lenders: 40% off for three months. Ten places, until 30 June 2027. See the offer

Due diligence

Vendor questionnaire

Our answers in the shape of the Cloud Security Alliance’s CAIQ, a line each, with where to check. Your own form? Send it to hello@creditcresttechnologies.com.au and we will fill it in.

65 answers, as at 20 November 2026: 44 yes, 17 no, 3 partly, 1 not applicable. Download them as a spreadsheet (CSV).

Jump to one of 15 domains

Audit and assurance AA

QuestionAnswer
AA-01 Do you hold a SOC 2 report or an ISO 27001 certificate?No Neither is held. No audit is booked. Check
AA-02 Has an independent penetration test been done?No Not yet. Before any lender goes live. Rigorously tested internally in November 2026, and every high and medium finding in the software was fixed and tested; the summary will be shared with lenders. Check
AA-03 Do you hold professional indemnity and cyber insurance?No Neither is held, and no cover is bound yet. Check
AA-04 May a customer audit you?No The draft Lender Agreement has no audit clause; the question is with our lawyer. We answer your own assessment in writing.
AA-05 Is the accuracy of the software measured and published?Yes Statement reading’s precision and coverage, per category, refreshed with every release. Check

Application and interface security AIS

QuestionAnswer
AIS-01 Is the software tested automatically before release?Yes More than 11,000 automated tests run on every push; a failure stops the deploy. Check
AIS-02 Do you use third-party code libraries?No None in the running software: every line is ours. The one tool beside it, Wrangler, which deploys it, is pinned to an exact version with a lockfile. Check
AIS-03 Is every API call that carries data authenticated?Yes With a key signed with HMAC-SHA256, scoped to one lender and to live or test, expiring and revocable. Check
AIS-04 Are webhooks from suppliers verified?Yes Identity and payment webhooks are signature-checked and refused when more than five minutes old.
AIS-05 Do your pages restrict what can run in them?Yes A strict content security policy on every page: no inline script, no framing, and no third-party script except Cloudflare’s cookieless visit counter. Check
AIS-06 Has the code had a security review?Partly Internal only. 29 September 2026: seven issues, each fixed with a test. 11 November 2026: every high and medium finding in the software fixed and tested. No independent review yet.

Business continuity and resilience BCR

QuestionAnswer
BCR-01 Is availability committed in the contract?Yes 99.5% each calendar month, with service credits of 10% to 50%, and a right to terminate after three months in a row below 99%. Check
BCR-02 Is the hosting redundant?Yes The software runs across Cloudflare’s network and a failed location is routed around. There is no server of our own. Check
BCR-03 Are customer records backed up?Yes They are in the lender’s own database: restorable to any minute of the last 30 days on a paid plan (7 on the free plan), and copied out at least monthly with the export tool we provide.
BCR-04 Can a release be rolled back?Yes To the previous release, in minutes. Check
BCR-05 Are recovery time and recovery point objectives set?No Not as contract terms. A release rolls back in minutes, and a lender’s records restore to the minute.
BCR-06 Can we keep using our data if Creditcrest stops?Yes Records, evidence and signed documents are in the lender’s own database and stay readable. There is no source-code escrow. Check
BCR-07 Can money movement be stopped at once?Yes One switch pauses every payout and repayment, for every lender, within 30 seconds.

Change control CCC

QuestionAnswer
CCC-01 Is every production change tested and recorded?Partly A push to the main branch deploys only if every test passes. The Cloudflare account’s owner can also deploy by hand, to fix forward in an incident. Every deploy is recorded and can be rolled back.
CCC-02 Are customers told before a change that alters results?Yes A change that moves a figure for the same input is announced before it takes effect, with what moved and why. Check
CCC-03 Do changes to a lender’s controls need approval?Yes A requester and a different approver. Check

Cryptography and keys CEK

QuestionAnswer
CEK-01 Is data encrypted in transit?Yes HTTPS only, over TLS 1.2 or newer. Plain HTTP is redirected, and browsers are told to use HTTPS only (HSTS). Rated A+ by Qualys SSL Labs and A+ by securityheaders.com on 11 November 2026. Check
CEK-02 Is data encrypted at rest?Yes By the platform holding it: Cloudflare for ours, the lender’s own provider for its records. Check
CEK-03 Are secrets kept out of the source code?Yes They are encrypted Worker secrets in Cloudflare. Rotating the key-signing secret ends every key at once.
CEK-04 Can a record be shown to be unaltered?Yes Each lender’s records carry a hash chain, checked whenever they are read. Check

Datacentre security DCS

QuestionAnswer
DCS-01 Do you run your own datacentre or servers?No Physical security is Cloudflare’s; its compliance documents are available from Cloudflare. Check

Data security and privacy DSP

QuestionAnswer
DSP-01 Do you store borrower data?No A statement is read in memory and gone when the request ends. Applications, loans and documents live in the lender’s own database. Check
DSP-02 Is retention defined?Yes Request logs (time, address, status) for no more than 30 days, never a body; sandbox call records for 35 days; invoicing counts for 7 years, naming the lender and never a borrower. Check
DSP-03 Can data be processed outside Australia?Yes Cloudflare is a global network, usually handling an Australian request in Australia; our storage is placed in Oceania. Some suppliers are in the United States and Spain. Check
DSP-04 Is customer data used to train or tune anything?No Never for anyone else, and no hosted AI model is called. A model fitted to a lender’s own book (Score, AI and Data Advisory) is for that lender alone, and stays its own. Check
DSP-05 Is data sold or used for marketing?No Nothing is sold. Check
DSP-06 Is personal information ever put in a web address?No So no link can leak one. Check
DSP-07 Is data returned or deleted at the end of the contract?Not applicable We hold none to return. Request logs age out within 30 days, and sandbox call records within 35; invoicing counts are kept 7 years for tax. Check
DSP-08 Do you give us wording for our own privacy policy?Yes The overseas-disclosure wording (APP 8) a lender needs, with each supplier and its country. Check
DSP-09 Do you have a privacy policy?Yes For Creditcrest’s own handling of personal information. Check

Governance, risk and compliance GRC

QuestionAnswer
GRC-01 Is a named person accountable for security?Yes A director of Creditcrest Technologies Pty Ltd, at security@creditcresttechnologies.com.au. Check
GRC-02 Are security policies written down?Partly The controls are written beside the code they govern, and the incident runbook is written. A separate policy set was drafted on 11 November 2026 and is not yet approved.
GRC-03 Is Creditcrest licensed or regulated as a lender?No Not a credit provider or credit assistance provider, and no credit licence. The lender’s licence governs its lending. Check
GRC-04 Has the contract been reviewed by a lawyer?No Not yet. It is a draft, and is not offered for signature until it has been. Check

Identity and access IAM

QuestionAnswer
IAM-01 Can our staff sign in without a password that can be phished?Yes With a passkey, which can’t be phished and is both factors on its own. A lender can require passkeys of the staff who record funding. Check
IAM-02 Do sessions end when someone leaves?Yes Deactivating a member of staff ends their sessions. Sessions are HttpOnly, Secure, SameSite=Strict cookies. Check
IAM-03 Is access by role?Yes Each member of staff has a role, and only a senior records funding. Raising someone to senior or admin waits for a second administrator where the lender has one; the history records who did it.
IAM-04 Is one lender’s data kept from another’s?Yes Every key and session is scoped to one lender, and each lender’s records are in its own database, in its own account. Check
IAM-05 Do borrowers sign in without a password?Yes With a one-time code or a passkey. Check
IAM-06 Must every member of our staff sign in with two factors?Yes Every one, in every role, with no setting to turn it off: a passkey, or a single-use link to their work address and a code from an authenticator app. Check

Interoperability and portability IPY

QuestionAnswer
IPY-01 Is there an API for each product?Yes Every product is an API, documented with a sandbox. Check
IPY-02 Can we export our data?Yes It is already in your own database, and the records service comes with an export tool.

Infrastructure security IVS

QuestionAnswer
IVS-01 Are there servers or operating systems to patch?No The software runs on Cloudflare Workers. Check
IVS-02 Are test and production kept apart?Yes Test keys, the sandbox and suppliers’ test accounts are separate, and a live lender never reads test settings. A lender’s test key’s codes are sent for real; the free sandbox key reaches no supplier.
IVS-03 Are calls rate-limited?Yes Every keyed call: 60 a minute for a test key, 600 for a live one. Codes: 10 a minute from one address (120 from a lender’s server); texts only to Australian mobiles, five a number a day.

Logging and monitoring LOG

QuestionAnswer
LOG-01 Is the service monitored?Yes Checked every ten minutes; a failure alerts by email and shows on the status page. Check
LOG-02 Is it also monitored from outside?Yes UptimeRobot checks the health address from outside Cloudflare and alerts us if it fails or stops answering (since 30 September 2026). Its public status page is not set up yet. Check
LOG-03 Are request bodies logged?No Logs keep the time, the address and the status, for no more than 30 days. Check
LOG-04 Is there a record of who did what?Yes Each action on an application or a loan is an event naming who and when, in the lender’s own hash-chained records.

Security incidents SEF

QuestionAnswer
SEF-01 Is there an incident response plan?Yes A written runbook: what to check, how to roll back and pause payments, who to tell and by when. Check
SEF-02 Is a breach notified within a set time?Yes Within 24 hours of becoming aware, to each affected lender, with what it needs for its own assessment. Check
SEF-03 Are outages communicated?Yes On the status page and its feed, and by email to each affected lender as soon as confirmed. Check
SEF-04 Is a written account sent afterwards?Yes Within a week, to each affected lender: what happened, what it touched, and what changes. Check
SEF-05 Has there been a breach?No None. No lender’s or borrower’s real data has been processed yet. Check

Supply chain STA

QuestionAnswer
STA-01 Are your sub-processors listed?Yes Each with what it does, the data it receives, where, and on whose account. Check
STA-02 Are we told before a new one?Yes 30 days’ notice by email, on the list and in its feed. A lender that objects may end the agreement under its clause 11.2. Check
STA-03 Can we contract a supplier ourselves?Yes Identity checks, bank data and payments can run on the lender’s own account; credit reporting bodies always do. Check

Threats and vulnerabilities TVM

QuestionAnswer
TVM-01 Can a researcher report a vulnerability?Yes To security@creditcresttechnologies.com.au, as security.txt says; acknowledged within one business day. Check
TVM-02 Is there a bug bounty?No Reports are welcome; none is paid. Check
TVM-03 Are dependencies kept patched?Yes The running software has none. The deploy tool and GitHub’s actions are pinned, by lockfile and by commit, and moved on purpose to releases at least two weeks old. Check

Not answered here yet

These need answers this page cannot check against the software. Ask, and we answer in writing.

  • People (HRS): Background checks, security training and confidentiality agreements for anyone with access to production.
  • Identity and access (IAM): Multi-factor sign-in on Creditcrest’s own administrative accounts.
  • Endpoints (UEM): How the computers that hold signing secrets are secured.