Privacy Policy for Batch Statement Downloader

Last updated: July 31, 2026

Overview

Batch Statement Downloader is committed to protecting your privacy. Your statements, their contents, and your account information stay entirely on your device — they are never sent anywhere. The extension sends only a few minimal diagnostic signals to our own server (batchdownloader.com), each of which is described in full below in What We Send to Our Server. The site you request via "Request a bank" is kept strictly first-party; anonymous onboarding and uninstall counts are recorded in Google Analytics. We use no advertising or cross-site tracking, and we never sell your data.

What We Collect

The extension stores the following data locally on your device only:

Download History

  • Statement dates (as shown on bank websites)
  • Statement types (e.g., "Account Statement", "Tax Document")
  • Download timestamps
  • Filenames of downloaded PDFs
  • Bank identifiers (e.g., "chase", "wexhealth")

Usage Statistics

  • Total number of downloads
  • Number of banks used
  • First and last usage dates
  • Per-bank download counts

What We Send to Our Server

To keep the extension working and improving, it sends a small number of minimal, first-party signals to our own server at batchdownloader.com. These are the only data that ever leave your device. None of them contain your statements, account numbers, balances, credentials, or any statement content, and none carry a persistent identifier for you.

SignalWhen it is sentWhat it contains
"Request a bank"Only when you click the "Request a bank" button on a site the extension does not yet supportThe hostname of that site (e.g. example.com) and the extension version — nothing else. This lets us know which banks to add. It is sent only on your explicit click, is labeled in the popup ("Sends only the site address"), and is remembered locally so it is not sent twice. This one is kept strictly first-party — it is stored on our own server and is never forwarded to Google Analytics or any third party.
OnboardingOn first install, when the welcome page loads and if you start a tutorial videoAn anonymous event name (e.g. page_load, video_start) and the extension version. No identifiers. Recorded in Google Analytics as an aggregate, de-identified event (a random per-event id; your IP address is not forwarded to Google). Helps us see whether the setup instructions are working.
UninstallOnce, if you uninstall the extension (Chrome opens our uninstall page)Aggregate counters only: extension version, total number of downloads, and days since install — recorded in Google Analytics. No filenames, no bank names, no dates of individual statements. Because this is a normal page visit, our uninstall page loads Google Analytics like any website (see Third-Party Services). That page also offers an optional feedback form — see below.

As with any web request, our server receives standard network request metadata (such as your IP address); we do not use it to build a profile of you, and we do not combine it with any of the local data above. We do not sell any of this data. The only outside services that ever touch it are the service providers that operate our website and analytics, acting on our behalf — see Third-Party Services.

Optional uninstall feedback form

The uninstall page shows a short, optional feedback form. It is never submitted unless you fill it in and click send. If you choose to submit it, we store your answers (the reason you selected and any details you type), the aggregate counters above, and a one-way hashed version of your IP address for spam prevention (the raw IP is not stored). If — and only if — you type an email address so we can follow up, we store that too. This is used solely to improve the extension; it is never sold or used for advertising.

What We DO NOT Collect

We never access, collect, store, or transmit:

  • Your banking credentials (usernames, passwords)
  • Account numbers or balances
  • Personal identifying information (PII)
  • The contents of your downloaded statements
  • Any data from banking websites beyond publicly visible statement metadata
  • Your browsing history — we do not track the sites you visit. The only site address that ever leaves your device is the single hostname you choose to send by clicking "Request a bank" (see above).
  • Advertising identifiers, device fingerprints, ad-network cookies, or cross-site tracking IDs

How Data is Stored

All data is stored locally using Chrome's storage.local API. This data:

  • Remains entirely on your device
  • Is never transmitted to us as-is — your download history and per-statement details stay local. The only exception is the aggregate uninstall counters described in What We Send to Our Server (a total download count and days installed, no individual records)
  • Is never shared with or sold to third parties
  • Is isolated to this extension only

How to Delete Your Data

You can delete all stored data at any time:

  1. Right-click the extension icon
  2. Select "Options"
  3. Click the "Clear All" button at the bottom of the page

Alternatively, uninstalling the extension will remove all data automatically.

Permissions Explained

The extension requests the following permissions:

PermissionWhy We Need It
activeTabDetects when you're on a supported bank's statement page
downloadsRequired to save and rename files to your computer
storageStores download history locally in Chrome storage

Host Permissions

We only request access to specific banking domains where the extension works:

  • https://secure.chase.com/* — Chase Bank
  • https://global.americanexpress.com/* — American Express
  • https://card.discover.com/* — Discover Card
  • https://benefitslogin.wexhealth.com/* — WEX Health / HSA
  • https://rocket.com/* — Rocket Mortgage

We never request access to all websites (<all_urls>). Access is limited only to supported banking domains.

Third-Party Services

We do not use any advertising networks, data brokers, or cross-site trackers, and we never sell your data. To operate the website and understand aggregate usage, we rely on a small number of service providers that act on our behalf:

  • Google Analytics — aggregate, de-identified product and website analytics (the onboarding and uninstall signals above, and ordinary visits to batchdownloader.com). The "Request a bank" hostname is not sent to Google Analytics.
  • Vercel — hosts the website and the database where first-party data (such as "Request a bank" entries and any feedback you submit) is stored.
  • Resend — delivers us an email notification when you submit the optional uninstall feedback form.

Chrome Web Store Limited Use

Our collection and use of information received from the extension adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements. We use the data described above solely to provide and improve the extension's single purpose — helping you download your own statements. We do not sell it, use it for advertising, or use it to determine creditworthiness or for lending purposes. The only parties it is shared with are the service providers listed under Third-Party Services, who process it on our behalf.

Changes to Banking Websites

The extension only:

  • Reads publicly visible statement information (dates, types, account names)
  • Clicks download buttons on your behalf when you select statements
  • Does not modify, intercept, or interfere with banking website functionality

Children's Privacy

This extension is not intended for use by children under 13. We do not knowingly collect data from children.

Updates to This Policy

We may update this privacy policy as the extension evolves. Changes will be posted on this page with an updated "Last updated" date.

Contact

If you have questions about this privacy policy or the extension:

Summary: Your statements and account data stay on your device. The only data we receive are a few minimal diagnostic signals — a bank you request (kept strictly first-party), anonymous onboarding events, and aggregate uninstall counters — never your statements, and never sold. We use no advertising or cross-site tracking.