Security
About WealthLedger Security
Your data, isolated at the database level. WealthLedger is built on Django, the battle-tested framework trusted by Instagram, Mozilla, and financial institutions worldwide — with security enabled by default: encrypted passwords, protection against CSRF, XSS, and SQL injection, hardened sessions, and mandatory HTTPS. Because we host many independent clients on one instance, we go one step further than most SaaS: every row of your data is protected by PostgreSQL Row-Level Security. The database itself — not just the application — refuses any query that isn’t scoped to your account, so even a hypothetical software bug cannot expose your budgets, transactions, or statements to another tenant. Add continuous automated checks that verify the isolation never drifts, daily encrypted backups, and secret rotation, and you get bank-grade separation on a homelab-hosted service you can actually talk to.
What this means for you as a client
| Your concern | The answer |
|---|---|
| “Can another client see my financial data?” | No. The database engine itself refuses any query for rows that are not yours — this holds even if the application had a bug. |
| “Is my password safe?” | Hashed with modern one-way algorithms; optional SSO means your own identity provider can hold the credentials instead. |
| “What if the site is attacked?” | Django blocks the standard web attacks (CSRF, XSS, SQL injection, clickjacking) by default; a proxy, fail2ban and monitoring sit in front. |
| “What if your server dies?” | Encrypted daily backups; your tenant is restored with the database, and RLS re-isolates it immediately. |
| “Who can access the admin screens?” | A centralised ACL — staff see only what a superuser explicitly grants them; new users start with nothing. |
Honesty over hype
What WealthLedger does not do (yet)
The current system does not include:
- Budgets
- Attachment evidence
- Direct bank integration
- Integration to other systems
- Client desktop support, or structuring of folders and files with evidence for auditors
The development roadmap is published to logged-in users and does not constitute a commitment to timelines.