Privacy Policy
Last updated: June 2026
TL;DR
No accounts. No cookies. Calculator answers stay in your browser unless you share a result URL. Vercel may process standard server logs and anonymous performance metrics for Core Web Vitals. The site uses your device's system fonts rather than externally loaded web fonts.
Overview
This Privacy Policy describes how Scott Hazlitt (“I”, “me”, or “the operator”) handles information in connection with the Manitoba AI Disruption Explorer website at aidisruption.ca (the “Site”). This policy is intended to comply with the Personal Information Protection and Electronic Documents Act (PIPEDA) and applicable Canadian privacy law.
Information I collect
I collect no personal information directly. The Site is a read-only research and exploration tool. There are no accounts, no login, no forms that submit data to my servers, and no marketing analytics or advertising trackers installed by me.
Assessment inputs stay in your browser. When you use the AI Risk Calculator, your answers (business size, sector, AI readiness) are processed in the page and are not submitted through a form or stored in an account.
Shared result links store your assessment choices in the page URL. If you copy, share, or revisit a result link, the encoded URL can be requested by your browser and handled by the hosting platform. URLs may be included in standard Vercel request logs. Do not put confidential business information into the calculator.
No cookies are set by this Site. There are no tracking cookies, session cookies, or persistent cookies placed by this Site.
Information collected by third-party services
The Site is hosted on Vercel (Vercel Inc., San Francisco, CA, USA). As with any web hosting provider, Vercel's infrastructure automatically receives standard HTTP request data when you visit the Site — this may include your IP address, browser type, operating system, referring URL, and the date and time of your request. This is standard server log data processed by Vercel as part of delivering the service.
Vercel's handling of this data is governed by their Privacy Policy. Vercel is a US-based company; your request data may be processed in the United States.
The Site uses a system font stack instead of externally loaded web fonts. Your browser should render text with fonts already available on your device, so the Site does not need to request font files from Google Fonts or another font delivery service.
The Site uses Vercel Speed Insights to collect anonymous performance metrics such as Core Web Vitals, browser, device type, country, route, and metric attribution. Vercel describes these data points as anonymous and not tied to an individual visitor or reconstructable browsing session.
Production field performance evidence
Core Web Vitals evidence pending. Vercel Speed Insights is installed in code and gated to Vercel deployment or explicit opt-in, but the public product still needs production traffic evidence before it should be described as a 9.5/10 production release. Anonymous performance metrics are used only to confirm whether the deployed public site is fast, responsive, and visually stable in real browsers.
The required field metrics are Largest Contentful Paint, Interaction to Next Paint, and Cumulative Layout Shift, each with a good production-traffic rating.
Largest Contentful Paint (LCP)
Required target: good. Status: pending production traffic evidence.
Production traffic evidence showing LCP rated good for the public release candidate.
Interaction to Next Paint (INP)
Required target: good. Status: pending production traffic evidence.
Production traffic evidence showing INP rated good for the public release candidate.
Cumulative Layout Shift (CLS)
Required target: good. Status: pending production traffic evidence.
Production traffic evidence showing CLS rated good for the public release candidate.
Field evidence collection matrix
The production review must collect one completed production field evidence row covering all 13 public routes and all three required Core Web Vitals before the field-performance blocker can move from pending to verified.
| Metric | Route coverage | Evidence to record | Pass standard |
|---|---|---|---|
| Largest Contentful Paintlcp | 13 public routesVercel Speed Insights or a comparable production RUM export for the deployed release candidate. | Provider or RUM source; HTTPS production domain; Date range and timezone; All 13 public routes in scope; Traffic sample or low-traffic caveat; Reviewer and review date; p75 value, unit, rating, durable evidence artifact location, and reviewer summary | Production traffic rating is good for the deployed release candidate.Failure severity guidance: Blocker if LCP is not good or route coverage is missing; serious if the sample or p75 evidence is ambiguous; minor if reviewer notes need cleanup; pass only when evidence is recorded. |
| Interaction to Next Paintinp | 13 public routesVercel Speed Insights or a comparable production RUM export for the deployed release candidate. | Provider or RUM source; HTTPS production domain; Date range and timezone; All 13 public routes in scope; Traffic sample or low-traffic caveat; Reviewer and review date; p75 value, unit, rating, durable evidence artifact location, and reviewer summary | Production traffic rating is good for the deployed release candidate.Failure severity guidance: Blocker if INP is not good or route coverage is missing; serious if interactive routes are under-sampled; minor if reviewer notes need cleanup; pass only when evidence is recorded. |
| Cumulative Layout Shiftcls | 13 public routesVercel Speed Insights or a comparable production RUM export for the deployed release candidate. | Provider or RUM source; HTTPS production domain; Date range and timezone; All 13 public routes in scope; Traffic sample or low-traffic caveat; Reviewer and review date; p75 value, unit, rating, durable evidence artifact location, and reviewer summary | Production traffic rating is good for the deployed release candidate.Failure severity guidance: Blocker if CLS is not good or route coverage is missing; serious if layout-shift outliers lack a rationale; minor if reviewer notes need cleanup; pass only when evidence is recorded. |
Completed production field evidence
A completed production-performance claim must record provider, production domain, date range, route coverage, traffic sample, reviewer, and metric-level LCP, INP, and CLS evidence.
No production field Core Web Vitals evidence recorded yet.
Evidence to collect
- Vercel Speed Insights or comparable RUM evidence for LCP, INP, and CLS after the release candidate is deployed.
- One completed production field evidence row covering all 13 public routes, including date range, production domain, and route coverage for the field-performance review.
- Traffic volume or sample-size caveat so low-traffic results are not overinterpreted.
- Reviewer name, review date, and explicit pass/fail note for each required metric.
- Any route-level performance outliers and the mitigation or acceptance rationale.
This artifact documents the evidence required for a 9.5 production claim; it does not prove that production traffic has met the targets.
How information is used
I do not collect, use, sell, or disclose personal information for marketing or profiling. Anonymous performance metrics are used only to understand whether the Site is fast, responsive, and stable in real browsers after deployment. All data displayed on the Site (occupation scores, sector data, industry statistics) is derived from publicly available academic research and Statistics Canada datasets — it does not contain personal information about individual visitors.
Your rights under PIPEDA
Under PIPEDA, you have the right to access personal information held about you and to request corrections. Because this Site collects no personal information about visitors, there is generally nothing to access or correct.
If you believe the Site has inadvertently collected or published your personal information, please contact me at scott@scotthazlitt.ai. I will respond within 30 days.
Contact
For privacy-related questions or concerns, contact:
If you are not satisfied with my response, you may contact the Office of the Privacy Commissioner of Canada.
Changes to this policy
If this policy is updated, the “Last updated” date at the top of this page will change. Continued use of the Site after any change constitutes acceptance of the updated policy.