Privacy

The short version: your files never leave your browser, and there are no accounts, no profiles and no uploads. The one thing that will change is advertising: Google AdSense is planned for some pages, and the rules for it are set out below.

What happens to your files

Every tool on this site reads your file with the browser’s File API and processes it with JavaScript that is served from this domain. There is no upload step, no API call and no server-side processing. When you close the tab, the file is gone from memory.

What this site does not do

  • No file, key, password or certificate is transmitted anywhere.
  • No first-party cookies, no localStorage, no fingerprinting, no session recording.
  • No ad code today and no tracking pixels, no social embeds. Visit counts are anonymous and cookie-less. Read the Visit counts and Advertising sections below.
  • No accounts, no email collection, no newsletter.

Hosting

The site is static and hosted on Cloudflare Pages. Like virtually every web host, Cloudflare receives standard request metadata (IP address, user agent, requested URL) when your browser loads a page. That is how the HTML reaches you. No request that runs a tool carries your data, so that metadata never includes a file, key or password. See Cloudflare’s privacy policyfor how they handle request logs.

Visit counts

The site loads one small third-party script: Cloudflare Web Analytics (static.cloudflareinsights.com). Until ads are approved, it is the only request the page makes to a host other than this one, and it does one thing: records that a page was opened. It sets no cookies, stores nothing on your device, does not fingerprint you and does not follow you across other sites. The aggregate report shows which page was viewed, the referring site, the country and the browser family; never an individual visitor, and never anything about the files you open in a tool.

This is a visit counter, not surveillance. Cloudflare processes these aggregate counts under its own privacy policy (linked above). The tools themselves still make no network calls at all.

Advertising (AdSense)

No ads appear on CertKit today. We are applying to show Google AdSense ads on some pages. They will only appear after Google approves the site, and only with consent where required. Ad scripts can set cookies after consent; the tools themselves still run locally and never upload your files.

  • After approval only. No AdSense script is loaded until Google approves the site. There is no ad slot, no placeholder and no hidden ad code on any page right now.
  • Consent first where required. In regions that require it, ad and consent scripts load only after you agree. The tools do not depend on ad scripts, so blocking or declining ads does not disable them.
  • Cookies and third-party data. After consent, Google and its partners may set cookies or read device identifiers to serve and measure ads. That can include approximate location and ad-interaction data. It is Google’s processing, not ours, and it never touches the files you open in a tool. See Google’s advertising policiesand Google’s privacy policy.
  • The tools stay local. Ads sit beside the tools. Certificate, key, CSR and password contents never go to Google or anyone else: processing still happens in your browser tab.
  • Opting out. You can limit ad personalisation at Google Ad Settings or with your browser’s tracking controls. Blocking ads does not break any tool.

If the application is rejected, or this changes, this section will be updated before anything ships.

Verifying the claims

Open DevTools → Network, clear the log, then run any tool: you will see no request appear while your file is processed. The one exception is the “Load sample” button, which fetches that test file from this site (again, nothing of yours is involved). The only third-party entry today is the analytics beacon loaded with the page; once AdSense is approved and consented to, Google’s ad script will appear there too. Disconnect your network after a page loads and the tools keep working. That is the strongest possible proof that processing is local.

Contact

Questions about the privacy model? Write to contact@wheelchairrampcalculator.com or see the contact page. The parsing library, tests and site source are public at github.com/pantha704/certkit-mini-saas, open an issue if anything looks wrong.

Last updated: 20 October 2026.