Privacy
Two different people interact with this platform, with very different exposure. Somebody using a calculator supplies financial figures and is never identified. Somebody with an account is identified by an email address and has configuration stored.
Everything below describes what the software actually does. Where a claim is enforced by a test or a database constraint, that is stated.
If you use a calculator
What you type is not stored anywhere. Loan amounts, salaries, property values, deposits, interest rates, and every result computed from them are processed in your browser and stay there. They are not sent to a server, not written to a database, not logged, and not put into a link.
That is enforced structurally rather than by policy. The analytics event contract has a fixed set of permitted fields, none of which can carry a monetary value; a recursive scan rejects any batch containing a forbidden key; and a release-blocking test asserts that no financial value can reach the events table. The database schema has no column that could hold one.
What is recorded
When a calculator is embedded on a business’s website, that business can see how it is being used. The events recorded are: widget_loaded, calculator_viewed, calculator_started, calculator_calculated, calculator_recalculated, calculator_switched, cta_viewed, cta_clicked, embed_error.
Each carries, at most:
Which calculator, which site, which embed
Resolved on the server from a public embed key, never from anything your browser claims.
An anonymous session identifier
A random value for one visit, so a view and a click from the same visit can be counted as one journey. It is not a cookie, not a fingerprint, not derived from your IP address, and not linkable to you or to any other visit. A “session” in the reporting is a visit, not a person.
A coarse source and campaign, when present
Where the visit came from, at the level of a referring channel — not a full URL and not a search query.
Layout and timestamp
Which widget arrangement was shown, and when.
What is never recorded
Any calculator input or result. Your name, email address, phone number or postal address — there is no field for any of them and no form that asks. Your raw IP address. No cookie is set for analytics, no fingerprinting is performed, and no third-party analytics is loaded at all: no Google Analytics, no Meta Pixel, no session recorder, no external tag of any kind.
Raw events are retained for 90 days. Deletion after that is run by hand rather than on a schedule, because no scheduler exists yet — so a row may survive past 90 days until it is run. It carries no financial figure and identifies nobody either way.
If you have an account
An account holder is a business customer, and more is necessarily stored:
Your email address
Used to sign you in and to reach you about your account. There is no password — authentication is a single-use link sent to that address, so no password of yours is stored here and none can be stolen from here.
Your session
A cookie holding a random value, with the corresponding hash stored on our side. The cookie carries nothing about you, and signing out deletes the record rather than only clearing the cookie.
Your account and membership
Which business account you belong to and what role you hold in it.
Your configuration
Your business name, the websites you have registered, your branding, and the embeds you have saved.
Billing identifiers, if you subscribe
A customer and subscription identifier from the payment provider, the current status, and the renewal date. No card details are stored here — no number, no expiry, no name on the card, no billing address. Those stay with the payment provider, and this platform never sees them.
If you embed calculators on your site
Your visitors’ financial inputs never reach us, so they are never in a system you did not choose. The engagement metrics you see are counts of what happened, not records of what anybody entered.
The call to action sends a visitor to a destination you configure — your page, your phone number, your email. Nothing is captured in between, and no visitor figure is ever put into that link. If you collect details after that, you are collecting them, on your own site, under your own privacy policy.
What this page is not
This is a description of how the software behaves, written so it can be checked. It is not a legal privacy policy, and it makes no claim about compliance with the Privacy Act 1988, the Australian Privacy Principles, the GDPR or any other regime — no such assessment has been performed, and claiming one would be exactly the kind of unsupported statement this page is written to avoid.
A reviewed privacy policy is required before this product is sold, and it will replace this page rather than sit alongside it. In the meantime, everything above is accurate about what the system does.