Your numbers stay yours, wherever Pascal runs.
Pascal handles the most private documents you own: bank statements, account numbers, balances. This page says exactly what leaves your device, what never does, and how each edition keeps the ledger private.
Only anonymised descriptions reach the AI model
To tell a vendor payment from a transfer, the model needs the text of a line, and nothing else. Names, numbers and references are stripped before the description is sent. Balances, account numbers and statement files never leave your computer, and the model never sees the ledger itself.
ledger · statements · account numbers · balances, all saved locally
anonymised descriptions only
category · confidence · reason
- The description of a transaction, anonymised
- Its kind and currency, so amounts can be reasoned about without revealing them
- Statement files, in any format
- Account numbers and balances
- The ledger, your exports, your rules
- A category and a confidence score
- A one-line reason you can read
- Nothing posts until you approve it
You choose where the data lives. Pascal never chooses for you.
The same audit runs in both editions. The difference is where the ledger is stored, and both answers are private.
Sign in from any browser. Your ledger is hosted fully encrypted, in transit and at rest, in one tenant per ledger: it is never pooled with anyone else's data. It is cached in your browser so the canvas never waits on the network, and the AI assistant is included.
Pascal in the cloudmacOS and Windows. The ledger, your statements, account numbers and balances live in a database on your own disk, never on our servers. It works offline. When you ask the model to understand a statement, it sees anonymised transaction text and nothing more.
Pascal on your computerSix things that are true of every Pascal ledger.
Every transaction is two or more postings that sum to zero per currency. A transfer between your own accounts can never turn into income, and a fee can never hide inside a payment.
Every line keeps the bank's own reference. Re-importing a statement, or importing an overlapping one, never duplicates a posting.
A label you set by hand, or an AI proposal you confirmed, stays put. Rules and the model only ever touch what is still untagged.
Proposals carry a confidence score and a one-line reason. They post only when you approve them, or when they clear a threshold you chose.
Each label records who set it (manual, AI-assisted, AI auto, rule or import), when, and why. The history is kept in full and everything is undoable.
Export the ledger to Excel or QuickBooks whenever you like, with the audit trail attached. On desktop, the database is a file on your own disk.
Every label says who set it, and nothing bleeds across.
In Pascal Business each company or client workspace keeps its own ledger, accounts, currencies and review queue. Preparers propose, reviewers approve, and the audit trail records both. The trail survives the export, so the file you hand over carries its own evidence.
Found something? Tell us first.
If you believe you have found a vulnerability in Pascal, email us with what you found and how to reproduce it. We read every report, reply to every one, and fix what needs fixing before we talk about it publicly.