Last updated 15 August 2026
Your bank statement is never uploaded to us. It is read, parsed and written to your spreadsheet entirely inside your own Google account. We have no server in that path and no copy of your document.
That is a strong claim for a tool that handles the most sensitive document most people own, so here is precisely how it works and precisely where the one exception is.
You pick a PDF using Google’s own file picker. The add-on asks Google Drive to make a temporary copy of it converted to a Google Doc, which is what performs the text recognition. That conversion happens inside your account, on your quota. The add-on reads the text from that temporary Doc, turns it into rows, and deletes the temporary Doc. The rows are written into a new sheet in the spreadsheet you already had open.
At no point does the document, its text, or any row leave your Google account.
Your licence key, and nothing else. Google Apps Script has no way to check a cryptographic signature on its own, so when you save a licence key the add-on asks our server whether that key is genuine. The request contains the key. It does not contain your document, your rows, your totals, your spreadsheet, or your Google account details.
The answer is remembered for 30 days so the check is rare. If our server cannot be reached, the add-on keeps working. We would rather be unable to enforce a licence than lock a paying customer out because of our own downtime.
We do not log the keys we are asked about, and there is nothing to look them up in: the check is a signature verification, not a database lookup.
Nothing about your documents. The add-on keeps a small amount of information in your own browser and Google account properties, which you can erase by removing the add-on:
| What | Why |
|---|---|
| Your licence key | So you do not have to paste it every time. |
| A count of statements | To apply the 3-statement free allowance. A number, nothing else. |
| The date of the last licence check | So the check runs rarely. |
If you buy a licence, Stripe processes the payment and holds your billing details under their own privacy policy. We never see your card number. Your email address is used to send your licence key and its renewals. It is not added to a mailing list and is not shared.
| Permission | What it is for |
|---|---|
| drive.file | The narrowest Drive permission there is. It gives access only to files you hand over through the picker, plus files the add-on itself creates. It cannot see the rest of your Drive. |
| spreadsheets.currentonly | Only the spreadsheet you have open. It cannot read your other spreadsheets. |
| script.container.ui | Draws the sidebar. |
These are deliberately narrow. A broader Drive permission would be easier to build against and would mean the add-on could read everything you own, so it is not requested, and our release process refuses to build if a broader one is ever added.
It reads statements and produces rows. It is not accounting software, it is not a financial adviser, and it does not check your figures against anything except the balances printed on your own statement. Errors in a bank statement, or in what it extracts, remain yours to check. The preview exists so you can.
If this policy changes, the date at the top changes with it. If a change ever made the “never uploaded” statement untrue, that would be a different product, and it would be said plainly here and on the front page rather than buried in a revision.