Questions

If something here does not answer yours, email hello@firelog.sg.

What stays local, and what can be sent?

Importing and browsing happen locally. You can check rather than believe us: open your browser's developer tools and inspect the Network tab. An import should create no request carrying the PDF, extracted text or transaction history. The app still loads its own same-origin files.

Parsing runs in your browser, and results are written to browser storage for this site. Data can leave through three optional actions: sharing selected parser evidence, contributing an exact description or template correction, or sending the diagnostic shown after an unexpected app failure. Statement and description reports also require a consent checkbox. Each happens only after you press Share or Send; the privacy notice lists the exact payloads and limits.

Which banks work?

Today: DBS / POSB (tested deposit-statement layouts, PayLah and credit cards), UOB (One Account, Stash Account and One Card), and Citibank (Cash Back card). OCBC is not supported yet.

Only the listed formats have been tested. Another product may reuse one of those layouts, but verify its output. Optional parser reports are one way new or changed formats can be investigated.

My statement is password-protected. Will it work?

Not directly — most Singapore banks email statements locked with your NRIC or date of birth, and Firelog cannot read a locked PDF. Open it with the password, save or print an unlocked copy, and import that copy.

Where you can, download the statement from internet banking instead of using the emailed copy. Those are usually unlocked and are the exact files Firelog is built for.

It says my statement could not be read. Now what?

Firelog tells you which of these happened, and each has a different fix:

• Password-protected — save an unlocked copy and import that.
• No selectable text — the PDF is a scan or a photo. Download the bank's digital statement instead.
• Damaged or not a PDF — download it again from the bank.
• Format not recognised — the PDF was read fine, but this layout is not supported yet. This is the one worth sharing.
• Did not match the printed totals — it was recognised, but the arithmetic did not add up, so none of it was trusted. Also worth sharing.

Only the last two are offered for sharing, because only those two teach the parser anything.

What if I clear my browser, or switch device?

Do I need an account?

No. There is nothing to sign up for, no password, and no email required for ordinary use. Firelog does not hold your local transaction database; it holds only material you explicitly submit under the retention terms in the privacy notice.

What does it cost?

Core parsing, the transaction table and uncapped CSV download from Transactions are free. Spending and income, fees and interest, transfers and correctness findings have no paid list-length limit.

The full recurring-payment list is included during beta. Once Pro is available, the free plan will include five recurring-payment examples, full counts and the estimated annual commitment; Pro will unlock the complete active and stopped lists. We will announce the transition before limits take effect. The free plan will continue to need no account.

Pro is not available to purchase yet. Prices will be shown before purchase, and nothing starts charging automatically. See the terms.

Which browser do I need?

A current Chromium browser — Chrome or Edge. Firelog needs browser features for private local storage and safe locking that not every browser provides yet. If yours cannot run it, the app says so rather than misbehaving quietly.

It works on a phone, though the wide transaction and account tables are cramped on a small screen and scroll sideways within their cards. A laptop is the better experience today.

Does it connect to my bank?

The current product does not. It reads PDFs you already downloaded; it does not ask for bank credentials, use a bank API, or hold or move money.

How accurate is it?

For supported layouts with the necessary printed totals or balances, Firelog compares parsed arithmetic with those anchors and flags a mismatch. Some formats expose weaker anchors than others, and a passing check cannot prove every individual row or field is correct; offsetting errors can also escape an arithmetic check.

That is a real check, not a guarantee. Who a transaction was with is read from the wording your bank printed, so unusual descriptions can come out wrong. Before relying on anything here for tax, a loan, or a dispute, check it against your statements and your bank's own records. Firelog is not financial advice.

What happens to a statement I choose to share?

Your browser encrypts the selected statement before sending it over HTTPS to Firelog's Cloudflare Worker. The Worker and temporary R2 storage receive ciphertext and cannot decrypt it. Intake is intended to move the encrypted submission to the working machine and delete the R2 copy. Nothing removes a submission from R2 automatically, so if that path fails it stays there, encrypted, until it is collected. Working copies follow a 90-day retention policy and may be deleted sooner. Full detail and limitations are in the privacy notice.

Can I take back something I shared?

Where Firelog shows a submission reference such as 20260804T040043.621Z-4420b7e90c9a2200, keep it and email it to dpo@firelog.sg to request early deletion. Failed-statement upload references are kept in this browser; other report references may be shown only when the send succeeds, so copy them then.

A reference locates a submission; it is not proof of identity for an access or disclosure request. Without it, and without an email address supplied with a statement, we may be unable to identify which submission is yours. See the privacy notice.

Can I inspect or report a result that looks wrong?

Every imported transaction is listed and filterable. Findings contains known structural flags, and Transactions shows description shapes with no template; neither is a guarantee that every error has been detected. You can right-click a transaction cell to report a suspected parser or template error. Reporting does not itself change the stored value.