Privacy Policy

Browser Local Storage

retireclarity uses your browser's localStorage to save your inputs, settings, and optimization results. This data:

• Stays exclusively on your device
• Is not accessible to us or any third party
• Persists between browser sessions for your convenience
• Can be cleared at any time using your browser's settings

What Gets Stored Locally

The following information is stored in your browser only:

• Personal information (age, retirement age, filing status)
• Account balances (cash, brokerage, tax-deferred, Roth)
• Income sources (salary, Social Security, pensions)
• Expense amounts and categories
• Investment assumptions and Roth conversion settings
• Optimization results and timing strategies
• Display preferences (today's dollars vs. future dollars toggle)

Clearing Your Data

You can clear all locally stored data at any time by clearing your browser's localStorage or browsing data. Instructions vary by browser:

• Chrome: Settings → Privacy and security → Clear browsing data → Cookies and other site data
• Firefox: Settings → Privacy & Security → Cookies and Site Data → Clear Data
• Safari: Preferences → Privacy → Manage Website Data → Remove All

Page views & feature counts — Umami (cookieless, via our own domain)

Both are sent through our own domain (first-party) to Umami and are cookieless — we are not hiding that it is Umami; routing the counts through our domain simply keeps them from being silently dropped by ad and tracker blockers.

Anonymous page views. When you open a page we record an anonymous view of it: the page path (no query string), the referring site (for example a search engine or a link that sent you here), your browser language, a coarse screen size, and an approximate country (derived by Umami from your IP address at the moment of the request and not stored by us). There is no cookie, no unique identifier, and nothing tying one view to another or to you.

Feature counts. We also count which features get used. Each event is a plain name plus, at most, a few coarse labels chosen from a fixed list we publish below — never a number, a date, or anything you typed. There are exactly 37 of them, and this is the complete list, with every label each one can carry:

• verdict_shown — A retirement projection produced a real verdict (not an empty form).
  • Records kind — which of the three verdicts was shown. One of: on-track, funded-through, funds-short.
  • Records persona — which life stage the visitor picked. One of: working, retiring-soon, retired, unknown.
• plan_created — A first plan was saved on the device.
  • Records persona — which life stage the visitor picked. One of: working, retiring-soon, retired, unknown.
• plan_exported — A plan/backup file was exported.
• progress_return — A returning visit to the Progress page (coarse cadence bucket only).
  • Records bucket — how long since the first visit. One of: first, day-1, week-1, week-2-plus, month-2-plus.
• scenario_compare_used — The scenario-comparison feature was used.
• multiplan_created — An additional (2nd+) plan was created.
• report_or_export_used — A report or CSV export was generated.
  • Records surface — which surface produced it. One of: print_report, csv_export.
• demo_viewed — The sample-household demo was shown on a tool page.
  • Records page_class — which class of page showed the sample. One of: calculator, tax_optimizer, chance_of_success, progress, landing_roth, landing_monte_carlo, landing_social_security, landing_withdrawal, landing_fire, landing_aca, other.
• demo_persona_picked — A sample household was selected in the demo.
  • Records sample_persona — which sample household was selected. One of: couple-near-retirement, recently-widowed, sandwich-generation, fire-early-retiree, fire-accumulator, at-risk.
• start_from_sample — The visitor started a plan from the sample household.
  • Records sample_persona — which sample household was seeded. One of: couple-near-retirement, recently-widowed, sandwich-generation, fire-early-retiree, fire-accumulator, at-risk.
• use_own_numbers_clicked — The visitor chose to enter their own numbers from the demo.
• roth_optimizer_run — The Roth-conversion optimizer was run.
  • Records run — first run of this browser session or a repeat. One of: first, repeat.
• mc_run — A Monte-Carlo simulation was run by the user.
  • Records run — first run of this browser session or a repeat. One of: first, repeat.
• ss_optimizer_run — The Social Security claiming optimizer was run.
• mc_different_markets — A Monte-Carlo run against a different market history.
• mc_bond_optimize — The Monte-Carlo bond-mix optimization was applied.
• account_added — An account was added to the plan (coarse account-type bucket).
  • Records bucket — which kind of account. One of: 401k, ira, roth, brokerage, cash.
• real_asset_added — A real asset was added to the plan (coarse asset-kind bucket).
  • Records bucket — which kind of real asset. One of: home, rental, other.
• liability_added — A liability was added to the plan.
• income_stream_added — An income stream was added to the plan (coarse income-kind bucket).
  • Records bucket — which kind of income. One of: salary, pension, other.
• expense_added — An expense was added to the plan.
• milestone_added — A custom milestone was added to the plan.
• timing_dates_used — A month-precision timing date was set (partial-year proration).
• chart_tab_viewed — A projection chart tab was viewed (coarse tab bucket).
  • Records bucket — which chart tab. One of: balances, cashflow, income, taxes.
• chart_table_toggled — A projection chart was toggled between chart and table view.
• inflation_view_toggled — The inflation (today’s-$ vs future-$) view was toggled.
  • Records bucket — which dollars view (today's or future). One of: today, future.
• onboarding_completed — The onboarding flow completed into a real plan.
  • Records persona — which life stage the visitor picked. One of: working, retiring-soon, retired, unknown.
  • Records surface — which hero the plan was created from. One of: home-hero, calculator.
• cta_click — A named call-to-action into the planner was clicked.
  • Records button — which call-to-action was clicked. One of: blog_calculator, guide_calculator, seo_landing_cta, hero_sample_link, hero_continue_plan, footer_scroll_to_hero.
• plan_imported — A previously exported plan/backup file was imported.
  • Records kind — whether the file held saved plans or a full backup. One of: plans, full_backup.
• settings_opened — The Settings modal was opened.
• analytics_opted_out — The user turned anonymous analytics off.
• analytics_opted_in — The user turned anonymous analytics back on.
• waitlist_shown — The sync-waitlist ask was shown.
• waitlist_joined — A sync-waitlist signup was submitted (never the email address).
• waitlist_dismissed — The sync-waitlist ask was dismissed.
  • Records stage — dismissed on its first appearance or a later one. One of: first_show, repeat.
• annuity_template_used — The annuity payments stream template was used.
• recipe_hsa_clicked — HSA modeling-recipe link clicked from the stream picker.

What Is NEVER Collected

• Any financial data from your inputs — balances, income, expenses, ages
• Anything you type, and any number at all — the counts carry only an event name and labels drawn from the fixed lists above
• Names, emails, or contact information
• Cookies, device fingerprints, or unique user identifiers
• Any way to tie an event back to you or to a specific plan

What a crash report excludes

• No plan data — no balances, income, expenses, ages, or anything you type. Amounts and long numbers are stripped from error text before it is sent.
• No session recording. We do not use Sentry Session Replay or any screen recording — nothing watches or replays what is on your screen.
• No cookies, request bodies, or identifiers. Cookies, headers, request/response contents, and URL query strings are removed from every report.

HTTPS Encryption

The site is served over HTTPS, ensuring that communication between your browser and our servers is encrypted. This protects against man-in-the-middle attacks.

Client-Side Processing

Since all calculations occur in your browser, today your financial data does not travel over the internet. This eliminates the most significant security risk: data transmission.

No Authentication Required

We don't require accounts, passwords, or login credentials. This eliminates risks associated with password breaches or account compromise.

Browser Security

Your data's security depends on your device and browser. We recommend:

• Keep your browser and operating system updated
• Use device encryption (FileVault, BitLocker, etc.)
• Lock your device when not in use
• Use browser profiles or private browsing if sharing a computer

Because all financial data is stored and processed locally on your device, the security of your information depends entirely on the security of your device, browser, and network. You are solely responsible for maintaining appropriate device security, including operating system updates, access controls, and safe browsing practices.