What the pages themselves do
Each page is a prebuilt HTML file served as it is. Fonts, scripts and images load from this domain only, and no outside script, tag or pixel runs on any page.
The practice board and the timed sprint keep your picks, the clock and the score in the open tab. They write nothing to your device and send no answers anywhere; reload the page and the board starts clean. The only extra request a board makes is for the rest of its cards, from this site’s own /assets/ folder.
Like any web host, the network that delivers these pages receives your IP address and browser details in order to answer each request, and handles them under its own terms. On top of that the site keeps the two server-side logs described below, and nothing else.
The app redirect and its click log
Every Get the app button on this site points to go.capm-certification-101.com/app, with the page path and the button’s position (top, menu, hero, rail, band or the 404 page) in the link. On an iPhone or iPad the redirect sends you to the app’s App Store listing. Android phones have no app to install, so they go to this site’s free CAPM® practice test instead.
A computer sees a short page first, with the App Store badge, a link to that practice test and a QR code. The page sets no cookies, and a press of its badge or link is logged the same way. The QR code holds one fixed address, go.capm-certification-101.com/app?src=qr, the same for every visitor, with no page path and nothing about you in it. It is drawn into the page, so showing it requests nothing from anyone else. Scanning it opens the redirect on your phone, and that request is logged as a press with the source marked as the QR code. The code is hidden on narrow screens.
After the redirect has answered, its server sends one log line to the publisher’s own database, server to server. Your browser is not involved in that step: nothing is stored on your device, no script runs, and no identifier is carried from one press to the next. Pages on this site let your browser pass their full address to the redirect as the referring page; the App Store receives no more than a host name. Each log line carries the date and time of the press and whether it was a press of an app button or of a badge or link on the computer page; the other fields are listed in the table.
| Field | What is recorded |
|---|---|
| Page | the path of the page the button was on, how that path was found, and which button (top, menu, hero, rail, band, 404) or the QR code |
| Device | the operating system family, read from the user-agent string |
| Destination | App Store, this site’s practice page, or the short page for computers |
| AI assistant | which assistant the press came from, when the App Store link carried the AI label; otherwise empty |
| Network | IP address, the network operator (ASN and its name), and the country, region, city, time zone and delivery data center that follow from it |
| Browser | the user-agent string and the referring page |
| Other link labels | anything else in the link’s query string, such as a utm label |
The label on the App Store link
- Campaign token (ct)
- Set to this site’s domain, so the publisher’s App Store reports can count downloads that began on a link from this site. When the press comes from an AI assistant, the token ends in -ai, so those downloads are counted separately.
- Provider token (pt)
- Identifies the account that publishes the app, which Apple needs to attribute the campaign token to the right publisher.
- How an AI assistant is recognized
- The redirect looks only at the request in front of it: the referring page, or a utm_source label on the link or on the page you came from. It recognizes ChatGPT, Perplexity, Gemini, Copilot and Claude, and the log line records which one. A press with no such sign gets the ordinary token.
The visit log
Each page on this site is answered by a small server script before it reaches you. After the page has gone out, that script may send one log line to the publisher’s database, server to server, the same way the redirect does. It adds no cookie, no script and no pixel, and the page you receive is the same whether a line is written or not.
A line is written in only two cases:
- you opened a page on this site from somewhere else: the request names a referring page on another site, or the link carries a
utm_sourcelabel; - an AI assistant or AI search service fetched the page, known by its user-agent name: ChatGPT-User, OAI-SearchBot, Perplexity-User, PerplexityBot, Claude-User, Claude-SearchBot, MistralAI-User or DuckAssistBot.
Nothing is written for a move from one page of this site to another, for a direct visit with no referring page and no label, or for a redirect, a prefetch, a 404 page, or a font, script or image. Crawlers that collect text to train AI models are not logged either.
| Field | What is recorded |
|---|---|
| Time | the date and time of the page view |
| Type | a visit, or an AI fetch with the name of the fetcher |
| Page | the path of the page; the rest of the address is not kept, apart from the labels in the next row |
| Source | the referring page, and the utm_source, utm_medium and utm_campaign labels if the link carries them |
| Network | IP address, the network operator (ASN and its name), and the country, region and city that follow from it |
| Browser | the user-agent string |
What the logs are for, and what is never collected
The click log shows which pages and which buttons send readers to the app. The visit log shows where readers arrive from, such as a search engine, an AI assistant or another site. The publisher’s server sorts each visit by source and marks each line as likely a person or an automated client. Lines are mostly read as counts per page, per button and per source; single lines are opened to diagnose faults and to filter bots. A line holds no name, email address, account or device identifier. Lines of the same site are compared by IP address in three ways: to count each address once a day, to check that a press on the computer page followed a press of an app button, and, together with the browser string, to estimate where a reader came from when the press is on a different page from the one they arrived on. These are estimates. No fixed deletion date has been set for either log; both stay with the publisher, are not sold and are not shared with advertisers.
The site never collects:
- anything stored on your device: cookies, local storage entries or identifiers;
- analytics scripts, heatmaps, session recordings or advertising pixels;
- your picks, scores or timings on the practice board and the sprint;
- an email address, a name or a sign-up of any kind.
Once you install the app, it is covered by its own privacy policy, linked from its App Store listing. About Swimlane Prep says who publishes the site, and the contact page covers where questions go.
This page last changed on November 4, 2026, when the visit log, the QR code and the AI label were added.