Privacy Policy
Effective April 19, 2026
Levee is a personal budgeting tool. This policy describes exactly what we collect, where it lives, and what we do with it. Short and specific — no templated legalese.
What we collect
- Account identity. The email address and password you sign in with. Passwords are hashed by Supabase Auth; Levee never sees the plaintext.
- Financial entries. The income and expense amounts, optional notes, and dates you log.
- Session state.A small amount of browser local storage: whether you chose “keep me logged in,” whether you've seen the current set of in-app notifications, and whether you've skipped the income-setup screen.
We do not collect device identifiers, analytics, telemetry, location, or any third-party advertising data.
Where it's stored
Levee's backend is a self-hosted Supabase instance at supabase.jrquimora.dev. Your data sits inside that instance under your user account, isolated from other users by Row Level Security.
The desktop app talks to the same backend directly — there is no intermediate server.
Who we share it with
Nobody. Your data is not sold, rented, handed to ad networks, or shared with third parties. The only systems it touches are the Supabase backend itself and the browser or desktop app on your device.
Your rights
- Export.Contact us and we'll send you a copy of your data.
- Delete. Contact us to close your account and remove every row associated with it.
Automatic updates (desktop)
The desktop app checks levee.jrquimora.dev/api/updates/win at launch for a newer installer. The update check sends only what the underlying updater library needs (version, OS, architecture) — no account or financial data.
Changes
If this policy changes, the effective date above will change and the new text will be live on the same URL. Material changes will also be called out in-app.
Contact
Questions, export requests, or deletion requests: reach the project maintainer through the repository at github.com/RaidenSora/levee.