Useful measurement without learner profiling.

First-party aggregate funnel counts

Selected milestones—such as opening a certification, starting or submitting a diagnostic, opening a source, and requesting a release notice—increment an hourly PostgreSQL counter. Each counter contains only an allowlisted event name, certification code, coarse page source, hour, and count.

The counter does not store an IP address, browser identifier, cookie, account ID, email, question response, score, or visited URL. Browser-side event requests explicitly omit credentials.

Server-owned lifecycle measurement

When enabled, our application records a small allowlisted set of completed lifecycle milestones: diagnostic start and completion, Checkout creation, and paid, refunded, or disputed order status. The dimensions are limited to a fixed route category, certification, approved offer, coarse campaign category, result, and test or live commerce mode.

To deduplicate and correlate those milestones without storing account, anonymous-principal, attempt, or Checkout identifiers, the server replaces application-owned UUIDs with keyed one-way pseudonyms before storage or Stripe correlation. Pseudonyms are separated by test/live mode and a bounded immutable key epoch. The epoch can change only after every retained event from the prior epoch has expired or been purged.

The analytics table cannot store arbitrary metadata and assigns each event an expiry exactly 90 days after occurrence. An application-owned retention scheduler starts immediately, uses the PostgreSQL clock, and continues pruning expired rows even when collection is disabled or its key is unavailable.

Contact and correction reports

When you use the contact or corrections form, we collect the reply email address, any optional name, the category and subject, and the message or correction details you submit. Correction reports can also include a WebLizard Labs page URL, certification code, revision identifier, and public source URL.

We use this information only to respond to the inquiry or investigate the reported content. The website sends the report through Azure Communication Services to our monitored Microsoft 365 support mailbox. The application does not store a second copy in its database, but Microsoft systems and the mailbox process and retain the message.

Microsoft Clarity

Public pages use Microsoft Clarity to collect cookieless, per-page interaction and usage information. Clarity Consent V2 is set to deny both analytics storage and advertising storage, so the integration does not set Clarity cookies or persist a visitor identity across pages.

Clarity is not loaded on the contact and corrections pages or on authentication, account dashboard, diagnostic, lab, practice-session, commerce, or workforce operations routes.

Google Analytics

Google Analytics is optional and remains off until you choose Allow analytics. We store that choice in this browser's local storage. Rejecting optional analytics keeps the Google tag unloaded; you can change the choice later through Analytics settings in the footer.

When allowed, Google Analytics measures visits and navigation on successful public pages. Page locations use the canonical public URL without query strings or fragments; same-site referrers omit query strings and fragments, while external referrers are reduced to their origin. Advertising storage, advertising user data, advertising personalization, Google signals, and ad-personalization signals remain disabled.