Privacy Policy

Last updated: 22 June 2026

Trackie (trackie.nz) is a free, privacy-focused budgeting service for New Zealand, run by Alan Grainger and built on the open-source Actual Budget. This policy explains what data Trackie handles, why, and the control you have over it. The short version: no ads, no tracking, no data sale - and your email is never stored in a form anyone can read.

What we collect

  • Your email, for login only. Sign in is handled by a specialist identity provider over OpenID Connect. We never receive or store your password. Your email is stored only as an irreversible HMAC-SHA256 token - no column in the budget database holds a recoverable email or name. This is enforced by automated tests, not just promised here.
  • Your budget data. The categories, transactions and notes you enter. This is yours alone; no other user can see it. You can optionally encrypt your budget data with a password, which means not even the server can read it.

What we don't do

No ads. No analytics, tracking or telemetry. We do not sell, rent or mine your financial data - ever. There is no third-party advertising or behavioural tracking anywhere on the service.

Where your data lives

Access is restricted to New Zealand and served only over HTTPS. Each user's budget and any bank connection are isolated to that user. Login is delegated to a self-hosted identity provider, so passwords never reach the budgeting service.

Your control

  • Export any time. You can export your full budget whenever you like. There is no lock-in.
  • Disconnect any time. Any bank connection can be switched off whenever you choose.
  • Delete your account. Removing your account removes your budget file. Dormant accounts (6+ months of inactivity) may be cleaned up periodically as part of storage management.

Transparency

The exact code that runs this service is public on GitHub. The entire difference from upstream Actual Budget is published and intentionally small, so anyone can confirm precisely what handles your data.

Contact

Questions about your privacy, or want to report a security issue? See the security policy on GitHub, or get in touch with Alan Grainger.