Privacy Policy
Last updated: October 2026. This policy explains, in plain language, how The Main Story handles personal information. It is written for the Canadian context, including the federal Personal Information Protection and Electronic Documents Act (PIPEDA), Quebec's Law 25, and Canada's Anti-Spam Legislation (CASL).
What we collect
We collect as little as possible:
- Email address — only if you subscribe to The Morning Edition. Subscribing is your consent to receive our emails (CASL), and you can unsubscribe at any time — your address is removed from our records immediately. We store the address in our own database and never sell or rent it.
- Consent preferences — your cookie choice is stored locally in your browser, not on our servers.
- Basic technical data — our hosting provider (Cloudflare) processes standard technical information (such as IP address and browser type) to deliver the site and protect it from abuse. This is necessary for the site to function.
Cookies and third parties
A cookie is a small text file stored in your browser. We use a consent banner for any non-essential cookies and third-party resources. When you accept:
- Google Fonts may be loaded to display the site's typography. If you decline, the site uses local fonts and works the same.
- Advertising — when ad placements are active, advertising partners may set cookies for measurement and frequency capping. No ads are served until you have consented via the banner.
- Social media links — buttons linking to X, Facebook, Instagram and YouTube only load those services' content when you click them.
Cloudflare Web Analytics — we measure readership with Cloudflare's cookieless analytics: how many visits a story gets, which pages and referrers bring people in, rough country and device class, and page-speed (Core Web Vitals). It sets no cookies, does not fingerprint you, does not track you across other sites, and reports only aggregate counts — we never see an individual reader. Because it involves no cookies and no personal information, it runs without a consent prompt; the cookie banner still governs advertising and any other non-essential third party.
How we count a read
Hosting logs count requests, and requests are not readers: a search engine crawling a story, a chat app fetching a link preview, or a monitoring script pinging the site all produce requests. So we count a read in two layers, and we only report the second one as a reader.
- Request totals come from our hosting provider and are reported separately, with automated traffic counted and labelled as such. We classify each request from its browser identification string and its network — never from its content, and never from anything you typed.
- A confirmed read is signalled by your browser only once a page has actually been open and visible on screen for several seconds. That signal carries three things: the page address, how long the page was open, and how long it was visible. It sets no cookie and writes nothing to your device.
- Counting unique readers uses a one-way key derived from a masked IP address, the browser identification string and the date. It cannot be reversed to an address, it changes every day, and it is never joined to your account, your email or your comments. To count one reader per story per day we have to hold it for that day only.
- What we keep is aggregate: reads per story per day, and a bounded list of browser identification strings (truncated, with no address attached) kept for 90 days so we can tell a real browser from a scanner. Daily counts carry no IP address and no identifier that survives the day.
- What is excluded: signed-in staff viewing the site, draft preview links sent to authors and sources, and browsers that send Do Not Track or Global Privacy Control. Those requests are dropped before anything is counted.
This is why a story can show fewer "reads" than the request count, and why we would rather report a smaller, defensible number than a larger one that includes robots.
Comments and social sign-in
Readers can comment on stories by signing in with Google or Facebook. When you sign in, that provider shares only the basics needed to identify you — your name, profile photo and email address — and we use that information solely to display your identity beside your comments and to moderate the discussion.
- What we store: your name, profile photo and email address from the provider, plus the comments you post and any reports you make.
- Why: real identities keep the conversation civil, and Canadian law requires us to know who stands behind content we publish in a discussion forum.
- Sign-in is a choice: Google and Facebook are the only sign-in options; there is no anonymous commenting. You can sign out at any time, and you are not required to comment to read the site.
- Third parties: your sign-in itself is handled by Google or Facebook under their own privacy policies — we never receive or store your password.
- Deletion: you can erase your own reader data — your sign-in profile, comments and reports — at any time while signed in. You can also ask us at submit@themainstory.ca and we will remove it.
Comments are moderated. We may remove comments that violate our Terms and block repeat offenders.
Your rights
- Access and correction — you may ask us what personal information we hold about you and have it corrected (PIPEDA).
- Withdraw consent — you can change your cookie choice at any time by clearing this site's data in your browser, and you can unsubscribe from The Morning Edition at any time with the unsubscribe link, which deletes your address from our records.
- Quebec residents — Law 25 gives you additional rights, including the right to know how your information is used and to request its deletion in certain cases.
Contact
Privacy questions: submit@themainstory.ca.
This policy is not legal advice. If you believe your rights have been affected, you may contact the Office of the Privacy Commissioner of Canada.
— 30 —