Skip to main content
myClerkBook is a private income and expense platform. You record what came in, what went out and what is coming; it keeps the arithmetic, the history and the audit trail. It is built for people who run their own work: freelancers, founders and small businesses, and for anyone who would rather not hand a third party the keys to their bank account in exchange for a spending chart.

No bank access. Ever.

This is the product’s first principle and it is an architectural constraint, not a setting. myClerkBook does not request, store or process bank credentials, and it integrates with no data aggregator: not Plaid, not Finicity, not MX. There is no door to leave open, no connection to revoke, and no third party holding a copy of your transaction history. The line is drawn at the credential, not at the data. A statement file you export from your own bank and choose to upload is yours to give, and reading it needs no credential and no connection to any institution. Any feature that would require reaching into an account to obtain something is out of scope permanently, whatever the commercial argument for it.
The test any feature has to pass: does myClerkBook need to reach into an account to get this? If yes, myClerkBook does not do it, regardless of how useful it would be.

Privacy sits in the architecture

Three independent mechanisms operate at once, so privacy never rests on a policy promise alone.

At the edge

Requests are authenticated before they reach any code that touches your data. An unauthenticated request is rejected at the boundary.

In the account

Closing your account removes you from every service that holds your details, not only from myClerkBook. Each removal is recorded and retried until the service confirms it.

In the database

Every table enforces ownership in PostgreSQL itself. No application code and no automation can reach another person’s data, because the database refuses rather than the code remembering to.

AI helps you type. It does not decide.

Where myClerkBook reads a document, it extracts the figures and pre-fills the form. You review and confirm before anything is saved. Parsing is there to save you keystrokes, not to act on your behalf.

Deleting means deleted

Account deletion removes your account and everything in it immediately. There is no soft delete, no archive, no retention of a copy for later, and your transactions are never used to train a model. Analytics records are held by separate providers and are erased on request. Ask for an export first if you want to keep anything.

What it is not

Worth stating plainly rather than discovering later.
  • It is not accounting, tax, financial or legal advice.
  • It is not a payment service provider. It cannot hold or move money.
  • It is not double-entry accounting software, and it does not produce statutory financial statements.
  • It does not file anything with a revenue authority for you.

Next: creating your account

What sign-up asks for, what it does not, and where you land afterwards.