Skip to content

Privacy Policy

How Calculatopia keeps financial entries in your browser and handles limited visitor analytics, hosting requests, preferences, and voluntary messages.

Last updated:

Financial values entered into Calculatopia's public calculators stay in your browser. We do not send those values to our analytics service, put them in page URLs, or store them in a user account. Loading the website still involves network requests, and the limited analytics and hosting processing described below are separate from your financial inputs.

This policy covers the Calculatopia website and its public calculators. The tools do not require public registration, connect to a bank, accept payments, or collect payment-card details.

Site operator and privacy contact

Site operator
LING QU AI LIMITED

See Contact for guidance on reporting an issue without sending sensitive information.

Calculator inputs, comparisons, and downloads

Amounts, rates, terms, and calculator scenarios are held in browser memory while you use the page. We do not save those financial entries to our servers, analytics records, cookies, or local storage. Reloading or leaving the calculator can clear its state; it is not an account-backed record of your finances.

If you choose “Use this rate in the CD calculator,” your original rate, rate type, and compounding frequency pass once to the CD calculator in the current tab's memory. A pending transfer expires after one minute and is cleared when consumed. Reloading or opening the CD calculator directly does not restore it. The transfer does not put financial values in URLs, telemetry, cookies, or persistent browser storage. You still enter the deposit amount and term; returning to the APY calculator does not restore your previous inputs.

If you export a CSV, the browser creates the file for you to save on your device. Calculatopia does not upload a copy. You control the downloaded file and any sharing, backups, or cloud synchronization performed by your device or other software.

The downloadable net-worth-by-age table contains public SCF group statistics and source metadata, not personal financial inputs. Its export timestamp records when your browser generated the file; it does not change the survey year or dollar basis.

The net worth percentile tool downloads an aggregated public SCF dataset for the selected broad age group, or for all families. That request's URL identifies the selected group and is visible to the hosting service. Your entered net worth is not included in the request. The tool does not request an exact age, and visitor analytics records only whether all-family or age-group mode was used, not the selected age range.

Limited first-party visitor analytics

We use our own analytics endpoint to understand page use and whether people can complete the calculators. The endpoint accepts a strict set of fields, rather than arbitrary form data. Stored visitor events may contain:

  • An approved public page path, without its query string or fragment.
  • An event type, such as a page or tool view, calculation start or completion, validation error, scenario comparison, export, or a methodology or related-tool link click.
  • A supported calculator mode, such as personal/household, nominal/APY, or all-family/age-group, and a coarse validation-error category when relevant.
  • Random event identifiers and a random session identifier used to count and deduplicate activity within a visit.
  • A broad source bucket: direct, internal, Google, Bing, DuckDuckGo, Yahoo, social, or other. The browser reduces a referring URL to this bucket before sending the event.
  • A mobile, tablet, or desktop layout category based on viewport width, and a country code supplied by the host, or an unknown-country code.
  • A test-traffic flag and a server-recorded timestamp, reported in UTC.

The visitor-event table does not store financial values, exact age, the selected age range, IP address, raw user-agent text, a referring page's path, URL query strings, or a user account ID. A completion event describes interaction with a valid calculator state; it does not reveal the result or mean a financial decision was made.

Sessions and storage

The analytics session identifier exists only in the current tab's memory. A reload starts a new session; a new session also starts after 30 minutes without an event. A session count is not a count of unique people. Analytics does not use cookies, local storage, or browser fingerprinting to recognize a returning visitor or connect activity across devices.

Visitor-event records older than 90 days are pruned when new events are ingested. There is no separate scheduled deletion job, so older records may remain until ingestion next runs if the site receives no new events. This retention rule applies to our visitor-event records; it is not a promise about hosting logs or voluntary correspondence.

Browser privacy signals and exclusions

We suppress our visitor analytics when the browser sends supported Do Not Track or Global Privacy Control signals. The endpoint also ignores matching signals and recognized bot or crawler user agents. Authenticated administrative sessions are excluded, and administrative pages are outside the approved public-page list. Bot detection is limited to recognized patterns and does not guarantee that every automated request is identified.

Privacy signals do not prevent the requests needed to load pages, assets, or public survey data. Blocking analytics does not prevent the calculators from working.

Hosting, network requests, and security logs

Cloudflare hosts and delivers the site. It necessarily processes request information such as IP addresses and requested URLs to deliver content and protect the service. Depending on the hosting configuration, request metadata, errors, and security or operational logs may be processed separately from our visitor-event table. The analytics exclusions above do not mean that this network information is absent from hosting systems.

Cloudflare describes its handling of end-user traffic in its Privacy Policy, and its Workers Logs documentation describes request, response, and related log metadata. Those systems have their own configuration and retention rules. We do not claim that the visitor-event retention period governs Cloudflare's separate processing.

Cookies, preferences, and third-party scripts

The public calculators do not require authentication cookies. Restricted administration uses authentication cookies to keep an authorized operator signed in. Theme or language preferences may use browser storage or a preference cookie; these preferences are separate from calculator values and visitor analytics.

The public pages do not mount third-party tracking, advertising, or chat scripts. Links to source websites take you to services with their own privacy practices. We do not send your calculator values with those links.

Information you choose to send

If you contact us, your email address, message, and any attachments are information you voluntarily provide outside the calculator. We use them to investigate and respond to your request and address related site issues. Email providers necessarily handle delivery. Please send examples with invented numbers instead of financial records, credentials, or identity documents.

We do not publish a fixed response time or a fixed retention period for correspondence. Contact us if you want to ask about access, correction, or deletion of information you have sent. The available response depends on the information held and applicable obligations; a browser-memory session may not be identifiable from your name or email address.

Use, disclosure, and your choices

We use the limited information described here to operate the site, diagnose issues, understand aggregate use, protect the service, and respond to messages. We do not sell calculator inputs or visitor-event data, and we do not use them for personalized advertising. Hosting and communication providers process information needed for their services. Information may also need to be disclosed to meet a legal obligation or investigate abuse.

You can use browser privacy signals to suppress our analytics, clear site preference storage, and delete your downloaded files. Avoid including sensitive information in URLs or correspondence. No online service can promise absolute security; the browser-only calculation design reduces the financial information that needs to reach us in the first place.

Changes to this policy

If the site's data handling changes, this page should be updated with an actual revision date and an explanation of material changes. The date above describes this policy's content update, not a guarantee that an external provider's policy has remained unchanged.

For questions or privacy requests, use Contact. For the scope of the service, read the Terms of Service.