Privacy notice
Updated 5 November 2026 · Private, personal use
Personal Finance is a private application operated by David Hoogland for understanding his own finances. It is not open for public registration. Questions or requests about this application can be sent to hello@davidhoogland.com.
Information used
When the owner chooses to connect a bank, the application retrieves authorized account information, balances and transactions through Enable Banking. Records may include account identifiers, account-holder names, amounts, currencies, dates, payment references, and names or descriptions of counterparties. The application also stores the owner’s sign-in identifier, bank connection status, and any account names, categories, budgets, rules or commitments entered by the owner.
Bank credentials and bank authentication codes are entered with the bank or its authorization provider. This application does not ask for or store bank passwords. Connection tokens and imported source payloads are encrypted in the application database; normalized financial information is stored separately for calculations and display.
Purpose and access
Information is used to display the owner’s financial position, organize transactions and understand cash flow and commitments. Access to financial pages is restricted to the configured owner. Bank access is read-only: the application does not initiate payments or move money.
The application does not sell personal information or use advertising trackers. Hosting, authentication and database providers process information needed to run the service: Vercel for hosting, Clerk for sign-in, Neon for PostgreSQL storage, and Enable Banking for bank connectivity. The bank and these providers have their own privacy notices and may maintain operational or security logs. Their processing can involve locations outside the owner’s country.
Retention and control
Imported records and owner-entered information are retained until the owner requests their deletion. There is currently no automatic retention deadline. Bank consent expiry stops further retrieval but does not automatically remove previously imported data. Deletion requests are handled manually; provider backups and operational logs may remain for their respective retention periods.
The owner can choose which accounts to authorize, revoke consent through the bank or provider, and request access, correction of annotations, export or deletion using the contact address above. Original imported bank observations are preserved separately from editable names and categories. Requests concerning another person’s information in a payment reference can also be sent to this address.
Cookies and security
Sign-in and bank connection flows use cookies and temporary state to maintain sessions and validate authorization callbacks. These support authentication and security. No system can guarantee absolute security; access should be limited to trusted devices and accounts.
Current setup
The live application is being configured. Publishing this notice does not mean that any real bank account has been connected. Sandbox and fictional example records are kept separate from live financial records.