What each log records, item by item

Scoring happens in your browser: the page's own script marks each answer. Nothing about your picks, the explanations you open or your running score is transmitted, and it is lost once the tab is closed. Navigation inside the site is not noted either. There is no analytics script, advertising tag or social media widget on any page, and the site sets no cookies.

The server writes a note when a page on oncology-nursing-exam.com is reached in one of three ways: by following a link from some other website or a results page; through an address that carries a utm_source tag; or because an AI search service retrieved the page on behalf of a person asking it something (for instance Perplexity, ChatGPT, DuckDuckGo's assistant, Claude or Mistral). The note contains:

• the path of the page that was opened;
• any utm tags in the address (source, medium, campaign), and the referring address if your browser sent one;
• your IP address, with the operator of its network (AS number and name), and the place it maps to (country, region, city);
• the user-agent header your browser sent, and the name of the AI tool where there was one.

These produce no note at all: an address typed in or opened from a bookmark, a link followed within the site, requests for images, fonts or stylesheets, prefetching, and crawlers that collect training data for AI models. The note is sent on once the page has already been delivered; the page you get is identical with or without it. Its use: learning which referrers (search engines, AI services, other sites) bring readers, and to which pages.

An app button does not point at a store directly. It goes through go.oncology-nursing-exam.com, which forwards the App Store button to Apple and the Google Play button to Google; if the exam has no app in that store, the button leads to this site's own pages instead. Before forwarding, that service notes:

• the exam, the kind of button, and the page the tap started from;
• the operating system, guessed from the user-agent, and the destination the button had;
• the IP address with its operator (AS number, name), an approximate place and that place's time zone;
• which Cloudflare data center handled the request;
• the user-agent header, the referrer, and any leftover parameters of the link.

The store address it opens carries this domain as a label (a campaign token for Apple, a referrer value for Google Play), so an install can be credited to this domain in the store's reports; taps that arrived via an AI assistant get a label saying so. From then on, the store's privacy policy, Apple's or Google's, is the one that applies.

HTML pages carry a Referrer-Policy header of no-referrer-when-downgrade, identical for all visitors. So when you tap a button, the go. service learns which page held the button; that is how note two records where the tap started. The go. service forwards with strict-origin-when-cross-origin, so Apple and Google are told the go. host name only. No address is handed from these HTTPS pages to a plain HTTP one.

Cloudflare hosts both the site and the go. service; serving a page means Cloudflare's servers process your request. Records of your certification are kept by ONCC, not here; Contact explains where to ask about them.