ForeA

Privacy

What we collect, what we don’t, and where your numbers actually go.

Last updated 2026-07-24.

Who processes this data

This notice is issued by ForeA Technologies, the data fiduciary for ForeA Tools. Contact: hello@forea-tech.com.

[Registered address: Bengaluru, India — full street address and PIN code to follow once a registered office is set up. Not an oversight, a known interim state; see the grievance officer page for the same note.]

The notice, itemised

Personal data collected	None. Every calculator runs entirely in your browser — your inputs are never sent to a server to be calculated, and we never see your corpus, expenses, or results.
Non-personal data collected	Two tool-slug strings and a boolean per “next decision” link click (for example, `corpus-target → sip-to-goal`, whether numbers were carried across); and, separately, a page path per page load (for example `/tools/emi-calculator`), so traversal counts have a denominator to be interpreted against. Both are aggregate only — no identifier ties two events to the same visitor.
Lawful basis & purpose, per activity	Traversal analytics (tool-to-tool click logging): to see which decision paths people actually follow, so the connected journeys can be improved. Pageview analytics (page path per load): to give traversal counts a denominator to be interpreted against. Both are anonymous, aggregate click/visit-counting — no personal data is processed by either activity, so no consent-based lawful basis is engaged (see “Right to withdraw consent” below).
Security safeguards	HTTPS is enforced everywhere, with HSTS (`Strict-Transport-Security`) telling browsers to never fall back to plain HTTP. `X-Content-Type-Options`, `Referrer-Policy`, `Permissions-Policy`, and `X-Frame-Options` are set on every response. A Content-Security-Policy is defined and currently running in Report-Onlymode (logged, not yet enforced) while a few components still need a nonce-based rework before it can be turned on without breaking them — stated here as what’s actually true today, not what’s aspirational. Beyond headers: no personal data is ever transmitted to a server (every calculation runs in your browser) or stored, and no identifier is held anywhere that could re-associate a visitor across visits.
Retention	90 days. Both datasets are stored in Cloudflare’s Workers Analytics Engine, whose stated retention period is three months.
Sharing / processors	Only one processor, Cloudflare, in three distinct roles: Cloudflare Workers: hosts and runs the application itself (every page you load). Cloudflare Analytics Engine: stores the two aggregate datasets described above (traversal clicks, pageview paths). Cloudflare’s network/CDN:serves the site from the edge location nearest you and provides the HTTPS/HSTS layer described under “Security safeguards”. No other processor is involved — no ad network, no third-party analytics vendor, no email or CRM platform in this data path.
Cross-border processing	This site runs on Cloudflare’s global network, which serves and processes requests from whichever edge location is nearest to you — not confined to one country or region. We haven’t configured Cloudflare’s data-localization options, since there’s no personal data collected that would need geographic restriction.
Your rights	See your data rights for all six, and how to exercise them.
Right to withdraw consent	No consent is collected from you, because no personal data is processed — there is nothing to withdraw. Stated here explicitly rather than left implicit, since Section 11(3) requires the withdrawal route to be as easy as giving consent was: if you believe that’s wrong, or that something here is in fact processing personal data, use the same grievance route as any other complaint.
Grievance route	See the grievance officer page for who to contact and the response timeline.
Children	This site isn’t directed at children under 18. We don’t knowingly collect data from anyone, of any age, and don’t process data in ways that would require verifiable parental consent.
URL parameters	Your numbers travel between tools as URL query parameters — visible in your address bar, saved in your browser history, and included if you copy or share that link. Share deliberately.
Last reviewed	2026-07-24 — updated whenever what the code actually does changes.

In plain language

Every calculator on this site — including the Retirement Planner’s Monte Carlo simulation and the Retirement Corpus Target Calculator’s stress-tested search — runs entirely in your browser. This is a factual statement about how the code works, not a promise layered on top of it: nothing in this site’s code makes a network request to compute a result.

We count page visits with a small first-party beacon (see src/lib/analytics/pageview.ts) that reports only the path you’re on — no cookie, no browser storage, no identifier, so two page loads can never be linked to the same visitor. It exists purely as a denominator: a traversal count is uninterpretable without knowing roughly how much traffic the site gets overall. Separately, the traversal analytics described above logs tool-to-tool clicks in aggregate. See the cookie policyfor why there’s no consent banner.

We don’t use cookies or browser storage of any kind — there is genuinely nothing stored on your device by this site beyond what your browser caches for performance.

Questions

If anything here is unclear, or you think we’ve gotten something wrong, write to hello@forea-tech.com, or see the grievance officer page for formal complaints.