Security Information
Data handling, controls and the evidence available to inspect.
Security evidence summary: 13 August 2026.
At a glance
Calculating does not send your estimate to a firm. Saving or emailing a summary uses our server. A firm Contact Request is a separate, consented service where intake is available. The details and limits of each flow are below.
This page describes application design and available evidence. It is not a security certification, independent assurance report, security schedule, or contract.
1. What happens to your information
Calculator only
The arithmetic runs in your browser without an account, name or email address. Ordinary in-progress figures are not intentionally written to the application database. Restore and demonstration features may use storage on your device. The site still makes network requests, including availability checks and restricted operational events; browser calculation does not mean the site is offline or makes no analytics requests.
Save a PDF or email a summary
Both choices send the submitted calculation information to our server to prepare the PDF. A download returns to your browser. An emailed summary also uses the address you provide and an email-delivery provider. This does not create a firm Contact Request. Minimal delivery records exclude calculator values and support abuse prevention and operational diagnosis.
Request contact from a named firm
Where firm intake is available, separate verification and explicit consent are required. Authorised firm staff can then access the permitted estimate summary, selected review context, safe-contact preference and contact and consent records. Ordinary requests exclude raw income, raw care values and unrestricted case narrative. Read the collection notice and the named firm's privacy policy before choosing to share.
The Privacy Policy is the detailed source for collection, disclosure, retention and your privacy choices.
2. What the evidence establishes
Code and local tests: show how the application is designed and tested. They do not establish that controls are deployed or operating effectively in production.
Live operation: provider settings, key custody, account access, processing locations, backups, deletion, monitoring and incident handling require separate operational evidence. This page does not verify those activities.
Independent assurance: this summary supplies no ISO 27001, SOC 2, penetration-testing report, government approval or legal compliance certification. It makes no guarantee of security or evidence of customer adoption.
3. Access and protection
The current code includes these protections; this is not a claim about every historical record or a live environment.
- Administrator passwords are stored as one-way hashes, rather than readable passwords.
- Multi-factor authentication secrets are encrypted and recovery codes are hashed.
- Defined Contact Request content is encrypted. Contact lookup is scoped to the receiving firm.
- Firm access checks the signed-in user, their role and their firm.
- Exports require a Firm Admin password confirmation and an expiring download permission tied to that user and firm.
Technical control details and encryption limits
Administrator passwords use salted scrypt hashes. The defined Contact Request payload and multi-factor authentication secrets use AES-256-GCM. Exact contact lookups use firm-scoped HMAC values; export download tokens are stored as hashes.
Not every database field is separately encrypted by application code. These controls do not establish transport encryption, provider encryption at rest, production key handling, backup protection, logs, support access or deletion from provider backups.
4. Providers and retention
The Privacy Policy's provider register records disclosed purposes and location and retention dependencies. A listed provider does not prove the settings, contracts, processing region or access controls of a live account. This page makes no Australia-only processing claim.
The policy assigns new Contact Requests a 180-day retention period unless deleted earlier or subject to a documented legal hold. That rule is not proof that every historical or live record has been deleted. Provider backups, logs, exports and copies held by a firm are separate; deleting the platform copy does not establish their deletion.
Read the retention policy for the detailed rules. Recovery targets, monitoring and incident-response operation are not independently assured by this summary.
5. Evaluating for a firm
Match the evidence to your proposed use: what clients would share, who could access it, which providers would process it and how retention and offboarding would work. Firm intake requires separate activation; a fictional demo or an implemented workflow does not establish availability for your firm.
Your firm remains responsible for its received copy and its professional obligations. Firm-specific commitments depend on executed written terms. This page does not promise a security schedule, data-sharing agreement, questionnaire response, response time or monitored security mailbox for a particular review.
6. Policies and next steps
Privacy Policy — detailed handling rules and privacy requests.
Terms of Service — service scope and obligations.
Methodology — calculation sources, scope and evidence.
About the operator — identity, background and accountability.