Privacy Policy

Last updated: November 14, 2026

Overview

Analytics Pitfalls & Principles ("we," "us," or "our") operates analyticspitfalls.com. This policy explains how we collect, use, and protect information when you use our site, purchase products, or interact with our content.

Information We Collect

Account information: When you create an account (via Clerk), we collect your email address and name.

Purchase information: When you purchase the Audio Pass, Stripe processes your payment. We store only your purchase status and product access — not your payment card details. You don’t need an account to buy: if you have none, we create one with the email address you give at checkout (no password; you sign in with a code sent to that address), so the audiobook follows you to any device. If that address already has an account, the audiobook is added to it.

Usage data: We collect listening progress (chapter position, playback speed) to let you resume where you left off. We do not sell this data.

Assessment responses: When you take the Analytics Leadership Mirror assessment, your results are generated in your browser. No account is required.

Anonymous benchmark data: Unless you untick the box on the assessment’s start screen, we store your answers anonymously when you finish, along with the scores and pattern they produce and how long the assessment took. We do not store your name, email, IP address, or anything else that identifies you, and this record is not linked to your email even if you also request a reading guide. We use it only to build benchmarks — for example, how a team’s results compare with other analytics teams. If you untick the box, nothing about your assessment is stored.

Team assessments: If you take the assessment through a team link, your anonymous record is grouped with your team’s. Whoever runs the team assessment sees only combined team results, never an individual’s answers or pattern, and only once at least three people have finished.

Reading guide: If you choose to enter your email to receive a personalized reading guide, we store your email address, pattern name, and dimension scores in our database. If you share your results (e.g., via social sharing), only a summary of your pattern type is shared — not your individual question responses.

Your Quarter: If you start a quarter, we store what you write there — what you are working on, how you will know, your notes, your scores and your reflection — together with your pattern name and the quarter’s dates. It is kept with your account, which is why saving a quarter needs a sign-in: so that it follows you from one device to another and is not lost when a browser is cleared. Only you can read it. We do not show it to anyone, we do not use it in marketing, and we never quote it. If you ask for them, we email you a copy when you save it, a question every Saturday or on the last day of each month (your choice), and one email on the quarter’s last day, to the address on your account; every email has a link that stops them with one click. We count how many quarters are started, how many notes are added and how many quarters are scored — the counts only, never the words. The “Delete my quarter” button on the page deletes a quarter from our database immediately and permanently. Until you sign in, a quarter you are writing is held only in your own browser.

The Second Factory early-reader list: If you sign up on the Second Factory page, we store your email address, the number of team copies you mention (if any), which of our posts brought you to the page (if a link said so), and when you confirmed and unsubscribed. We send one email to confirm the address, then the rest of Chapter 1 and news about the book. Every email has an unsubscribe link. If you mention team copies, Brian gets your address and the number by email so he can reply. Your address is never sold, shared or shown to anyone else; the marketing tools behind this site see only counts.

The Founding Readers’ Club: If Brian invites you to read a book before it is published, we store your invitation (your email address, your name and his note, as he wrote them), the name you choose for the room, where you are in each chapter (read and listened, separately), and the notes you leave. Other readers see only the name you chose and the notes you send to the room; a note to the room on a chapter is shown only to readers who have finished that chapter. Nobody but Brian sees your email address, how far you have read, or the notes you send to him alone. Brian never quotes anyone from the room without asking first. If you suggest someone for an invitation, we keep the name, email and reason you give, for Brian alone. We count how many invitations are accepted, chapters finished and notes left — the counts only, never a name or a word.

Book club requests: If you ask Brian to join your book club, what you enter in the form — your name, email, company or team, group size, preferred dates and anything you’d like to discuss — is sent to Brian by email so he can reply. It is not stored in our database or added to any mailing list. We keep only a note that a request came in and when, with nothing about who sent it, so Brian sees that one is waiting.

