LedgerDrop

Privacy

Last updated: 10 September 2026

Your PDF never leaves your browser

This is not a promise about how we handle your file after receiving it. We never receive it.

LedgerDrop is a static website: HTML, CSS and JavaScript files served from a CDN, with no application server and no database behind them. When you drop a statement on the converter page, the file is read by JavaScript running in your own browser tab, using the browser's File API. The text is pulled out with pdf.js, which also runs in your tab. The CSV you download is assembled in memory and handed to your browser as a local blob: download. At no point is there any code on the page that sends the file, its text, or anything derived from it anywhere.

How to check this yourself

  1. Open the converter.
  2. Open your browser's developer tools and go to the Network tab.
  3. Convert a statement.
  4. No request appears carrying your file, its text, or anything worked out from it. The only requests are the page itself and the two Google Analytics events listed below.

You can also disconnect from the internet after the page has loaded and convert a file. It works, because there is nothing it needs the network for.

What the page loads

Everything the converter itself needs is served from this site, including the PDF-reading library — so reading your statement involves no other party at all. The one thing loaded from elsewhere is Google Analytics, which counts the two events described below and never sees your file. There are no fonts from another domain, no other trackers, and no advertising.

WhatFromWhy
Page, styles, converter codethis siteTo show the page
pdf.js library and its workerthis site (/assets/vendor/)To read the text layer of the PDF
Google Analyticsgoogletagmanager.com, google-analytics.comThe two counters described below, and nothing else.

What is recorded

LedgerDrop counts two things, so that we know whether the converter actually works on real banks. Both are anonymous and neither contains anything out of your statement.

EventThe complete contents
convert_resultstatus — one of ok, mismatch, unknown, no_table, scanned, too_many_pages, not_pdf, error
pages — how many pages the file had
rows — how many transactions came out
feedbackvoteup or down, only if you press one of the two buttons

That is the entire list. Specifically, none of the following is read for analytics, sent, or stored: the file name, the bank, account numbers, account holder names, dates, amounts, descriptions, balances, or any other text from the document.

A script this site does not use

Cloudflare, which serves this site, adds its own analytics beacon (static.cloudflareinsights.com) to pages it hosts. This site's Content Security Policy does not allow it, so your browser refuses to load it and it collects nothing. If you look at the developer console you will see it being blocked — that is the policy doing its job, and it is the same policy that stops this page sending your statement anywhere.

The code that sends these is one short file — /assets/analytics.js — and it accepts nothing but the fields above. You can read it in a minute.

Google Analytics

Google Analytics 4 is loaded on this site and receives the two events above along with the standard information any web request carries: your IP address (which we ask Google to truncate), your browser and operating system, the page address, and the referring page. Google's handling of that is covered by Google's privacy policy. If you would rather not be counted at all, any content blocker or the browser's own tracking protection will stop it, and the converter works exactly the same with it blocked.

Cookies and local storage

LedgerDrop itself sets no cookies and stores nothing in your browser — no local storage, no session storage, no saved settings. (Saved per-bank settings are planned for the paid version; when that exists it will keep them in your browser and this page will say so.) Google Analytics sets its own cookies.

Who runs this

LedgerDrop is operated by Tekiba, an independent software project. We do not sell data, because we do not have any to sell. Questions about this page can be sent to [email protected].

Changes

If this page changes in a way that affects what leaves your browser, the date at the top changes and the change is described here. As of the date above, nothing derived from your statement has ever been transmitted, because the code to do so does not exist in this site.