BankSync
The data promise

Your data is not training data.

BankSync does not sell your banking data or use customer banking data inside the BankSync Boundary to train AI models. Here is exactly where the boundary sits.

Pass-through by default

For ordinary syncs, data flows from your provider to the destination you choose. We store full banking datasets only when a feature you enable requires it, such as future BankSync Tables or another managed destination, or where needed for support, security, compliance, backups, or legal requirements.

Never sold by BankSync

We charge a subscription for the service, not for your data. Within the BankSync Boundary, we don’t sell your banking data, use it for advertising or data brokerage, or disclose identifiable banking data for another party’s independent commercial exploitation.

Never trains BankSync AI

Within the BankSync Boundary, customer banking data is not used to train AI or machine-learning models. Customer-selected destinations, AI tools, and independent providers may have their own terms, settings, and legal obligations.

how it works

Private, with a clear boundary by design

Pass-through data is temporary, managed feature data stays inside the BankSync Boundary, and BankSync does not train models on customer banking data.

Regulated open banking, no stored passwords

You authorize each connection through your bank’s own consent screen via open banking, CDR, or PSD2. BankSync never sees or stores your banking credentials, and you can revoke any connection from your bank at any time.

An in-memory edge-worker pipeline

Each pass-through sync runs inside a short-lived edge worker close to you. Financial data is forwarded to your destination and discarded after the sync, unless the destination is a BankSync-managed feature you enabled.

Encrypted in transit and at rest

All data is encrypted in transit with TLS, and the operational metadata we do keep is encrypted at rest with AES-256, the same standards used by major financial institutions.

Your AI reads, it doesn’t train

Point Claude or ChatGPT at your workspace with one API key over a secure connection (MCP). BankSync does not use that data to train models inside the BankSync Boundary. Your chosen AI tool may have its own terms and settings.

What we keep, and what we never touch

We’re specific about this on purpose. Here is the honest line.

Operational metadata we retain

  • Feed and sync configuration (which accounts map to which destinations)
  • Sync logs and operational metadata needed to run and audit your syncs
  • Account and workspace settings, billing, and team membership
  • Data you choose to store in BankSync-managed features, such as future BankSync Tables

Financial data we do not keep for sale or training

  • Your banking passwords or credentials
  • A pass-through copy of your transactions, balances, or account details after delivery
  • Any copy of your financial data kept to sell, advertise, broker data, or train BankSync AI
The full security approach →Compliance & architecture →Privacy policy →

Data & AI privacy FAQs

Does BankSync use my financial data to train AI?
No. Within the BankSync Boundary, customer banking data is not used to train AI or machine-learning models. When you connect your own AI assistant over our secure MCP connection, BankSync does not use that data for model training. Your chosen AI tool, destination, or independent provider may have its own terms and settings.
Does BankSync store my bank transactions and balances?
Pass-through sync data is discarded after delivery to your destination. BankSync stores transactions, balances, or account details only where you enable a managed feature that requires storage, such as future BankSync Tables, or where needed for support, security, compliance, backups, or legal requirements.
Do you sell or monetize my financial data?
No. We charge a subscription for the service, not for your data. Within the BankSync Boundary, we don’t sell banking data, use it for advertising or data brokerage, or disclose identifiable banking data for another party’s independent commercial exploitation.
What data does BankSync actually keep?
Operational metadata such as feed and sync configuration, sync logs, account and workspace settings, billing, and team membership. If you enable a BankSync-managed destination or future BankSync Tables, we also store the data required to provide that feature until deletion, subject to backups and legal, compliance, security, billing, or dispute-retention requirements.
Are my banking credentials stored?
No. You authorize each connection through your bank’s own consent screen via regulated open banking, CDR, or PSD2. BankSync never sees or stores your banking passwords, and you can revoke any connection from your bank at any time.
How is this different from screen-scraping aggregators?
Screen-scraping tools often store credentials and retain copies of your data, sometimes to analyze or monetize it. BankSync uses regulated open banking, does not store banking credentials, treats pass-through data as temporary, and does not use customer banking data inside the BankSync Boundary to train AI models.
Can I get this in writing for a security review?
Yes. On the Enterprise plan we provide a custom DPA plus NDAs and mutual NDAs on vendor-standard terms, along with audit logs and SSO/SAML. See /enterprise or talk to sales.

Move your bank data without giving it away

Start a free trial, or talk to sales about Enterprise terms for your security review. Either way, BankSync does not sell your banking data or use it inside the BankSync Boundary to train AI.

Start free trialEnterprise terms