Privacy
Freelancer’s Pond — nothing leaves your browser
On Freelancer’s Pond — Time → Invoices → Revenue. Hours feed invoices, invoices feed revenue.
Client names. Day rates. Who paid on time and who did not. That is the shape of your freelance life, and it lives — in most tools — in a database run by a company you have never met. In the Pond it lives in your browser, on your machine, and nowhere else.
The thing you did not know you were sharing
Freelance SaaS knows your book of clients. Some of them mine that data — anonymised, aggregated, they promise — to sell 'benchmark' features back to you. The rate you charge, the way you invoice, the clients you keep: all of it is grist for someone else's product roadmap.
The Pond has no dataset to mine because it has no back end to send data to.
How this shows up in daily use
No email, no password, no forgot-password flow. Nothing to breach because there is nothing to store. Open the file, work, close it. What you typed stays on the device you typed it on.
If you email an invoice PDF, that PDF is now a normal document — same as anything you send from Word.
A note on client confidentiality
Freelancers who work with law firms, agencies, or NDA-heavy clients often find themselves quietly non-compliant the moment they type a client name into a SaaS's textbox. The Pond removes the awkward question. There is no third-party processor to disclose.
What the file does not do
- No cloud, no sync.Everything is local storage. Export a JSON any time; that is the only export.
- No analytics.We do not know how many hours you logged this month. Neither does anyone else.
- No account.Nothing to log into. Nothing to lose.
- No third-party fonts, scripts, or CDNs.The file works with the network cable pulled.
Questions people ask
Is my client data leaving my machine?
No. There is no back end. The file cannot phone home because it has no home to phone.
What about invoices sent by email?
That is you sending a PDF from your email client. Same privacy as any attachment you send. The Pond does not touch it.
What if my laptop is stolen?
Standard disk encryption on your OS is the correct answer here, as it is for every other file. The Pond does not add a separate password because the OS already provides one, done properly.
The safest client database is the one that exists in exactly one place: yours.