Security

Books that protect themselves.

Letting an AI keep your books only works if the ledger cannot be corrupted. Here is exactly how LedgerMCP guarantees that.

Checks · Coffee Company

  • Every entry balancesPass
  • Trial balance tiesPass
  • Accounting equation holdsPass
  • No orphaned linksPass

Re-derived from raw postings.

verify_books

Run it yourself, any time.

01 · The ledger

Rules the database enforces.

Constraints in Postgres, not app code a bug can skip.

Balanced

Debits equal credits to the cent. Otherwise the write is rejected at commit.

Jun 28 · Gusto, payroll run

AccountDebitCredit
Payroll$6,797.00
Business Checking$6,797.00
TotalDebits equal credits$6,797.00Debits equal credits$6,797.00
entries_balanced · pass

Immutable

The app cannot edit or delete an entry; a correction is a new one. Entries leave only when the whole account is deleted.

Journal · Coffee Company

Jun 27
Square
processing fees · Bank Fees
$1,204.00
Jul 02
Reversal
linked to of Jun 27
($1,204.00)

Both stay in the journal.

UPDATE and DELETE revoked
  • Repeats are harmlessIf the same action gets sent twice, a network hiccup or an AI repeating itself, it is only recorded once. Nothing is ever double-counted, so timeouts stop being dangerous.
  • Balances are computed, never storedReports always derive from the postings themselves at the moment you ask, so they cannot drift from the ledger. There is no cached balance to corrupt.
  • No AI deletes an entryTaking back an import reverses what it posted, and both stay in the journal.

02 · Keys

The AI works inside a fence.

A scoped API key, or an OAuth sign-in it cannot escalate.

  • Lists and reports
    Both keys
    Allowed

    Every list and report tool

  • Writes
    Read-only key
    Refused

    Rejected at the server

    Full key
    Allowed

    Categorize, post, reconcile, lock

  • Revoke
    Both keys
    Allowed

    In Settings, instantly dead

Logged

Every change your AI makes is logged: which key, which tool, what entry.

Activity · Coffee Company

  • Claudebulk_categorize81 rows
  • Claudereconcile_accountJun 30
  • Youset_lock_dateJun 30
no_stale_entry_links · pass

Locked

Nothing posts into a locked month. Not you, not your AI.

Locked through June 30
Entry datedJun 14
Lock dateJun 30
ResultNot posted
locked_periods_undisturbed · pass

Whatever a confused AI posts is balanced, logged and reversible.

03 · Infrastructure

Where the data lives and how it moves.

  • Transport & sessionsAll traffic is TLS (1.2+, terminated at the edge with HTTPS forced). Sessions are httpOnly cookies; the browser never holds a database credential; everything goes through the server.
  • Bank dataBank credentials never touch us: Plaid handles the connection, and access tokens are sealed at rest with AES-256-GCM. Skip bank connections entirely and use CSV if you prefer; the paid tier is optional by design.
  • Accounts & keysPasswordless sign-in with 6-digit email codes, optional TOTP two-factor, API keys stored SHA-256 hashed and revocable at any time. You see a key once; we can never read it back.
  • Tenancy & backupsEvery domain row belongs to exactly one book, and one checkpoint in the server decides which books a request may reach. Before every release, a second account calls every route to check it cannot reach the first. Daily database backups.
  • Small attack surfaceOne sign-in cookie of our own, plus Google Analytics on the public pages and nowhere else. No ad tech, no cross-site tracking, and the marketing site works with cookies disabled entirely. Less machinery, less to break.
  • Report an issueSecurity reports jump the queue: email support@ledgermcp.com with “Security” in the subject.
Responsible disclosure policy →

04 · Your data

Your data is yours.

A ledger you can leave is a ledger you can trust.

  • ExportOne ZIP per book, in one click: CSV files of the general ledger, transactions, accounts, reconciliations and the audit log, with the book’s receipts and statements.
  • DeleteDelete your account from Settings. What remains afterward, and for how long, is in the data retention schedule.

We do not sell data, run ads, or train models on your books. The business model is plan subscriptions covering bank connections, the built-in assistant, and emailing invoices and statements on your behalf. Nothing else.

Because the free tier is the product and every book exports in one click, we have to earn your business every month. The Bench story is what the alternative looks like.

The promises are written down: privacy policy, data retention, subprocessors, and the rest of the policy set.

Questions

Common questions.

Is it safe to let an AI write to my books?

Safer than any alternative that accepts silent mistakes: the database rejects unbalanced entries, every correction is a new entry, and every change your AI makes is logged. Any entry it posts can be reversed.

Can LedgerMCP employees edit my postings?

Not through the app: the database refuses the application any change to a posting, so a correction posts as a new, linked reversal entry. Postings are removed only when the whole account is deleted.

Do you see my bank password?

Never. Bank connections run through Plaid: you authenticate directly with your bank, and we receive only the data you authorize.

What if an API key leaks?

Revoke it in Settings: instantly dead, and a new key is free. Read-only keys limit the blast radius to zero writes in the first place.

Is my data used to train AI models?

No. LedgerMCP never trains on your books; your agent’s handling of conversation data is governed by your own Anthropic or OpenAI plan.

Where does my data live, and who processes it?

In the United States, with a deliberately short list of providers. The full list with roles is published at /subprocessors, and retention schedules at /data-retention.

Trust, then verify.

Post a few entries, run verify_books, and read the audit log yourself.

No card. Works with Claude, ChatGPT, Grok, Cursor, and any MCP client.