Analytics Notice
How visits and active time are measured
MockMindset uses first-party analytics and Google Analytics for logged-out visitors and signed-in learners. The sections below distinguish the two systems.
Last updated: 14 September 2026
At a glance
- Google Analytics measures site use alongside our first-party analytics; Google advertising personalization is disabled in our tag.
- Full IP addresses are not stored in analytics tables.
- Country, region and city are approximate and depend on trusted hosting/CDN headers.
- Active time counts visible, focused use rather than simply the time between opening and closing a tab.
- Do Not Track and the browser control below stop collection.
Google Analytics
We use Google Analytics 4 to understand page visits and use of the website. Google may receive browser and device information, page information and network information, and may use analytics cookies. Google Analytics retention is controlled separately in our Google Analytics account.
Our Google tag removes query strings and fragments from its configured page and referrer URLs. We do not configure it to send account names, email addresses, OTPs or support messages. Google signals and advertising personalization are disabled in the tag configuration.
The browser analytics opt-out and Do Not Track also disable Google Analytics measurement. The signed-in “Help improve MockMindset” setting controls our first-party analytics; use the browser control on this page to disable Google Analytics too. Enabling analytics takes full effect on the next page load.
See how Google uses information from sites that use its services.
First-party analytics fields
| Field | Purpose | Privacy treatment |
|---|---|---|
| Visitor identifier | Estimate unique visitors across sessions | Random browser UUID is stored as a one-way HMAC hash |
| Session and page-view IDs | Group activity and avoid duplicate page views | Random UUIDs |
| Path, title and referrer host | Understand content use and navigation | Referrer is reduced to hostname; path is length-limited |
| Country, region and city | Country-wise visitor reporting | Approximate deployment-network values; may be unavailable or inaccurate |
| IP-derived information | Security and approximate unique-network reporting | One-way HMAC hash and IPv4 /24 or IPv6 /64 network prefix; full IP not stored |
| User agent | Basic browser/device troubleshooting | Length-limited text |
| Active seconds | Estimate engaged time | Sent in increments capped at 60 seconds per event |
How active time works
A page-view event starts when a page loads. While the page is visible and the browser is focused, the page sends a heartbeat approximately every 15 seconds. Hidden or unfocused time is not intentionally counted. Each event adds no more than 60 seconds, which limits inflated totals after a suspended tab.
This produces an estimate, not an exact record of attention. Reading without browser focus, connectivity failures and browser restrictions can affect the result.
Logged-out and signed-in visits
Logged-out visits use random browser/session identifiers and are not dependent on registration. If a visitor is signed in, the analytics session may also be associated with that account so aggregate product usage can be understood. Analytics is not used to alter question scoring.
Retention
The configured default is 395 days. The server removes analytics sessions older than the configured retention period when it starts and deletes visitor records with no remaining session. The production configuration can use a period from 30 to 1,095 days; this notice must be updated if the production setting differs.
Your control
The browser choice affects future page loads. Signed-in learners can also save “Help improve MockMindset” under Settings; the backend rejects analytics events when that saved preference is off. Do Not Track is respected automatically.