Privacy Policy

We believe in total transparency. Here is exactly how your data moves.

Last Updated: January 17, 2026

1. Architecture Overview

Bank Data Manager operates as a pass-through tool between your Excel workbook and your bank. We prioritize client-side processing to minimize data exposure.

Data Flow:
Excel (Your Device)  →  Cloudflare Worker (Our Proxy)  →  GoCardless (Provider)  →  Your Bank

2. Data We Store

To provide our service and enforce licensing, we persist minimal metadata. This data is stored in a secure Cloudflare D1 database.

  • License Keys

    We store your unique license key to validate your subscription status.

  • Connected Bank Names

    We record the name of connected banks (e.g., "Deutsche Bank") solely to enforce connection limits (e.g., max 3 banks).

3. Data We Process (But Do NOT Store)

The following data passes through our secure proxy to reach your Excel sheet but is never saved, logged, or retained on our servers:

  • Transaction History: Dates, amounts, merchant names, and descriptions flow directly to your device.
  • Account Balances: Real-time balance data is transient.
  • Requisition IDs: The technical identifiers for bank connections are used instantly and discarded.

4. Data We NEVER See

We strictly adhere to PSD2 (Open Banking) security standards.

Bank Credentials
We never ask for, see, or store your bank username, password, or PIN. You enter these directly on your bank's secure portal during the initial connection setup (facilitated by GoCardless).

5. Third-Party Processors

We use trusted infrastructure partners to deliver this service:

  • GoCardless (formerly Nordigen): Provides the authorized Open Banking API to connect with 2,300+ institutions.
  • Cloudflare: Hosts our secure Worker functions and database (D1).

6. Contact Us

For any privacy concerns or data deletion requests, please contact us directly.