Skip past the menu
Maternal Newborn Nurse Certificationindependent exam reference

Privacy · compared with the site's code, November 2026

Privacy, followed step by step

Nothing here needs a login, a form or a cookie. Two events leave a trace on the server: landing here from somewhere else, and tapping through to an app store. To make that concrete, the steps below follow a nurse who finds the site during a night shift, noting at each step what, if anything, gets stored.

One night-shift visit, step by step

  1. A search result leads to a topic page

    Because this visit started outside the site, a short entry is filed on the server. It lists the path opened, the referring URL the browser supplied (with utm tags, if the link had any), the IP address together with the operator that runs its network and a city-level guess at location, and the user-agent text the browser sends. Had a chatbot such as ChatGPT loaded the page while answering a person, the entry would name the bot. The entry is filed after delivery finishes, which keeps the page's speed and content independent of it.

  2. Three more pages, then a break

    Moving on through internal links adds nothing. Nor does returning days later from a saved link or by typing the domain, or the background loading of images, fonts, stylesheets and prefetches. Bots that scrape text to train AI are left out entirely.

  3. Ten practice questions

    Marking happens in the tab itself, done by the page's script. The letters chosen, the notes opened and the score never leave that tab and are lost when it closes.

  4. A tap on the Google Play button

    This tap passes through go.certified-maternal-newborn-nurse.com, which writes a single row and then hands off to Google Play. Stored: the exam and the store; the path of the button's page; the referrer and any further query parameters; IP address and network operator; an approximate place and its time zone; which of Cloudflare's locations took the tap; and the user-agent text the browser sends. The page path travels in the button's own link, as a pg parameter; the browser's referrer header carries it as well, since pages here use the no-referrer-when-downgrade policy.

  5. Google Play opens

    The link arrives carrying this domain as a tag in Play's referrer parameter (Apple's equivalent is a campaign token), so installs that began here show up in the store's own figures; visits that started in an AI chat get an extra marker. The hop's response tells the browser to pass on the origin alone (the strict-origin-when-cross-origin rule), and the store never learns which page it was. Google's or Apple's terms take over from there.

Why keep even that much

The rows answer one practical question: which channels (search, AI chat, links from other sites) send readers, to which page first, and how many then go on to look at the app. A landing and a later tap may be joined to make that count. No row contains names, email addresses or logins, because nothing like that is ever requested, and the rows are not for sale.

What the site never runs

  • No cookies at all.
  • Third-party code of any sort: no analytics, no ads, no share buttons.
  • Sign-ups: there is nothing to join, whether an account, a form, a comment thread or a newsletter.
  • No record of quiz activity.

The host, and the files this site never sees

The site's pages sit as fixed files on Cloudflare Pages, and the go. address is a small Cloudflare Worker script, so Cloudflare carries all traffic to and from the site. The paperwork of the exam itself, from the application and the PSI booking to the score report and the maintenance file, lives with NCC and PSI and never reaches this site; the contact page explains who holds what.