Get the iPhone appApp Store

Security

Your Books. Protected.

Your books are never used to train models. Access stays scoped, bank credentials stay with Plaid, and every Tally action is attributed.

Start FreeSee How It Works
Scoped Access · Visible Actions · Credentials Stay With Plaid

Ask. She finishes.

One request. Finished books.

You

Tally

On it. Coding the feed, reconciling the bank, then your statements.
  • Coded and posted 12 bank rows — every entry balanced
  • Reconciled Operating Checking — difference $0.00
  • July financial statements delivered 📄
01

No Training on Your Books

LedgerHQ does not use customer books to train models.

02

Scoped Access

People, Tally, and connected agents work inside company-scoped permissions.

03

Visible Work

Every entry shows whether a person or Tally made it, so review stays grounded in the books.

Scoped by Design

Access Stays Inside the Right Books

Every person and Tally operate under explicit roles. Company-owner access reaches only that company. On Pro, firm staff reach the companies the firm manages and nothing else. Tally inherits the scope of the context she is working in.

  • Company-Scoped Permissions
  • Visible Tally Attribution
  • Connections You Can Revoke
LedgerHQ agent access controls scoped to the selected company
People, Tally, and connected agents stay inside the books they are allowed to reach.

How It Works

Clear Boundaries From Connection to Close.

The same access rules follow the work from bank activity through the finished books.

01

What Happens When Tally Uses a Model

LedgerHQ does not use customer books to train models.

02

Independent Controls Behind the Infrastructure

SOC 2 guides how LedgerHQ approaches security.

03

Bank Credentials Stay with Plaid

Bank credentials stay with Plaid. LedgerHQ does not receive or store your bank login password. Bank and card activity arrives through Plaid; LedgerHQ holds provider records and transaction evidence.

The Difference

Know What Protects the Work.

The controls stay visible while the bookkeeping keeps moving.

Controls That MatterTodayLedgerHQ
Bank credentialsHeld by the provider; nobody using the software sees them. Held by Plaid; neither the people in your books nor Tally can read them.
AI authorityNot applicable — the AI does not post work. Tally works under the same limits as a person, and every entry says she made it.
AttributionAudit log of user activity. Every record shows whether a person or Tally created it.

Questions, Answered

Straight Answers About Security.

Does LedgerHQ use my books to train AI models?

No. LedgerHQ does not use customer books to train models.

How Does Tally Protect My Data?

Included managed Tally turns use OpenRouter routing that denies provider data collection and requests zero data retention. Some included research tasks use an Anthropic path and can receive the bank descriptors needed for that task.

What happens if I connect my own provider key?

Customer-connected provider keys follow that provider's terms.

What does SOC 2 cover here?

SOC 2 guides how LedgerHQ approaches security. Railway hosts the application and database, and Plaid handles bank connections. Both have completed SOC 2 Type II audits covering their own services. LedgerHQ has not yet completed its own SOC 2 audit.

Only $20 per month

Protect the Books Without Slowing the Work.

Start Free. Tally's AI use is included.

Start Free