Buzzkill is a Chrome extension that highlights corporate jargon in Gmail and on LinkedIn, warns you before you send it, and ranks the jargon-heaviest senders in your inbox and the most corporate posters in your LinkedIn feed. This policy explains what the extension touches and where that information goes.
The short version: Everything the Buzzkill extension does to your content happens inside your own browser. No account, no server, and no tracking by the extension. The one and only network request it makes is to fetch a small settings file on startup, and that request carries none of your data. Your email content, the posts you read, the addresses you read, and your stats never leave your computer.
To do its job, Buzzkill reads the following while you use Gmail:
On LinkedIn, Buzzkill reads the text of posts shown in your feed so it can highlight jargon there too. This reading happens inside the page, just like on Gmail, and nothing is sent anywhere.
Buzzkill saves the following using your browser's local storage (the storage permission). This data stays on the device and is not synced or uploaded:
Gmail and LinkedIn rename their page structure often, which can stop Buzzkill from finding the right text to highlight. To keep working without a full extension update, Buzzkill fetches a small settings file from the developer's GitHub Pages site once when it starts up. This file only tells Buzzkill where to look on the page. The request is one-way: it asks for the file and nothing about you, your email, the posts you read, or your stats is attached or sent. If the fetch fails, Buzzkill falls back to the settings built into the extension.
storage: Saves your settings and stats locally in the browser. Nothing is synced or uploaded.
Host access to mail.google.com (required): Buzzkill runs on Gmail by default. This access lets it read the email or draft you are working with so it can highlight jargon and guard your sends. All of that processing happens inside the page.
Host access to linkedin.com (optional): LinkedIn support stays off until you turn it on in Settings. Only then does Buzzkill ask for permission to run on linkedin.com, where it reads the text of posts in your feed to highlight jargon. You can revoke it any time by turning LinkedIn back off, which removes the permission.
Host access to the developer's GitHub Pages site: Used only for the one-way settings fetch described above. That request is made from the extension's own background process, not from your Gmail or LinkedIn tab, and carries nothing about you.
scripting and background: Let Buzzkill switch LinkedIn support on or off when you toggle it, and run the small background process that performs the settings fetch.
Open the Buzzkill popup and use "Reset stats" to clear your usage data. Removing the extension from Chrome deletes everything it stored. There is nothing held anywhere else to delete.
The Buzzkill extension itself collects nothing, as described above. This marketing site (usebuzzkill.com) is separate, and it uses Microsoft Clarity to understand how visitors use the pages so we can improve them. Clarity records anonymized interaction data (clicks, scrolls, and session replays) and sets cookies to do so. It does not run on the license redemption pages, and it has no access to your email, your stats, or anything inside the extension. See Microsoft's privacy statement for how Clarity handles that data, and you can block it with any tracking or cookie blocker.
If this policy changes, the updated version will be posted at this address with a new effective date.
Questions about this policy can go to patrick@patrickfrank.com.