Privacy

At a glance

Your statements

The converter reads the PDF in your browser, on your computer. The statement, its transactions and the files it writes are never sent to us or to anyone else.

A scanned page is read the same way. The text on it is found by OCR running in your browser, and the page image never leaves it. To do that, the first scan you drop fetches the OCR reader, about 16 MB, from ledgaroo.com. That request asks for the reader and carries nothing about you or your statement, and a statement with no scanned pages never makes it.

Check it yourself

Open your browser's developer tools on the Network tab and convert a statement: no request carries it. The page's own security policy lets it talk to ledgaroo.com and nowhere else, and the only thing the converter ever sends there is a licence key.

The layout report

A layout report, from Pick the columns, is made in your browser and copied to your clipboard, or saved as a file where the browser blocks the clipboard. It goes nowhere unless you email it to us yourself. The contact page says what it holds.

What your browser keeps

So a statement you open again picks up where you left it, your browser keeps these in its storage for this site. They stay in that browser and are never sent anywhere, except where you came from and the currency you picked, which go to Stripe with your checkout.

• The columns you pointed at, and the rows you corrected or removed, for each statement. They are filed against a fingerprint of the file, which identifies it without holding any of it. A corrected row holds the date, description and amount you typed.
• Your payee rules, with Premium: the text each looks for, the payee and category it sets, and the account number it is held to, if it is held to one. Save rules writes them to a file on your computer and Load rules reads one back; neither sends them anywhere.
• A list of the last 50 statements you converted: the file name and its fingerprint, when you converted it, the period, the number of transactions, how many rows passed and failed the checks, and which formats you downloaded. It holds no transactions.
• The CSV layouts you saved: each one's name, its columns, date format, separator and decimal mark, and whether it names its columns. They hold nothing from a statement.
• Your licence key, if you pasted one, and when it was last checked.
• The currency you picked on the pricing page, if you picked one, so the page shows its prices in it again.
• Where you came from, if the link you arrived by said so: the source, medium and campaign it was tagged with (utm_source, utm_medium and utm_campaign), the click reference Google Ads adds to an ad's link (gclid), the page you landed on, and when. A later tagged link replaces it, and an untagged one leaves it as it is. It is sent only when you press Get Premium. It is removed when the thanks page shows your key, or the first time you open this site more than 30 days after you arrived, and it is never sent after those 30 days. A link with no tag keeps nothing.

Clear the list with Clear the list in the converter, or clear this site's data in your browser settings to remove all of it. Do that on a computer that is not yours.

When you buy Premium

Checkout is Link, Stripe's service, which takes the payment for Premium. Your card and billing details go to Stripe and are kept under Stripe's privacy policy. They never reach us.

From the sale, our server keeps:

• your email address;
• Stripe's reference for you and for your subscription;
• the state of the subscription, whether it is billed by the month or the year, and when it renews;
• the licence key made from it, and when it was made.

Stripe also keeps where you came from, if your browser had kept it, with the checkout and the subscription, so we can tell which advertisement or post led to a sale. Our server passes it on and keeps none of it.

If a Google ad led to the sale, we send Google Ads that ad's click reference (gclid), when you paid and what the sale was worth, so Google can count the sale against the ad. Nothing else about you or the sale goes with it, and a sale that no Google ad led to sends Google nothing.

We use them to email your key, to tell your browser whether the key is valid, and to send it again if you lose it. We could not sell you Premium without them.

If we give you a key rather than sell you one, our server keeps only your email address, the key, and when it was made, for the same three uses.

In its dashboard, Stripe also shows us what any seller sees of a sale: your name, country, what you paid, and the card's brand and last four digits. Our server never reads or copies those.

What reaches our server

Only these, each sent when you act on it:

