Retirement Savings Calculator

Privacy Policy

Last updated June 18, 2026

This is a personal project I built to visualize compound interest and retirement projections. To understand how people are using the tool and to improve it over time, I collect a small amount of anonymous analytics. This page explains exactly what gets collected, why, where it lives, and how you can opt out.

What I collect

When you use the calculator, the following data is sent to my analytics backend:

• Anonymous visitor ID — a random UUID generated in your browser, stored locally for 30 days. No name, email, or account is attached.
• The calculator inputs you save — starting amount, rate, years, contributions, and yearly spend, but only if you click the Save button. Typing in the inputs without saving is not stored.
• Scenario names you save — the label you give a saved scenario.
• Device and browser type — whether you're on touch or mouse, and which browser family (Chrome, Safari, etc.). Not your exact device model.
• Referrer hostname — where you arrived from (e.g. github.com), but not the full URL.
• Page interaction events — page view, page exit duration, recalculations, insight cards focused, and mobile sheet opened.

What I don't collect

• Your name, email, IP address, or any personally identifying information.
• Anything you type into the calculator that you don't explicitly save.
• Cookies for tracking across other sites.
• Data from any third-party advertising or marketing network — there are no ads here.

Why I collect it

To understand:

• Which of the financial insights (Lift Off, Coast FI, Lean FI, etc.) people find most useful.
• How long visitors spend with the tool before leaving.
• What proportion of visitors are on mobile vs. desktop, so I know which experiences to polish.
• How many people make it through to actually saving a scenario.

That's it. The data informs improvements to the tool — it's not sold, shared, or used for marketing.

Where it's stored

Events are stored in a Supabase database hosted in the United States. Access is restricted to me (the developer) via authenticated login. The database is governed by Supabase's own privacy and security practices.

How long it's kept

• Your local visitor ID expires from your browser after 30 days. After that, you become indistinguishable from a brand-new visitor.
• Event records in the database are kept indefinitely so I can look at long-term trends. They can't be tied back to you personally once your visitor ID rotates.

What's stored on your device

Two values are written to your browser's localStorage (not cookies):

• calc_visitor_id — the anonymous UUID.
• calc_visitor_id_issued_at — when the UUID was generated, for the 30-day rotation.
• calc_analytics_consent — your tracking preference (accepted or declined).

Your rights

You can:

• Opt out using the button below. Once declined, no further events will be sent.
• Erase your local identifier by clearing your browser's site data for this domain.
• Request deletion of past events by emailing me. Provide your visitor ID (or approximate visit timeframe) and I'll remove matching records.

Contact

If you have questions about this policy or want past events deleted, email me at amandaraedev@gmail.com.

Source code

The full source code (including the analytics implementation) is public at github.com/amandarae220/Calculator2.0. If you want to verify what's described above is what actually runs, the relevant file is assets/analytics.js.