Privacy · written from the server code, Nov. 2026
Privacy: what gets written down, and when
The server writes something down in exactly two cases: an arrival from another website, and a badge press for one of the app stores. The table below goes through what readers ordinarily do here and marks which of them write one; no page asks you to sign in, and none sets a cookie.
Everyday actions, and whether a record follows
| What you do | Record? | Kept where |
|---|---|---|
| Arrive on a page from a search result, an AI chat answer or a link on another website | Yes, one arrival record | the site itself |
| Arrive through an address that includes utm_source, even a bookmarked one | Yes, one arrival record | the site itself |
| An AI assistant such as ChatGPT or Perplexity fetches a page while answering someone | Yes, marked with the assistant's name | the site itself |
| Type the address, open a plain bookmark, or follow a link between two pages of this site | No | the page loads with nothing kept |
| Pick answers in a quiz and open the explanations | No | the quiz script holds your picks in the open tab only, so closing it erases them |
| Press a store badge for Apple or Google | Yes, one badge record | go.certification-for-cardiac-nurses.com, the redirect to the store |
| Follow a link out to ANCC, Prometric, a journal or a guideline | Not here | the receiving site sees the page address you left |
| A crawler gathers text to train an AI model | No | not logged; the worker skips training bots by name |
Inside a record
A record names the page involved and any referrer the browser passed along. It also keeps the visit's network details: the IP address, its AS number (the ID of the network it sits on) and that network's operator, the town, region and country Cloudflare attaches, and the User-Agent string.
For an arrival, any utm values in the address are kept as well; for an AI fetch, the assistant's name.
Badge records add which exam and which store the badge was for, other parameters present in the link, the time zone Cloudflare infers, and a code for the Cloudflare facility that served the press. The badge link carries the page it sits on in a pg parameter. A second copy arrives in the referrer header, which these pages permit under no-referrer-when-downgrade.
What the counts are used for
Totals per source (search engines, AI assistants, other websites) and per landing page, plus the share of readers who go on to a store listing: that is the whole use. To compute that share, an arrival may be paired with a badge press that follows it. There is no field anywhere on the site for personal details, so records hold none, and no record is sold or passed to an ad network.
What the stores learn
On the way through, the go. redirect tags the store link with this domain, as Apple's campaign token or as utm_source within Google Play's referrer value. A distinct label is added when the visit started inside an AI chat reply. The store therefore learns which site sent you but not which page, thanks to a strict-origin-when-cross-origin header on that redirect. Whatever Apple or Google record next falls under their policies, not this one.
Where hosting ends and ANCC begins
Pages and the go. redirect both run on Cloudflare, so every request crosses its network; its privacy policy covers what Cloudflare itself logs. Your CV-BC application, eligibility review, appointment, score report and renewal are kept by ANCC and Prometric and never reach this site. The contact page shows who handles what.
The papers behind this page
1 document, listed by tag
- Sprivacy policysource site cloudflare.com