What we collect
Purely stores profile data, source metadata, accounts, transactions, categories, rules, reports, Month Closes, supporting documents, CSV batches and billing state needed to operate the product.
Last updated: October 4, 2026. This page explains what Purely stores, how uploaded financial files are handled, and which controls are available to export or delete data.
Purely stores profile data, source metadata, accounts, transactions, categories, rules, reports, Month Closes, supporting documents, CSV batches and billing state needed to operate the product.
Purely stores financial data that you choose to upload, such as bank statements and CSV files. Your uploaded data remains in your workspace until you choose to delete it.
CSV files are parsed into import batches. Transactions are stored in your workspace and a batch can be undone from privacy settings.
We use data to import sources, clean transactions, run Month Close, show analytics, create reports, manage subscriptions, detect errors and secure the service.
Purely may use artificial intelligence and machine learning technologies to provide certain features, such as transaction categorization, financial analysis, summaries, and other product functionality. Where required, data may be processed by third-party AI service providers acting on our behalf. We do not use your financial data to train third-party AI models unless this is clearly disclosed and permitted under applicable law. Automatic category suggestions are optional and can be turned off in settings. For categorization, we send limited transaction details with account-number, IBAN, card-number and email patterns removed; amounts are reduced to direction and a broad range. If AI-assisted search is enabled, your search text may also be processed by an AI provider. These features return suggestions or help interpret a query; review their results before relying on them.
Purely does not sell sensitive financial data. Trusted infrastructure providers process only the data needed to operate the service.
Signed-in users manage these controls in settings. Destructive actions require authentication, use CSRF protection for cookie requests and are recorded as audit events.
For privacy requests, account help or security concerns, contact support or security.