Client billing data doesn't belong in someone else's cloud
Your billing records are the most confidential data your business holds: who you work for, what they pay you, what you did for them, and how long it took. Most freelancers hand all of it to a SaaS invoicing tool by default, where it sits in a vendor's cloud next to everyone else's. The fix is not paper and it is not a fragile spreadsheet. It is keeping billing records in files you own, on your machine, and sharing them one document at a time.
What does your billing data actually reveal?
Line up the fields in any invoicing tool and read them as an outsider would. There is nothing routine in there:
| Field | What it reveals |
|---|---|
| Client list | Who you work with. Some contracts treat the relationship itself as confidential. |
| Rates | Your pricing floor, visible in every line item, usable against you in every future negotiation. |
| Hours per client | The scope and rhythm of work that is often under NDA. |
| Invoice history | Your complete revenue, dated and itemized, client by client. |
Where does SaaS billing data actually go?
Not just to the vendor. Read any invoicing SaaS's subprocessor list and you will find the payment processor, the email delivery service, the analytics suite, the support desk, and the data warehouse behind them. Every one of those is a company your client never agreed to. When the inevitable breach disclosure lands, the email goes to you, but the apology belongs to your clients.
None of this requires the vendor to be careless. It is simply how SaaS works: your data becomes operational input for their stack. The subprocessor list grows, the terms update, the company gets acquired, and your clients' names ride along for all of it.
How do you keep billing private without going back to paper?
Run billing the way you would run any local-first business record: the application and the data live on your machine, and the only thing that ever leaves is the document you deliberately send. A client asks what they owe, you send that invoice. Nobody gets the standing feed.
- Storage: client names, rates, hours, and invoices sit in local files. Your backup policy is your exposure policy.
- Sharing: outbound is per document. An emailed PDF discloses one invoice, not a database.
- Continuity: contracts end, tools get cancelled, vendors fold. Files you own keep answering questions in ten years.
Ledger is built exactly this way: a local-first dashboard holding income, clients, and invoices in files on your machine, bought once for $19. It follows the same doctrine as everything on the ZediaLabs products page: boring tech, plain files, no standing feed to anyone.
Income, clients, and invoices in one local-first dashboard. Your clients' data stays on your machine, where your contracts assume it is.
Get Ledger →