Piggy MoneySign in

Account connection privacy

Bart Waardenburg develops and manages Piggy Money himself and currently uses it solely for his own account overview. This text describes the data processed for that purpose and the service providers involved.

Own accounts

The connection is intended for the application owner's own account overview. Enable Banking's restricted production activation permits personal use and evaluation. Ongoing business use, including business PayPal, requires a separate agreement with Enable Banking. This configuration does not provide access for other users.

Data processed

Piggy processes account names, identifiers, any IBANs, currencies, balances and booked transaction details, including amounts, dates, descriptions and counterparty information. Consent status, expiry and technical import information are also retained. This connection does not collect bank or PayPal passwords.

Purpose and consent

After your consent, Piggy reads data through Enable Banking for account overviews, payment import and review, and financial planning. Sign-in and consent take place at the provider. The connection cannot initiate payments. Personal and business connections remain separate.

Service providers

Enable Banking connects to the account provider. The app and the background jobs run on Cloudflare Workers, and the database uses Turso. Anthropic processes data when you use AI chat, categorisation or document processing. Resend handles sign-in and receipt emails. Sentry processes errors and technical traces; Fallow Cloud processes technical data about software execution. Automatic account import itself does not use AI categorisation.

Storage and access

Access to financial data requires signing in to Piggy. Application requests and changes are tied to your user account. Consent sessions are encrypted on the server and excluded from browser responses. Transactions and balances are stored in the database; this text does not claim separate application-level encryption of those fields.

You can disconnect a connection in Piggy. Scheduled synchronisation stops after successful revocation. If provider revocation fails, Piggy reports an error and retains the connection for another attempt. Old sessions after renewal may be retained encrypted until revocation succeeds. Disconnecting does not delete previously imported transactions. Expired consent requires renewal.

Retention and deletion

Piggy retains imported financial data until you delete them or delete your Piggy account. No automatic retention period is configured for these data. Disconnecting does not delete them. Account deletion first resolves outstanding bank consent. If an interrupted authorization has an unknown outcome, manual recovery may be needed before the account can be deleted. Confirming provider-side revocation permits reconnecting but does not prove that unknown sessions have ended. Deleting data from Piggy does not mean that backup or supplier copies disappear immediately. The relevant supplier's retention periods apply; this configuration does not guarantee a fixed period for those copies.

Owner and contact

Bart Waardenburg personally manages Piggy Money. Contact for data questions: bart@waardenburg.dev. For now, Piggy is solely for his own use.