Skip to content
calculateeveryday

Privacy Policy

Last updated: 17 October 2026

CWK Solution (Suman Kumar) operates calculateeveryday.com and is the data controller (a "Data Fiduciary" under India's DPDP Act 2023) for the data described below.

What we collect

  • Site analytics. We use two, and neither sets a cookie. Cloudflare Web Analytics stores nothing on your device and cannot recognise you on a later visit. DataFast runs in its cookieless mode, loaded from our own subdomain (e.calculateeveryday.com): it tells visits apart on its side with a hash of your network address and browser that changes every day, so it cannot follow you from one day to the next, and its only browser storage is three short entries that are deleted when you close the tab (see below). It records which pages are visited, where the visit came from, and actions on the site: using a calculator, sharing or downloading a result, opening the embed panel or the watermark offer, copying embed code, reaching the explanation or the FAQ, scrolling to parts of the home, sponsor and embed-plan pages, picking a search result, voting on "Was this helpful?", opening the sponsor form, clicking a sponsor or one of our own house ads, starting a checkout or a checkout failing to start (with its error code), asking for an embed-plan sign-in link, and sending a message from the contact page (its topic and, when one is attached, which calculator — never what you wrote). With most of them it records which calculator, never the numbers you type or anything you write. Neither follows you to other sites. We deliberately don't run Google Analytics or any ad-network script.
  • Aggregate visit counts. Our own "total visits" and "visitors online" counters, and the view count on the sponsor page, count one visit per visitor per day without a cookie: our server computes a one-way hash of your network address, browser and the date, mixed with a secret, keeps that hash for at most two days to avoid counting you twice, and never stores the address itself. A new day gives a new hash, so the counters cannot link your visits together. Counters only — no profile and nothing used for ads. Until 14 October 2026 these counters set cookies and ran only if you agreed; a browser still holding one of those cookies is told to delete it.
  • Country for currency display. When you load a calculator, our edge detects your country (via Cloudflare, from your network location) to suggest a display currency. It is cached in your browser and you can override it any time with the currency switcher.
  • Shared result links. If you press "Share", we send the calculator slug, the values you entered, and the headline result to our server, store them under a random short ID, and return a link. See Shared result links below — this is the one case where numbers you typed leave your browser, and it only happens when you choose it.
  • Sponsor checkout. If you book a sponsor slot, we collect your email, the number of days and amount paid, display name, pitch, destination link, and the cover image link if you add one, and we email you a confirmation. Card and billing data is handled entirely by Dodo Payments as Merchant of Record — we never see or store card numbers. If DataFast is running in your tab, the checkout also passes DataFast's id for that day's visit to Dodo (see DataFast under Third parties).
  • Embed plan. If you buy the $5/month embed plan, we keep in our database the email and name you give at checkout, the calculator and the site you name, the plan's status and next billing date, and Dodo's references for the subscription and for you as its customer. We use them to take the watermark off on that site, to show the plan — and the sites its embed has been seen on — in your dashboard, and to email you a welcome message and any sign-in link you ask for. A sign-in link works once and lapses after 30 minutes, or 7 days for the one in the welcome email. The sign-in page says whether an address has a plan, so anyone who types your address there can learn that it does. Card details stay with Dodo Payments, and the checkout carries the DataFast visit id just as a sponsor checkout does.
  • Sponsor click counts. Clicks on a sponsor listing are counted in aggregate per booking so its owner can see volume. Sponsor listings never appear inside embedded calculators. We do not log the individual visitor behind a click.
  • Calculator page views. Each calculator page increments an aggregate view counter in our edge database (at most once per browser tab session per calculator). We use this only to rank the "Popular" list on the homepage — no profile, no cross-site tracking.
  • Embedded calculators. When a calculator is embedded on another website, the embed reports that website's hostname to us once per visitor session — never the page address, and nothing about the visitor. We keep a count per site so a paid watermark-removal plan applies to the site it was bought for, and so we can see where calculators are used.
  • Homepage activity strip. When you open a calculator, we may record the calculator's name, your country (from Cloudflare, not your IP address), and the time — never the numbers you type or the result. We keep only the 20 most recent opens, each replaced as newer ones arrive, and the homepage shows the newest as "Someone used X from Y" only while it is under 15 minutes old. Health calculators are never added to this list.
  • Calculator-open notifications. The same open also sends one short message to a private Telegram chat that only we read: the calculator's name, the city and country Cloudflare places your network in, and your device and browser type (for example "Android · Chrome") — never your IP address, the numbers you type, or the result. At most 20 a day; after that they stop until midnight India time. Opens by recognised crawlers are not sent. Unlike the homepage list, these include health calculators.
  • "Was this helpful?" votes. A single up/down vote per calculator per browser, counted anonymously. DataFast also records the vote and which calculator it was for, as one of the actions above. It is never shown as a star rating.
  • Email to us. Mail to hello@calculateeveryday.com is received by Cloudflare Email Routing and forwarded to our Gmail inbox. We use what you send only to answer you and to act on what you report.
  • Contact form. If you write to us from the contact page, we receive your email address, the topic and your message, and your name and the calculator it is about if you add them. Our server passes them straight to Resend, which emails them to hello@calculateeveryday.com with your address as the reply-to, so our answer goes to you. We don't save them in our database: they reach us only as an email. Like most of our API, the form is rate-limited by network address. So that one connection can't use up the form for everyone, our server also counts how many messages each network sends in a day, against a one-way hash of its address mixed with a secret and the date, kept for at most two days. A one-line notice that a message arrived, with its topic only — never your name, email address or message — goes to our Telegram chat.
  • Sponsor waitlist. Only while sponsor checkout is switched off, the sponsor form becomes a waitlist instead: we keep the name, email, link, pitch and number of days you enter for 90 days, and email them to ourselves.
  • Abuse limits. Most of our API limits how many requests each network address can make in a minute, using Cloudflare's rate limiting. The address is used for that count only; we never store it. Two limits keep a one-way hash of it, mixed with a secret, instead: the contact form's daily count (above, kept at most two days), and failed sign-ins to our admin panel (kept 15 minutes).
  • Pre-launch notify-me list. If you enter your email on the launch countdown screen, we store it in our edge database so we can tell you when CalculateEveryday — and future CodeWithKolin projects — launch. This is opt-in and used only for that purpose.

A shared link is public to anyone who has the ID and is used to render a preview card when the link is pasted into a chat app or social network. Shared records expire automatically 12 months after creation.

Do not share results that contain data you consider sensitive — your actual salary, loan balance, or health measurements. If you want a link removed before it expires, email hello@calculateeveryday.com with the link and we will delete it.

If you do not press Share, the numbers you type stay in your browser. Calculator inputs are kept in the URL fragment (the part after #), which browsers never transmit to a server and which does not appear in server logs or the Referer header.

Download PNG is not Share — the image is drawn on your device and saved directly to your device; your numbers are never sent to our server, even for health or tax calculators.

What we store in your browser

We set no analytics or tracking cookies. The only cookie is for embed-plan customers who sign in; everything else below is browser storage that never leaves your device and that we never read from the server:

  • datafast_visitor_id, datafast_session_id, datafast_pageview_state — DataFast's id for today's visit, a random id for this tab, and the page you are on (so a reload isn't counted twice). Session storage, not cookies: deleted when you close the tab.
  • ce_embed_session — set only when an embed-plan customer signs in from /embed-plan/sign-in. HttpOnly, 30 days, holds the signed-in email address so the dashboard can show that customer's plans. Signing out removes it.
  • ce_embed_email — the email you last used for the embed plan, so the sign-in form can prefill it. Browser storage, not a cookie.
  • ce_currency_override, ce_unit_override, ce_geo_cache — your chosen display currency and units, and the detected currency. Browser storage, not a cookie.
  • ce_recent_calcs — the last few calculators you opened, shown on the home page. This list never leaves your device.
  • ce_helpful_<slug> — records that you already voted, so we don't ask twice. Browser storage, not a cookie.
  • ce_calc_open:…, ce_embed_seen:…, ce_helpful_dismissed — markers that stop a calculator view or an embed sighting being counted twice, or the "Was this helpful?" prompt coming back, in the same tab. Session storage: deleted when you close the tab.
  • ce_launch_gate_cache — whether the pre-launch screen is switched on, so pages don't flash it. Browser storage, not a cookie.

Clearing your browser storage removes all of these and breaks nothing. Before 14 October 2026 the site asked before setting analytics cookies (ce_vid, ce_sid and four from DataFast) and kept your answer in ce_consent. None of those is set any more, so there is nothing left to ask about, and the site deletes any of those old cookies it finds in your browser.

What we don't do

  • No Google AdSense or third-party ad network scripts, and no cross-site ad tracking.
  • No selling, renting, or sharing of your data with data brokers.
  • No profiling, no automated decision-making, and no marketing email you did not ask for.
  • We do not knowingly collect data from anyone under 18.

Third parties we use

  • Cloudflare — hosting, edge functions, our databases, key-value storage and live counters, per-address rate limits, cookieless analytics, and Email Routing, which receives mail sent to hello@calculateeveryday.com and forwards it to our Gmail inbox.
  • Google — our email inbox (Gmail), where mail to hello@calculateeveryday.com arrives.
  • Dodo Payments — Merchant of Record for sponsor checkout and the embed plan. It takes your card and billing details on its own checkout page and handles them under its own privacy policy, and it runs the billing portal where embed-plan customers update or cancel a plan. From us it receives the email and name you entered, what you are buying, a reference that lets us match its payment confirmation to your booking or plan, and the DataFast visit id described below.
  • DataFast — analytics. Three separate things: the cookieless browser script described above; server-side bot tracking, which does not involve you at all; and payments. The bot tracking reports only requests from recognised AI and search crawlers (GPTBot, ClaudeBot, Googlebot and similar), and what it sends is the page they asked for and that crawler's own user agent and server address. Requests from real browsers are identified as such and never reported. For payments: when a live payment to us succeeds (never a test one), our server sends DataFast the amount and currency, Dodo's references for the payment and for you as its customer, whether it renews an embed plan, and the time — plus, if DataFast was running in the tab where you started the checkout, that day's visit id, so the payment can be credited to the visit. A refund is reported against the payment it undoes. DataFast never gets your email address, name or card details from us, and keeps what it receives under its own privacy policy.
  • Resend — sends our email: sponsor confirmations, embed-plan welcome and sign-in emails, contact-form messages, and notifications to our own inbox. Resend keeps a log of what it sends under its own policy.
  • Telegram — private notifications to us: the calculator-open messages described above; the topic of each contact-form message; a message when a sponsor books (the public display name, days and amount) or when an embed plan starts (the calculator and the site named for it) or ends; if a payment can't be matched to a booking or plan, Dodo's reference for that payment or subscription (no name or email address); and error alerts that name the part of our API that failed but carry no request contents, email address or name.

Our infrastructure runs on globally distributed edge locations, so data may be processed outside your country. A sponsor card shows an image from the sponsor's own website or, if that fails to load, the site's icon from Google's favicon service, so your browser fetches it from there, as it would any image. Clicking a sponsor listing takes you to a third-party site governed by its own policy.

How long we keep things

  • Shared result links — 12 months, then automatic deletion.
  • Sponsor waitlist entries — 90 days, then automatic deletion.
  • Pre-launch notify-me emails — kept until you ask us to remove you (no automatic expiry); email hello@calculateeveryday.com to be removed.
  • Sponsor bookings — kept as part of the public sponsor history indefinitely once made, plus transaction records we are required to retain for tax and accounting purposes.
  • Embed plans — kept while the plan runs and after it ends, so you can still sign in and see it, until you ask us to delete it. Nothing deletes an ended plan automatically.
  • The record a checkout creates before payment — 30 days, whether or not you pay. Sign-in links — until used, or 30 minutes (7 days for the welcome email's). If an email we send you fails, the address and the error — 7 days, so we can see what went wrong.
  • Email to us — in our inbox until we delete it; ask and we will delete yours.
  • Telegram notifications — in our chat until we delete them.
  • Calculator opens for the homepage strip — the latest 20 only.
  • Aggregate counters, including per-site embed counts — indefinitely, because they contain no personal data.

Your rights

Subject to local law, you may request access to, correction of, or deletion of your personal data, withdraw consent, or object to processing. Under the DPDP Act 2023 you may also nominate another person to exercise these rights. Email hello@calculateeveryday.com or use the contact form, and we will respond within 30 days.

Grievance Officer

Suman Kumar · CWK Solution
India
hello@calculateeveryday.com

Complaints are acknowledged within 24 hours and resolved within 15 days, as required by India's IT Rules 2021. Full contact details are on our Contact page.