Skip to the main text
Fire & EMSCertification Exam
Menu

Privacy

Privacy: what a visit here leaves behind

No account, cookie or form stands between you and any page or practice question. Two kinds of visit do produce a record on the server; each is described below, field by field.

Quiz answers are scored on the page

A script in the page marks your answers. Your choices, the reasons you expand and the running tally are never transmitted, and they disappear when the tab closes. Browsing inside the site leaves no record either.

Record 1: arrivals from outside the site

A record is created when a page on fire-ems-certification-exam.com is opened from outside the site, in one of three ways: you came through a link on another website or a results page, the address included a utm_source tag, or an AI-powered search tool or assistant fetched the page on someone's behalf (ChatGPT, Perplexity, Claude and Mistral are examples). The record holds:

  1. the page's address on this site;
  2. the referring address and any utm tags;
  3. your IP address, the network operator it is registered to (by AS number), and a country, region and city estimate based on it;
  4. the browser's user-agent header.

Nothing is logged for a typed address or a bookmark, for clicks inside the site, for files such as images and stylesheets, for link prefetching, or for crawlers that collect AI training data. The record leaves the hosting server for our reporting system only after the response has gone out, and it changes nothing in what you receive. Its purpose is to tell which search engines, assistants and websites send readers, and to which pages.

Record 2: what an app-button tap logs

App buttons do not link straight to a store. Each one passes through go.fire-ems-certification-exam.com, which forwards an App Store button to Apple's store and a Google Play button to Google's; the button you tap decides the store. Before forwarding, it stores:

  • the exam and the button tapped, and the page it sat on;
  • the device's operating system, as read from the browser, and the store the button pointed to;
  • your IP address and its autonomous system number;
  • the city, region and country that address maps to, with its time zone;
  • the Cloudflare data center that served the tap;
  • the user-agent string, the referring address and any extra parameters in the link.

The outgoing store link is tagged with this domain (a campaign token for the App Store, a referrer tag for Google Play), which lets each store credit an install to this domain; a tap that came through an AI assistant is tagged as such. Inside the store, the privacy terms of Apple or Google take over.

The page address your browser passes on

Pages here go out with no-referrer-when-downgrade as their referrer policy, for every visitor alike. That setting lets your browser hand the full page address to the app-button service, which is how the second record knows where a tap began. The hop from that service to the store uses a tighter policy, so Apple and Google learn only the go. host, not the page. Nothing is passed from this encrypted site to an unencrypted one.

Who runs the servers

The pages and the app-button service run on Cloudflare, which handles every request in order to deliver it. There are no advertising networks, analytics scripts or social media widgets on the pages. Questions about your own certification record belong with the agency that holds it; see Contact.