What we collect
Purely stores account profile data, connected source metadata, accounts, transactions, categories, rules, reports, CSV import batches, and billing state needed to operate the product.
Last updated: April 30, 2026. This page explains what Purely stores, how CSV and bank connection data is handled, and which controls are available to export, revoke, or delete data.
Purely stores account profile data, connected source metadata, accounts, transactions, categories, rules, reports, CSV import batches, and billing state needed to operate the product.
Bank connections use provider authorization flows. We do not store bank passwords. Where Open Banking access is available, it is used as read-only access for balances and transactions.
Provider tokens are encrypted before storage. User exports exclude encrypted tokens and raw provider payloads by default so exports remain useful without exposing unnecessary sensitive material.
CSV files are parsed into import batches. Parsed transactions are stored in your workspace, and you can undo a batch from privacy settings when you need to remove imported rows.
We use your data to import sources, clean transactions, show analytics, create accountant-ready reports, manage subscriptions, detect errors, and keep the service secure.
Purely does not sell sensitive financial data. We may use trusted infrastructure providers to run the service, but they do not receive data for independent sale.
Signed-in users can manage these controls from settings. Destructive actions require an authenticated session, use CSRF protection for cookie-authenticated requests, and are recorded as audit events.
For privacy requests, account help, or security concerns, contact support or security.