We do not store bank passwords
Open Banking uses provider authorization. Purely never asks you to enter a bank password in Purely.
Security Center
Trust controls for your financial workspace
Purely is designed for accountant-ready reporting, not custody or payment initiation. Learn how bank data, CSV imports, tokens, exports and deletion controls work.
Bank access is read-only
Connected bank data imports balances and transactions for reporting. Purely cannot initiate bank payments.
Tokens are encrypted
Provider credentials and refresh tokens are encrypted before storage and excluded from user-facing exports.
You can remove sources
Delete a source or revoke Open Banking access to remove the connection and its synced workspace data.
You can export or delete your data
Privacy settings include JSON export, workspace deletion, account deletion and session revocation.
CSV uploads stay under your control
CSV files become auditable import batches. You can undo a batch and exports omit raw provider payloads.
Sensitive data is not sold
Purely does not sell sensitive financial data. Account, source and transaction data is used only to provide imports, categorization, analytics, Month Close, reports, exports and subscriptions.
User exports are sanitized to include useful workspace records without encrypted provider tokens or raw bank payloads.
Contact security
For account support, privacy requests or a suspected security issue, contact: