SignalCrate Fresh, verifiable datasets from live web sources — updated automatically

Privacy Policy — Attachment Downloader for Gmail™

This is the privacy policy for the Attachment Downloader for Gmail™ Chrome extension. It describes exactly what the extension reads, stores, and transmits.

What the extension reads

When you have a Gmail message open, the extension reads the attachment links (the download_url attributes) that Gmail itself already renders on the page, so it can show the download button and fetch the files when you click it. To build the filename of the .zip it creates for you (a paid feature), it also reads an identifier for the sender of the open message — Gmail's markup exposes this as the sender's email address, and the extension falls back to the displayed sender name only if no address is present; either value is used solely to construct a local filename such as sender_2026-07-12_attachments.zip and is not transmitted anywhere. None of this reading happens unless you have a Gmail tab open; the extension does not run on any other site.

What happens to your files

Attachment bytes are fetched directly from Gmail's own servers, inside your own already-signed-in browser session, and are downloaded straight to your computer or bundled into a .zip locally in your browser. This all happens on your machine. Your email content and attachment files are never sent to the developer of this extension or to any server the developer operates — there is no such server. Nothing about your email content or attachments is transmitted anywhere by this extension.

What is stored, and where

The extension's own code stores two small pieces of state in your browser's local extension storage (chrome.storage.local): a cached copy of your Free/Pro purchase status (so the extension keeps working briefly if the license check is momentarily unreachable), and a one-time flag recording whether the upgrade page has already been shown once. Neither of these contains any email content, attachment data, or personal information.

Separately, the bundled ExtensionPay payment library keeps its own small records — an anonymous per-install API key, an install timestamp, and a cached copy of your purchase status object — using chrome.storage.sync when your browser has Chrome Sync available (falling back to chrome.storage.local otherwise). Data written to chrome.storage.sync is synced by Google across the devices signed in to your Chrome profile, the same as any other browser extension's synced settings. None of these ExtensionPay records contain your email content, attachments, or Gmail account details.

What the payment processor sees

The one-time Pro upgrade ($12, no subscription) is handled by ExtensionPay, a third-party payment processor, using Stripe for the actual card processing. When you check your purchase status or open the upgrade page, the extension contacts ExtensionPay's servers with only an anonymous, extension-generated API key — never your email content, attachments, or Gmail account details. If you choose to pay, you enter your payment details directly on ExtensionPay/Stripe's own hosted checkout page; this extension's code never sees or stores your card details.

What this extension does not do

It does not use the Gmail API or OAuth, and it never requests or receives access to your Google account. It does not run any analytics or tracking code, and it collects no browsing history. It does not sell or share any data with anyone; the only data leaving your browser at all is the anonymous ExtensionPay purchase check described above.

Contact

Questions about this policy or the extension can be sent through the Chrome Web Store listing's Support tab for Attachment Downloader for Gmail™.

Not affiliated with or endorsed by Google. “Gmail” is a trademark of Google LLC.