Security
Security, explained plainly
Finance involves sensitive information, so we'd rather explain our approach in plain language than hide behind badges. Here's how Findnance treats your data.
Encryption in transit
All traffic between your browser and Findnance is encrypted over HTTPS (TLS). Nothing you type in the conversation travels in the clear.
We collect the minimum
Data minimisation is a design rule, not an afterthought. The conversation asks only what's needed to calculate indicative options and, if you choose to proceed, to brief your specialist. We don't ask for tax file numbers, bank logins or documents at the quote stage — and we never ask for passwords.
Role-based access
Access to customer information is limited by role. A finance specialist sees the leads assigned to them; administrative access is restricted and reviewed. Nobody has access “just in case”.
Audit logging
Significant events — a quote generated, a status change, an assignment to a specialist — are recorded in an event log against your enquiry. If something needs to be traced or explained later, there's a record of what happened and when.
Consent records
When you agree to something — being contacted, having an application lodged — we store a consent record capturing what you agreed to, the wording you saw, and when. Consent is explicit and versioned, never assumed.
Where your information actually goes
What you enter is written to a PostgreSQL database we control, not held in a browser or a spreadsheet. The privacy policy sets out how long each kind of record is kept and why. Nothing expires on its own: there is no automatic sweep, and a record is deleted when you ask us to delete it, by a person. Your enquiry is also sent to the licensed brokerage that handles it — that transfer is the point of the service, and the privacy policy names exactly what travels with it.
Related reading
For what we collect and why, see the privacy policy. For how we're paid, see disclosures.