Your financial inputs stay in the browser.

Calculator financial values are processed locally in your browser. We do not send your income, assets, liabilities, net worth, age, percentile, Financial Position Score, or recommendation details to our analytics database.

We collect limited anonymous product-usage events through our own same-origin server API, and only our production website stores them. An event records what happened (for example, a page view or a completed calculation) and, where relevant, the site language, the type of page, which guide was opened, which language you switched to, which kind of comparison was shown (Financial Position Score, percentile, benchmark, or unavailable), which supported comparison dataset was used (United States, Canada, United Kingdom, Australia, or Germany; other countries are not recorded), and whether a next-step suggestion was shown.

Events are grouped by a random session identifier that exists only in the open page’s memory. It is not saved in cookies, localStorage, sessionStorage, or any other browser storage, and a new one is created when the page is reloaded or the language is changed. It is not an account, persistent identifier, device ID, or financial profile.

Challenge IDs are anonymous invitation identifiers, not user identities. Recommended-tool analytics on guides record only the configured tool ID (never the link address) and the anonymous fields described above. When a partner or suggested-tool card is shown with your next step, or you open it, we record only which configured provider it was, the site language, and which comparison dataset was in use (the country dataset selected in the calculator, not where you are). These provider events carry no session identifier, and no income, assets, debts, net worth, score, indicators, recommendation category, or link address is sent with them. Provider links go through an INVERSTACK address (/go/…) that forwards you to the provider and records the click in the same way.

Supabase is used server-side for anonymous event persistence. Analytics validation rejects financial fields and unknown event fields. Hosting and network infrastructure may process normal technical request information, even though the application does not intentionally store it in analytics tables.

Optional partner websites have their own privacy practices. Review their policies before choosing to visit one.