• When you press Get Premium, the plan and the currency you picked, and where you came from, if your browser kept it. Our server hands them to Stripe to open the checkout, and keeps none of them.
• The checkout reference Stripe sends you back with after paying, so the thanks page can show your key.
• Your licence key, when you paste it and about once a day after, so we can say whether it is still valid.
• The email address you type into the lost key form. We look up the key for it and email it there, and keep nothing new.
• Your answers to the waitlist on the API page: your email address, how many statements you convert, what you would want back and what you would build with it. We keep them with the time you joined, and they are emailed to our own inbox, so we can write to you about the API. They are used for nothing else.

Logs and limits

Our server logs its own requests for up to a week to find faults. When a request fails, the log says what failed, and names it by Stripe's reference or the last four characters of a licence key. A tag too long for Stripe to take is left off the checkout, and the log names which tag it was and its length, not what it said.

Every request to our server but Stripe's own is counted from its internet address for a minute, to stop the forms, the checkout and the key checks being abused. When a request fails on our side, the reply quotes the reference Cloudflare gave it, which finds that failure in our log and nothing about you.

Who else handles it

Three companies, and nobody else. We do not sell what we keep, and we do not share it with anyone but them.

Stripe

Takes the payment, works out the tax and sends the receipt. It holds your card and billing details under its own policy.

Cloudflare

Hosts the site, stores what our server keeps and sends our emails. Like any host, it sees the address and browser of each visit to deliver the page. Its policy covers that.

Google

Counts a sale against the Google ad that led to it, from the click reference, time and amount we send it after the sale. It holds those under its own policy.

No tracking

There are no analytics, advertising or tracking scripts on this site, and it sets no cookies. There is no account, so there is no profile of you to build.

When a link to the site is tagged with where it was posted, such as an advertisement or a forum post, your browser keeps the tag, as above, so that a sale can be put down to the place that led to it. The tag is part of the link's address, so Cloudflare sees it as it delivers the page and the files that page asks for, as it sees any address. After that, what your browser kept goes nowhere unless you press Get Premium, and then only to Stripe. Once you have paid, a Google ad's click reference goes back to Google with the time and amount of the sale, as above. Nothing else from the tag goes to Google or to anyone else, and it is never used to follow you anywhere.

How long we keep it

A licence record is kept for as long as the subscription runs and afterwards, so a cancelled key reads as cancelled rather than unknown. It is deleted when you ask.

Waitlist answers are kept until the API opens or you ask us to remove them. Logs are kept for up to a week.

Where you came from is used for 30 days at most, and your browser removes it on your first visit after that. Stripe keeps it for as long as it keeps the sale. Google keeps a click reference we send it, and the sale counted against it, under its own policy.

Seeing, correcting and deleting it

Write to support@ledgaroo.com from the address you paid or joined with, and we will:

• tell you what we hold about you, and send you a copy;
• correct it;
• delete it;
• take you off the waitlist.

Deleting a licence record stops its key working, so cancel first if the subscription is still running. What your browser keeps is yours to clear, and what Stripe keeps is Stripe's to answer for.

If you are in the EU or the UK

The law there asks us to say a few more things.

• We keep your licence record because we cannot provide what you paid for without it. We keep logs and count requests because we have a legitimate interest in finding faults and stopping abuse, and Stripe keeps where a buyer came from because we have a legitimate interest in knowing which advertisements and posts lead to sales. We keep waitlist answers because you sent them to hear about the API, and you can withdraw that at any time.
• Buying Premium needs your email address. Nothing else on the site asks for anything about you.
• What we keep is held on Cloudflare's network and read in Australia, so it leaves the country you are in. Stripe and Cloudflare each publish the terms they move information between countries under.
• As well as the rights above, you can object to what we do with your information or ask us to restrict it, and you can complain to the data protection authority where you live. In the UK that is the Information Commissioner's Office.

Who is responsible

Sebastian Zanotto runs Ledgaroo and decides what it keeps and why.

Run by

Sebastian Zanotto

ABN

39 600 672 942

Based in

Victoria, Australia

Write to

support@ledgaroo.com

When this page changes, the date here changes with it. Last updated 1 November 2026.