Contact form: A message sent from the contact form — your name, email, topic and message — is emailed to Brian so he can reply, the same way, and is not stored in our database or added to any mailing list. We keep only whether it was about a team and when it came in.

Analytics: We use two analytics services. Vercel Analytics counts visits without cookies and without personally identifiable information. Google Analytics tells us which pages are read and which posts or sites sent visitors here. On public pages it sets cookies (named _ga and _ga_…) that recognize a returning browser, and it sends Google the pages you visit, where the visit came from, your device and browser type, and your approximate location, which Google works out from your IP address. It never receives your assessment answers or results, what you write in Your Quarter, or your account details such as your name or email; before a page address is sent, everything in it except the page itself and the campaign tags of a link (utm_) is removed. It never reports a page that needs a sign-in, or Your Quarter. On the audiobook it is also told whether a chapter was started, played for three minutes, reached halfway and finished, whether the Audio Pass offer was shown and its button pressed, and whether checkout was opened, each with only the chapter number or where the button was. On the book page, in the Library and on the free Chapter 1 page it is told when the free Chapter 1 excerpt has been on screen for a few seconds, with only which of those three pages it was. When a link to the book on Amazon is clicked, it is told where on the page the link was and which edition it pointed to. We use it only to count these: no advertising, no remarketing, and no user IDs.

Meta Pixel: We advertise on Instagram and Facebook, and the Meta Pixel tells Meta (the company behind them) whether those ads bring people who listen. On public pages it sets a cookie (named _fbp, and _fbc when you arrive from one of our ads) and tells Meta that you visited a page, and the first time the free Chapter 1 of the audiobook has played for three minutes. With each one Meta receives the page address, your IP address and your browser type. It is told nothing else: not your name or email, not which other chapters you play, not whether you buy. It never loads on the Analytics Leadership Mirror, on Your Quarter, or on any page that needs a sign-in, so it never sees your answers, your results or what you write. Meta uses this to measure our ads and to show them to people more likely to listen; under its own terms it may also use it to choose the ads you see elsewhere.

Book link clicks: When you click a link to the book on Amazon, we count the click: which link it was, which format (Kindle, paperback or hardcover) if you chose one, and the time. We do not record who clicked — no IP address, device details, or account information — and we cannot see what you do on Amazon.

How We Use Your Information

  • To provide access to purchased products (the audiobook)
  • To save your listening progress and preferences
  • To send transactional emails (purchase confirmations) via your registered email
  • To send the emails you ask for: your reading guide, and a copy of your quarter with its weekly or monthly reminders
  • To reply to a book club request
  • To send The Second Factory’s early-reader emails, if you sign up for them
  • To improve the site based on anonymized usage patterns

We do not sell your personal information to third parties. We do not send marketing emails without your explicit consent.

Third-Party Services

We use the following services, each governed by their own privacy policies:

Your Rights

You may request access to, correction of, or deletion of your personal data at any time by emailing us. You can delete a quarter yourself, at any time, from the quarter page. Deleting your account removes your authentication data via Clerk. Purchase records may be retained for legal/tax purposes.

Cookies

We use essential cookies for authentication (Clerk session management) and functional cookies to remember your preferences. On public pages, Google Analytics sets its own cookies (_ga and _ga_…, kept for up to two years) to count visits and tell a returning browser from a new one. The Meta Pixel sets an advertising cookie (_fbp, kept for three months, and _fbc when you arrive from one of our ads) so Meta can tell whether our ads bring people who listen.

To stop Google Analytics, install Google’s opt-out browser add-on, block third-party trackers in your browser or with a content blocker, or block or delete cookies for this site in your browser’s settings. The site works the same without it.

To stop the Meta Pixel, block third-party trackers in your browser or with a content blocker; the site, the audiobook included, works the same. You can control how Meta uses activity from other sites in your Meta ad preferences.

Contact

Questions about this policy? Email us at brian@analyticspitfalls.com