Privacy Policy

A plain description of what this site actually collects, stores, and does with it.

Last updated: August 21, 2026

We collect your email only if you sign up for the newsletter — nothing else, ever.

Analytics is cookieless (Cloudflare Web Analytics) — no tracking, no cross-site profiles.

No ads, no ad trackers, no cookies of any kind, anywhere on this site.

Your email is never sold, rented, or shared with any third party.

What We Collect

  • Newsletter subscribers: just an email address, submitted voluntarily through the signup form.
  • Page feedback (the "Was this helpful?" widget): just the page path and a yes/no — nothing that identifies who submitted it.
  • Analytics: aggregate page-view counts via Cloudflare Web Analytics, which doesn't use cookies or track individuals across sites.

What We Don't Do

  • No cookies of any kind, on any page.
  • No Google Analytics, Facebook Pixel, or similar third-party ad trackers.
  • No selling, renting, or sharing your data with anyone.
  • No cross-site tracking or ad profiles built from your visit.

How Your Email Is Used

An email address submitted through the newsletter form is stored solely to send updates about new PBIDocs content. It's stored in Cloudflare's D1 database — the same infrastructure that hosts the rest of the site — and isn't used for anything else, analyzed, or shared with any third party.

Removing Your Data

There isn't a self-service unsubscribe link yet. To have an email address removed, open an issue on GitHub and it will be deleted.

Third-Party Services

PBIDocs runs entirely on Cloudflare — Pages for hosting, D1 for the newsletter and feedback data, and Web Analytics for traffic counts. Cloudflare's own privacy practices apply at the infrastructure layer; see Cloudflare's privacy policy for how they handle data as the hosting provider.

Changes to This Policy

This page may be updated as the site changes. Meaningful changes will be reflected here, with the date at the top kept current.

Questions

Open an issue on GitHub, or see the FAQ for common questions about the site itself.