LedgerPort

Security and data handling

The safest way to handle a bank statement is not to receive it. LedgerPort is built so that the files you convert never reach us.

What happens to your files

What is sent over the network

WhenWhat is sentTo whom
Opening a pageAn ordinary web request for the page, its script, style sheet and fontThis site, hosted on Cloudflare
Converting a fileNothingNo one
Buying a licenceThe details you type at checkoutStripe, on its own payment page
Unlocking with a licence keyThe licence keyThis site, which checks it with Stripe

How the page is locked down

Third parties

Neither receives the files you convert.

Verify it yourself

  1. Open the converter, then switch off your internet connection. Convert a file: it works, because nothing needs to be sent.
  2. Or open your browser's developer tools on the Network tab, convert a file, and see that no request is made.
  3. The page's source is not obfuscated; the conversion code can be read in the browser.

For firms

Client files are not transmitted to, stored by or accessible to LedgerPort, so there is no client data for us to process on your behalf. The personal data we and our payment provider handle is limited to what a buyer enters to purchase a licence. See the privacy page, and write to support@example.com if your review needs anything further.

Questions and answers

Are converted files or their contents logged anywhere?

No. They never leave the browser, so there is nothing to log. The hosting provider logs ordinary web requests for pages and scripts, as for any website.

What happens to the file after conversion?

It stays where it was on your computer. The converted file is saved to your downloads folder by your browser. Closing the tab clears the page's copy from memory.

Does the converter work behind a firewall or offline?

Yes. After the first visit the page is kept by your browser and works with no connection. Only buying a licence and checking a licence key need the network.

Who can I contact about a security question?

Write to support@example.com. Reports of vulnerabilities are welcome and will be answered.