Effective and reviewed: October 12, 2026
Site delivery
Our hosting and security providers may process technical data needed to deliver and protect the site, including IP address, browser type, requested pages, timestamps and diagnostic logs.
Newsletter
When you subscribe, your email address is sent to Buttondown so it can deliver the newsletter and manage confirmation and unsubscribe requests. New subscriptions use double opt-in: Buttondown asks you to confirm the address before regular emails are sent. You can unsubscribe through the link included in every newsletter.
Analytics and advertising
If configured, Rich2Fire uses Google Analytics 4 to understand aggregate readership and Google AdSense to display advertising. These optional services remain disabled unless you accept them through the site’s privacy controls. AdSense is additionally disabled until a Google-certified consent management platform has been configured for regions where it is required.
Article and tool view counts
Article and tool pages use a necessary same-site request to display an approximate aggregate view count. Session storage remembers only that the current browser session has already counted a particular content key, which prevents repeated refreshes from immediately increasing the total. The server sends only that content key—not your email address or a visitor identifier—to CounterAPI and receives the aggregate count.
Your consent choice
Your choice is stored in your browser’s local storage under rich2fire-consent-v2. You can reopen “Privacy choices” at the bottom of any page and change the selection. Choosing necessary functions only does not prevent access to the site.
Optional FIRE Calibration research
The FIRE planning data saved under rich2fire-plan-v1 stays in this browser. It can include a Five Paths baseline, a Calibration draft, saved Calibration snapshots and optional context retained from an earlier Calm Planner migration. You can delete individual snapshots in Calibration, clear the numerical baseline in Five Paths without deleting those snapshots, or remove the whole record through your browser's site-data controls. Saving a plan locally is not the same as sharing it for research.
Research sharing is active only when the in-product status explicitly says that it is ready. In every other state, the sharing control stays unavailable and no Calibration research contribution is transmitted. A readiness check is an ordinary operational request and may appear in infrastructure logs, but it does not contain your local plan or Calibration answers.
When sharing is ready, each contribution requires a separate, explicit choice at the time of sharing. That choice is independent of analytics and advertising consent; accepting either of those services will not enroll you in research or submit a plan.
The research data dictionary is deliberately narrow: a broad FIRE path, broad reason for recalibrating, the four Calibration signals, the resulting decision, a structured reversible experiment and, if you later choose to provide it, a structured outcome. A contribution does not include an email address, account, free-text response, exact financial amount, exact local date, local plan or snapshot ID, or persistent participant identifier.
The research record does not store an IP address. Hosting, firewall, database and security systems may still process network and request metadata, including an IP address, in operational logs used to deliver and protect the service. Those logs are not part of the research dataset and are not used to enrich a contribution. For that reason, Rich2Fire does not promise absolute anonymity.
A raw contribution is retained for no more than 30 days, then deleted after it has either been excluded or included in a thresholded aggregate. Public insights require at least 100 contributed snapshots overall and at least 20 observations in every exhaustive cell of a published dimension; otherwise that dimension is not published. Individual records are never published.
After a successful share, the service returns a deletion receipt and secret once and keeps them only in this browser; the research database stores only a non-recoverable verification value. During the raw-retention window, the interface can make a best-effort deletion request using that secret. If the browser copy is lost—for example, because site data is cleared—we cannot reliably verify a later request. Once the raw record has expired or its contribution has been combined into an anonymous aggregate, it can no longer be traced back and removed individually.
See the current public research status and aggregation method →
Affiliate links and external sites
Affiliate and other external links take you to third-party websites with their own privacy practices. If analytics is accepted, Rich2Fire records an aggregate affiliate-click event containing the destination and link label; purchase information is not collected by Rich2Fire through that event.
Your data choices
You may withdraw consent through the site controls and unsubscribe from the newsletter at any time. Requests to access, correct or delete subscriber information can be sent through the contact method published on the About page.
Changes
This notice will be revised when services or processing practices change. The date above identifies the current version.