1. Scope and operator
This notice describes a privately operated, non-commercial instance of Actual Budget used to view and organize the operator’s own financial information. The service is not offered to the general public, and public account registration is not provided.
The application operator is the individual who registered the corresponding application with Enable Banking. For privacy inquiries about that application, use the data-protection contact address provided to Enable Banking in its application registration.
2. Information processed
When an account is linked and the relevant permissions are granted, the application may retrieve account identifiers, bank and account names, balances, booked or pending transaction information, transaction dates, amounts, currencies, payment references, and counterparty details, as made available by the financial institution.
Actual Budget may also store manually entered transactions, budget categories, payees, budget assignments, user and configuration data.
3. Purpose and source
The information is used solely for personal budgeting, financial recordkeeping, reconciliation, and analysis. Bank information is obtained from the relevant financial institution through Enable Banking, following authorization by the account holder.
The banking integration is intended to retrieve account information; it is not used by this application to initiate transfers or payments.
4. Storage, hosting, and service providers
The Actual Budget application and its budget files are hosted on infrastructure controlled by the operator. Enable Banking facilitates access to bank account information; the financial institution also handles data under its own notices and terms.
Cloudflare hosts these public information pages and may process technical request data needed to serve them. If Cloudflare Tunnel or Access is enabled for the private application, Cloudflare may also process connection and access metadata as part of that service. Browser, network, and server access logs may contain technical information such as IP addresses and request times.
Optional features separately configured by the operator, such as identity providers, browser extensions, or integrations with AI/MCP clients, may involve additional data processing and should be assessed under those providers’ respective privacy terms.
5. Security
Access to the private application is restricted, and HTTPS is used for browser access where configured. Access credentials and bank-connection secrets must be protected. Actual Budget's bank-connection tokens and keys are stored on its server and are not protected by Actual Budget's optional end-to-end encryption for budget files.
6. Retention and deletion
Budget information is retained for as long as the operator needs it for personal recordkeeping, and may persist in device copies or backups until removed. Bank permissions may be revoked through the bank or the banking provider. Revocation prevents future access under that consent but does not automatically erase transaction records already imported into the budget.
7. No advertising or sale of data
These policy pages do not contain advertising trackers, analytics scripts, contact forms, or browser cookies set by this website's own code. The operator does not sell financial data or use it for advertising. Hosting and security providers may process technical data under their own policies.
8. Changes and inquiries
This notice may be updated if the private setup changes. For questions about the banking integration or this notice, contact the operator using the data-protection email registered for the application in the Enable Banking Control Panel.