LedgerLumen

Security and trust

Security and data handling for LedgerLumen bookkeeping workspaces

Bookkeeping records deserve clear boundaries, not vague security promises.

LedgerLumen uses signed-in workspaces, role-based access, private receipt file handling, explicit export and deletion controls, provider-handled bank sign-in, and conservative tax-readiness wording. It does not claim certifications that have not been verified.

LedgerLumen settings data screen showing category rules, backups, exports, and support controls

At a glance

Small business financial records deserve plain boundaries. Before you store receipts, invoices, bank activity, or tax-readiness notes, LedgerLumen explains what it is designed to handle and what it does not promise.

Authentication and roles

Workspace access is designed around signed-in users and roles such as owner, admin, bookkeeper, tax preparer, and staff.

Where records live

Financial records, bank metadata, receipt files, invoices, customers, collaborators, and sessions come from the authenticated cloud workspace, not durable browser storage.

Bank sign-in boundaries

Supported providers such as Plaid or Stripe Financial Connections handle bank sign-in when configured. LedgerLumen does not store bank passwords.

Receipt and record storage

Bookkeeping records, receipt metadata, invoices, customers, projects, tax payment records, and proof files are treated as sensitive workspace data.

Data controls

Exports, deletion controls, and private receipt files help owners manage sensitive records intentionally. Destructive workspace actions stay explicit and reversible where practical.

What not to send by email

Do not send bank passwords, full account numbers, API keys, private documents, or provider credentials through ordinary support email.

Tax-readiness limits

Tax estimates and readiness features are informational planning aids, not tax, legal, or accounting advice.

Buyer questions

Practical answers before you switch workflows.

Does LedgerLumen store bank credentials?

No. LedgerLumen does not store bank passwords. Supported connection providers handle the bank sign-in flow when configured.

Does LedgerLumen claim SOC 2 or bank status?

No. LedgerLumen does not claim SOC 2, HIPAA, PCI, bank, regulated accounting firm, or insurance status without verified proof.

Can I send private documents by email?

No. Private records belong in secure product paths when available, not ordinary support email.

Are tax-readiness views tax advice?

No. Tax-readiness features are informational planning aids for owner and advisor review.

Trust and fit

Built for the owner who still has to answer the money questions.

  • Workspace access is signed in and role-aware
  • Sensitive records use authenticated cloud workspace paths
  • Bank passwords are handled by connection providers, not stored by LedgerLumen
  • No SOC 2, HIPAA, PCI, bank, or regulated accounting firm claims without verified proof

Related pages