Hi HN — I’m Victor. I built Whisper Money, a personal finance tracker where your
financial data is end-to-end encrypted client-side before it ever reaches the
server (zero-knowledge style: the server stores ciphertext and shouldn’t see
plaintext transactions/accounts/budgets).
It’s aimed at people who want to track spending/budgets without giving a SaaS
provider access to raw financial data. There are no bank connections and no AI
processing — you can import transactions via CSV/XLS and everything is encrypted
locally before upload/sync.
MetricsWave is a web analytics solution designed to help you understand and improve your online presence. With intuitive dashboards and real-time insights, you can track visitors, monitor trends, and make data-driven decisions—all without relying on third-party services.
After a few months working on MetricsWave, I recently discovered that some blacklisting lists are including my site domain, not the tracking script, but my landing page domain.
> What he replied is that he couldn't block the script alone if he was serving it from the same domain, so I proposed to move it to a subdomain, and he was fine with that. I have been lucky.
Doubly so, since hosting the tracking script on the same domain as your website was a decision that was inevitably going to come back to haunt you at some point.
I am tired of all the applications to manage my expenses and income that are selling my financial data or offering me credit cards or loans. That's why I created this.
- Stack: Laravel 12 + React 19 + Inertia v2 + TypeScript + MySQL/Redis.
- Encryption code lives under src/lib/crypto (happy to point to specific files).
- Import is CSV/XLS; encryption happens before upload.
- Hosting/deploy: Docker + docker-compose, includes a production compose and a Coolify template.
If anyone has experience with audits / threat modeling for E2E apps, I’d appreciate pointers on what to formalize first.
reply