Authentication and roles
Workspace access is designed around signed-in users and roles such as owner, admin, bookkeeper, tax preparer, and staff.
Security and trust
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.
At a glance
Workspace access is designed around signed-in users and roles such as owner, admin, bookkeeper, tax preparer, and staff.
Financial records, bank metadata, receipt files, invoices, customers, collaborators, and sessions come from the authenticated cloud workspace, not durable browser storage.
Supported providers such as Plaid or Stripe Financial Connections handle bank sign-in when configured. LedgerLumen does not store bank passwords.
Bookkeeping records, receipt metadata, invoices, customers, projects, tax payment records, and proof files are treated as sensitive workspace data.
Exports, deletion controls, and private receipt files help owners manage sensitive records intentionally. Destructive workspace actions stay explicit and reversible where practical.
Do not send bank passwords, full account numbers, API keys, private documents, or provider credentials through ordinary support email.
Tax estimates and readiness features are informational planning aids, not tax, legal, or accounting advice.
Buyer questions
No. LedgerLumen does not store bank passwords. Supported connection providers handle the bank sign-in flow when configured.
No. LedgerLumen does not claim SOC 2, HIPAA, PCI, bank, regulated accounting firm, or insurance status without verified proof.
No. Private records belong in secure product paths when available, not ordinary support email.
No. Tax-readiness features are informational planning aids for owner and advisor review.
Trust and fit
Related pages