Calcs.finance

Cookies

Cookie Policy

Effective date: 8 June 2026. Last updated: 8 June 2026. This Cookie Policy explains how Calcs.finance uses cookies, local storage, session storage, service worker cache storage, pixels, identifiers, tags, and similar technologies.

Quick summary

Calcs.finance uses browser storage for three practical reasons: to make requested product features work, to remember choices such as currency or saved scenarios, and to measure or fund the free site through analytics and advertising where enabled. Calculator inputs, outputs, saved scenarios, notes, balances, income values, calculator usage details, account state, and local scenario data are not used for ad targeting.

Strictly necessary storage
Security, routing, consent records, authentication callback state, service worker cache, and requested product features can need cookies, local storage, session storage, or cache storage. Blocking this storage can break sign-in, saved scenarios, calculator drafts, currency preference, privacy choices, cached pages, or issue reports.
Optional analytics and advertising
Google Analytics, Vercel Web Analytics, Google AdSense, and Google Privacy & Messaging can use tags, identifiers, cookies, or similar technologies where configured and allowed by consent or privacy choice rules. Google Analytics pageview payloads are limited to route path metadata.
Policy owner review
This policy should be reviewed whenever analytics, advertising, CMP, authentication, saved-scenario, report, cache, or provider settings change. It describes the app source and intended production configuration; account-level provider settings still need policy-owner verification.

What cookies and similar technologies are

A cookie is a small browser file. Local storage, session storage, cache storage, pixels, tags, SDK identifiers, and similar technologies can also store information on a device or read information from it. Some storage is needed to provide a service you request; other storage, especially analytics and advertising storage, can require consent or opt-out choices depending on your location.

First-party product storage

First-party storage is set or read by Calcs.finance in your browser or by app code running on Calcs.finance. Lifetimes can change when features are refactored, but the current product categories are listed below.

Currency preference
The `calcs.finance.currency` browser cookie and local storage value remember the currency symbol or region display you selected. The cookie is first-party, lasts up to one year, and is used for interface preference only.
Calculator drafts and restore state
Calculator pages can use local storage keys for unsaved drafts, restore state, and demo inputs so you can return to recent work on the same device. These records stay on your device until replaced, deleted by the app, or cleared in browser storage.
Saved scenarios
Local scenarios are stored under `financial-calculator.anonymous-scenarios` and can include scenario names, notes, inputs, outputs, assumptions, formula version, timestamps, and calculator type. Local-only scenarios remain on your device until you delete them or clear browser storage.
Favourites and calculator usage
`financial-calculator.favorite-calculators` remembers favourited calculators. `calcs.finance.calculator-usage` supports recent or frequently used calculator navigation. These records are local product convenience data, not ad targeting data.
Service worker and cache storage
The site can register a service worker that caches app shell and static assets for performance and limited offline support. API, authentication, and scenario routes are excluded from the service worker cache.
Issue reports
When you submit an in-product calculator report, the report can include the current URL, calculator values, output, formula version, dataset version, browser diagnostics, viewport, timestamp, and your summary. This is support data, not ad targeting data.

Authentication and account storage

Authentication storage is used only where account, anonymous save, or sign-in features are enabled. These records are needed to maintain requested account or anonymous product state and should not be used for advertising audiences.

Firebase anonymous authentication
`financial-calculator.firebase-anonymous.local-uid` can keep a local anonymous identifier so browser-only or anonymous features can reconnect to the same local product state where enabled.
Amazon Cognito hosted sign-in
Cognito account features can use local or session storage for session information and PKCE sign-in state, plus a temporary first-party callback cookie during hosted sign-in. These records maintain sign-in and protect the account flow.
Account deletion and sign-out
Signing out, deleting local browser storage, or requesting account deletion can remove or start deletion of account-linked records as described in the Privacy Policy. Some security logs, backups, or legal records can remain for limited periods.

Analytics and performance measurement

