TL;DR. The Share button, beside the success-rate badges at the top of the Proof view, creates a public read-only URL for the plan you are looking at. Anyone who opens it - no account needed - sees your success rate, all the summary charts, the year-by-year deep dive, and a summary of the plan's assumptions (the household and any dependents, balances and their allocation split, the spending plan and its settings, and income and expense events with their schedules and routing). Nobody can edit anything, run simulations, or see who you are. It is built for "critique my plan" posts on forums like r/financialindependence, r/fire, Bogleheads forums, where a link beats a stack of screenshots.

What viewers see, and what they cannot

The share page is the real Proof view, read-only: the success-rate badges, every chart, the cycle selector, and the year-by-year detail for every cycle - a reader can move the cycle slider to any historical window and open its full drill-down, exactly as you can. Above it sits a plan-assumptions panel so readers can judge the inputs, not just the outcome. Viewers cannot edit inputs, run What-If comparisons, download reports or spreadsheets, or reach any other part of your account. The link never exposes your email, login, or anything outside the shared plan.

Only the first cycle's detail is stored with the link; opening another cycle for the first time takes a few seconds while it is worked out, then it is instant for everyone afterwards. It is always computed from the snapshot you shared, never from your live plan - so a reader's drill-down can never disagree with the page around it, even if you have edited the plan since.

Names are redacted by default

Two toggles on the share panel control redaction, and both start on. With "Redact our names" on, people render as Person 1 and Person 2 instead of your inputs, and any dependents render as Dependent 1; with "Redact account and event labels" on, your own labels render as generic type labels like Brokerage Account 1 or Pension 1. Switch a toggle off to show the real names or labels. Changing a toggle on an existing link republishes it immediately - viewers will see the updated plan on their next load. Dollar amounts are always shown; they are the point of sharing.

The views counter

The share panel shows how many times your link has been opened, with the most recent visit on hover. It counts page loads in a real browser - not unique people, so one reader refreshing counts more than once - and the preview bots that Reddit, Discord, and similar sites send when a link is posted do not count, because they never load the plan data. The counter keeps accumulating across snapshot refreshes; closing the link and sharing again starts a fresh count with the new URL.

Closing a link

Close link on the share panel turns the URL off permanently - visitors see a friendly "closed by its owner" page instead of your plan. Sharing again afterwards creates a fresh URL; the old one never comes back to life. Each plan has at most one active link at a time.

Sharing a Risk-Based Guardrails plan

A guardrails plan does not spend a fixed amount - it re-solves your spending each check-in year - so the shared copy has to be solved from scratch with your names removed. That takes a few minutes, and it runs in the background: the share panel says Preparing your share link and updates itself when the copy is ready. You can close the window and come back; nothing is lost. Until it lands, anyone opening the URL sees a "still being prepared" page.

The shared page carries a read-only Risk-Based Guardrails spending panel: your target chance of success, how often the plan re-checks, and the median spending, 10th-to-90th percentile range and guardrail action for each year across every scenario tested. Changing a redaction toggle rebuilds the copy, so it goes back to preparing for a few minutes - readers keep seeing the previous version until the new one is ready.

Limits

• Share links cover standard historical runs and Risk-Based Guardrails runs. On Monte Carlo results the Share button shows disabled with a note saying so.
• Sharing a Risk-Based Guardrails plan needs a Pro subscription, because building the shared copy re-solves the plan. Sharing a standard historical plan does not.
• The first open of a cycle other than the first takes a few seconds; after that it is served instantly to every reader.
• Names you give custom assets are not redacted - if a custom asset name is sensitive, rename it before sharing.
• Share pages ask search engines not to index them, and the URL is unguessable - but anyone who has the link can open it. Share it where you are comfortable.