Privacy
Last checked
Last updated
CardFeeCalc (cardfeecalc.com) provides free fee and surcharge calculators. This page describes what the site's code and hosting do with information when you use it.
Calculators on this site
The fee, comparison, surcharge, and marketplace tools run in your browser. Amounts and settings you enter are used locally to show results; this application does not send those inputs to CardFeeCalc servers for calculation or storage.
Some calculators update the page URL with query parameters (for example dollar amounts, channel mix, or custom rates) so you can bookmark or share a link. Those values appear in the address bar and in any referrer or server logs if you load a URL directly; they are not written to CardFeeCalc databases by the calculator code.
The card fee audit also runs entirely in your browser: statement totals and any CSV you import are not uploaded for calculation or storage. If a CSV import fails, the page sends an anonymous report (error type, file size, row and column counts, page, time). No file contents or column names.
The optional “detailed PDF report” on the fee audit generates a printable file in your browser (for example via Save as PDF). Your audit numbers still do not leave the device. If you submit that optional step, we store only these four fields in our hosting key-value storage (cfc-waitlist binding) under a separate key from other email sign-ups (cfc:fee_audit_pdf:<email>, not cfc:<email>): your email address (email), a consent flag (consent, always true when saved), the consent timestamp (consent_at, ISO UTC), and a purpose note (note) matching the checkbox text (storage and contact about the detailed report and occasional fee-change updates). We do not store your audit inputs, page URL, browser description, or IP address in that record, and we do not email the PDF from our servers. To delete this data, email [email protected].
Site search
The search box on the home page and in the navigation loads a list of calculator and guide pages that is built when the site is published. Matching runs in your browser; your full search text is not sent to our servers for ordinary results.
When a search returns no close matches (or only weak ones), the site may send a normalized copy of the query to our servers: lowercased, trimmed, capped at about 80 characters, with email and phone-like strings removed and digits-only queries dropped. We store an anonymous count per normalized query. We do not store your IP address or a user id in that storage, and this logging does not use cookies. To limit abuse, we keep a short-lived counter keyed by a hashed value derived from your connection (not your full IP address).
If you use “Tell us what you were looking for” or the optional feedback forms on calculator pages, that text is stored for review (accuracy reports are flagged for the site operator). An optional email for a reply is stored only with your message. The same short-lived hashed rate limit applies; we do not store your IP address in that feedback storage.
Analytics and advertising
Our hosting provider adds a small script to every page that sends anonymous, cookieless page-view and basic performance measurements (such as load time). It does not set cookies, does not use advertising identifiers, and does not receive anything you type into the calculators. We do not show advertising and do not use tracking pixels.
Typography uses the Inter font via Next.js next/font, which serves font files from this site.
Cookies
CardFeeCalc does not use tracking cookies, advertising cookies, or cookies for paid links. The only cookie this site sets is a sign-in session cookie for people with an API account after email verification (cfc_account_session, HttpOnly, SameSite=Lax, up to 30 days). Calculator pages still do not use localStorage, sessionStorage, or cookies to save calculator state.
Free embed widgets
If a third-party site loads our embed script from cardfeecalc.com/embed.js, the script may send one lightweight request when the widget loads (using navigator.sendBeacon when available). The JSON body includes the widget type (calc, such as fees, compare, or surcharge) and the embedding page's hostname (host). The handler increments a daily count in our hosting storage (keys like daily:YYYY-MM-DD:calc:hostname). The embed-hit code does not store IP addresses or free-form page content there.
Site operators can view aggregated embed counts through a private, authenticated tool.
Email sign-ups
If you submit an optional email form on the embed calculators page (to hear about a future paid API), on the fee changes log, on the card fee audit page (rate alerts), or on related calculator pages (rate alerts), we save your email address and any optional note (see the fee audit section above for the separate optional PDF step, which stores only email, consent, consent_at, and note under cfc:fee_audit_pdf:<email>). On the card statement check waitlist, business country and monthly card volume are required fields (stored with your email, not as an optional free-text note). One record per address notes whether you asked about API news, fee-rate alerts, or the statement check, which page you used first, and any later pages if you sign up again elsewhere. We also save when you signed up and a short browser description (up to 200 characters). We do not save your IP address in that sign-up record. We contact API waitlist sign-ups only about a possible paid JSON API and interest in the product. Statement-check sign-ups are used only to contact you about the card statement check. Rate-alert sign-ups will receive email when tracked rates change once that service is live; until then, use the fee changes log. Reply to any alert or email [email protected] to unsubscribe. We do not sell or share sign-up data with third parties for their marketing.
JSON API
If you create an API key on the API page, we store your email address, a public key id, and a one-way hash of your secret key in our hosting storage (prefixes like apikey:, apikeyid:, and apiemail:). We never store the full secret after the initial response. We use your email only to identify your key and to contact you about the API (for example, changes or limit issues). We do not use it for marketing or share it. Monthly usage counters and signup rate limits are stored separately from key records. To limit abuse, we store a counter keyed by your IP address (IPv6 shortened to its /64 network) when you create a key. Counters older than the previous UTC day are deleted automatically the next time anyone creates a key. Paid upgrades are processed by a third-party merchant of record when paid plans are enabled; we store subscription ids on your key record when payment notifications arrive. Contact [email protected] for API data requests.
Hosting and security logs
The site is served from static hosting with small server handlers for forms, widgets, and the JSON API. Like most web hosts, the provider may process standard request metadata (such as IP address, URL, User-Agent, and timestamps) when delivering pages and running those handlers. This application code does not add separate server-side access logging beyond the application data described above.
Your choices and contact
To ask what we have about you, request deletion of waitlist or fee-audit PDF sign-up data, or unsubscribe from waitlist emails, contact us at [email protected].