Analytics helps identify useful pages, broken flows, and navigation patterns. Analytics storage is not used to send calculator input values, outputs, scenario names, notes, user IDs, or account identifiers to ad targeting payloads.

Google Analytics 4
Google Analytics can use first-party cookies and device/browser metadata to measure site interaction where enabled and allowed. Calcs.finance sends pageview metadata as route paths, such as `/calculators/compound-interest`, rather than full URLs with query strings.
Consent-aware analytics
Where consent is required by configuration, the app waits for the consent signal before loading Google Analytics. Consent settings can be updated through available privacy choices.
Vercel Web Analytics
Vercel Web Analytics is loaded in production to measure aggregate traffic. Vercel describes its Web Analytics as cookie-free and based on a short-lived hashed visitor session rather than third-party cookies.

Advertising and consent tools

Calcs.finance is free and may be supported by Google AdSense or other ad vendors where production ads are enabled. Ad storage can be used to serve, personalise where allowed, measure, limit repeated ads, detect fraud, and report aggregate advertising activity.

Google AdSense
AdSense and Google advertising systems can use cookies, local storage, IP address, browser/device metadata, ad interaction data, and related identifiers. Personalised ads are controlled by consent and privacy choices where required.
Google Privacy & Messaging or certified CMP
When production ads are configured for consent-required regions, the app is designed to load ads only when the required production publisher ID, ads-enabled flag, consent-required setting, and CMP-enabled setting are present. A policy owner should verify the active CMP and vendor configuration before ad changes go live.
US privacy choices
For locations where targeted advertising can be treated as sale, sharing, or targeted advertising, available privacy-choice controls, browser or platform signals where supported, and contact requests are the relevant opt-out paths.

Advertising data firewall

The advertising data firewall is a product rule and a privacy commitment. Calculator and scenario data stays out of ad targeting, remarketing, lookalike audiences, custom ad segments, and personalised advertising profiles.

  • Do not use calculator inputs, outputs, saved scenarios, scenario notes, debts, income, balances, favourites, calculator usage details, account state, authentication identifiers, or local scenario data for ad targeting.
  • Do not send calculator field names, values, outputs, scenario names, notes, saved-scenario records, account identifiers, or user IDs to analytics or advertising payload helpers.
  • Keep analytics and ad payloads limited to page and navigation metadata needed to operate, measure, fund, and secure the site.

Managing storage and privacy choices

Use the Privacy choices control in the footer to reopen available consent or opt-out controls. You can also manage Google personalised ads, use the Google Analytics opt-out add-on where supported, or clear cookies, local storage, session storage, and cache storage through your browser settings.

What happens when storage is blocked
Blocking optional analytics or advertising storage should not stop calculators from running. Blocking strictly necessary or first-party product storage can break sign-in, saved scenarios, calculator drafts, currency preference, privacy choices, cached pages, and issue-report workflows.
Clearing local product data
Deleting browser storage can remove local-only scenarios, drafts, favourites, usage history, currency preference, service worker caches, and sign-in state on that device. Account-linked data may also require sign-out, in-product deletion, or a deletion request.
Consent changes
If available privacy choices do not reopen, check browser popup/content blocking, third-party storage restrictions, or contact Calcs.finance so the issue can be reviewed. Browser settings and platform controls can also affect what consent or ad-choice tools can do.

How this policy is kept current

This policy is reviewed when the production app changes storage names, consent tooling, analytics providers, advertising providers, authentication flows, service worker caching, saved-scenario behavior, issue-report payloads, or applicable legal requirements. If this page and an in-product consent message differ, the more specific in-product choice shown to you controls that consent interaction.

Educational estimate boundary

This Cookie Policy explains storage and privacy-choice behavior. It does not change the educational nature of Calcs.finance calculators. Calculator outputs, examples, guides, and formula notes remain estimates and are not financial, tax, legal, lending, investment, pension, insurance, accounting, or regulated advice.