Your Data Has a Boundary
Pass-through by default, managed storage only when you enable a feature that needs it.
“The safest data is the data we do not need to keep. When a feature does need storage, we draw the boundary clearly and protect it there.”
Held in V8 heap memory during sync · discarded immediately after forwarding
Operational metadata only · no transaction or balance data
What We Store
BankSync retains the data needed to run, secure, support, and audit your account. For pass-through syncs this is primarily operational metadata. For managed features, such as future BankSync Tables, it can include the financial data you choose to store in that feature.
Connection metadata
- Institution name and account type
- Consent scope and authorised data categories
- Consent status (active / expired / revoked)
Access credentials
- Tokenised connection issued by the licensed provider
- Encrypted at rest using AES-256
- Never includes raw banking credentials
Operational records
- Sync timestamps (last successful, last attempted)
- Error logs for failed sync jobs
- Feed configuration (schedule, field mappings, destination)
- Audit log of state-changing actions (connect, revoke, delete)
Managed feature data
- Records you choose to store in BankSync Tables or similar hosted features
- Feature configuration, field mappings, views, and sharing permissions
- Backups, security logs, and retention copies where required to operate safely
Stored data remains inside the BankSync Boundary while it is in systems we control. If you export, share, sync, or copy it elsewhere, that outside destination is governed by your settings and that provider's terms.
What Is Pass-Through by Default
Unless you enable a managed feature that requires storage, the following financial data categories are handled as pass-through sync data and discarded after delivery to your destination.
- Transaction history (amounts, dates, descriptions, merchant categories)
- Account balances (current and available)
- Account holder details
- Portfolio holdings and trade history (investment connections)
Technical detail: Transient data enters memory in an edge worker sync step spawned in the region closest to you. It is held for the duration of the sync and forwarded to your destination, unless the destination is a BankSync-managed feature you enabled.
The Edge Worker Model
Each sync runs inside a short-lived edge worker - a lightweight execution environment that is spun up for the duration of the sync and then discarded. There is no shared long-running process that accumulates financial data over time.
- Regional: Spawned in the region closest to you, reducing data transit distance during processing.
- Ephemeral: Created for one sync, then destroyed. No state persists between sync runs.
- Storage-aware:Pass-through sync data is discarded after the job completes. Managed feature data is stored only for the enabled feature and governed by that feature's controls.
Technical detail: Reducing stored data reduces breach impact, but no system can promise zero risk. BankSync protects data inside the BankSync Boundary and treats customer-selected destinations and independent providers as separate environments.
When You Delete
When you revoke consent or delete your account, stored connection metadata, encrypted access tokens, and BankSync-managed feature data are queued for deletion from active systems, subject to backup, legal, compliance, security, billing, and dispute-retention requirements.
Data already delivered to customer-selected destinations remains in those destinations unless you delete it there. BankSync cannot delete copies in Google Sheets, Notion, Airtable, Slack, email, APIs, webhooks, or other outside systems that you control.
Deletion removes data from the BankSync Boundary. Customer destinations and independent providers have their own deletion tools, retention periods, and legal obligations.
Secure by Design
Your financial data is pass-through by default and stored only when an enabled feature needs it.
14-day free trial • Cancel anytime