Privacy

The short version: your bank file is read and converted inside your browser tab. It is not uploaded, not stored and not seen by anyone here. Every statement below can be checked in your own browser.

Where your file is processed

In the browser tab you have open. The conversion engine is a JavaScript package bundled into the page; the site has no server code, only static files served by Cloudflare. When you drop a statement, your browser reads it from disk into the page's memory, and parsing, column mapping and writing the .qbo file all happen there.

What leaves your computer

Nothing from your file. The site makes network requests to load itself; the conversion makes none.

  • Opening a page downloads its HTML, scripts, styles and images from this site's host (Cloudflare). Other pages are fetched only when you click a link to them.
  • Clicking “Try a sample” downloads one of the fictional sample files from this site.
  • Shortly after a page loads, Cloudflare Web Analytics sends one small report to this site's address /cdn-cgi/rum: which page was opened, where you came from and how long it took to load. See the analytics section below. It is sent during page load, not during conversion.
  • Only if you choose “Accept” in the analytics banner: Google Analytics loads its script from www.googletagmanager.com and sends reports to Google. See the analytics section below. If you decline or ignore the banner, the script is never downloaded.
  • A QFX or OFX file larger than 2 MB, or with more than 5,000 transactions, is converted in a background worker so the page stays responsive. The worker's code is downloaded from this site the first time; your file is handed to it inside the browser, not over the network.

None of these requests carries any content of your file: no account number, payee or amount.

What is stored in your browser

Nothing from your file: no copy of it, of the output or of your settings is kept. Closing the tab discards them. Two things related to analytics can be stored:

  • Your answer to the analytics banner, in local storage under the key qboready-analytics-consent, so the banner does not ask again on every page.
  • If you accepted: the Google Analytics cookies _ga and _ga_*, which hold a random visitor ID so repeat visits can be counted. Declining, or choosing Decline later under “Cookie settings” in the footer, deletes them.

Clearing the site data for qboready.com in your browser removes both, along with the cached page files, which contain no data of yours.

Analytics, cookies and error reporting

A cookieless page-view counter for everyone, Google Analytics only if you accept it, and no error reporting. The site uses Cloudflare Web Analytics, which Cloudflare injects into each page as a script loaded from static.cloudflareinsights.com. It is there so the maintainer can see how many people visit and which pages they read.

  • What it reports: the page address, the referring site, your country, device type (desktop, mobile, tablet), browser and operating system, and page-load timings (Core Web Vitals).
  • What it does not receive: anything from a statement. The report is sent while the page loads, before any file exists in the page, and the converter never calls it.
  • Cloudflare states that the service does not use cookies or other client-side storage and does not track individual visitors across sites. The country comes from the network address of the request, which Cloudflare sees as the host of this site anyway.
  • To block it, use any content blocker that stops static.cloudflareinsights.com; the converter works the same without it.

Google Analytics, if you accept it

A banner at the bottom of the page asks whether Google Analytics may be used. It shows where visitors come from (including Google search) and which tools they use, so the maintainer knows what to improve.

  • Before you answer, and after Decline: nothing. The script is not downloaded and no request goes to Google.
  • After Accept: page views with the page address and referring site, plus what Google Analytics collects by default (approximate location from your network address, device, browser, language, screen size, a random visitor ID in the _ga cookies).
  • Three events from the converters, each carrying only which converter (CSV or QFX/OFX) it came from: a file was loaded, a sample file was loaded, and the .qbo was downloaded, with the number of files. No file name, account, payee, amount or error message is ever sent.
  • Google signals and ad personalisation are switched off, and the site runs no ads.
  • To change your answer, use “Cookie settings” in the footer.

There is no error-reporting service: a failed conversion shows a message in the page and is sent nowhere.

Check it yourself

Your browser's developer tools show every request a page makes. To watch the converter:

  1. Open the developer tools (F12, or Cmd+Option+I on a Mac) and choose Network.
  2. Tick “Preserve log” and load the converter page.
  3. Wait until the list stops growing, then drop a statement and download the .qbo.
  4. No request appears for the conversion: nothing while the file is parsed, previewed or downloaded (apart from the sample file, if you clicked one). The only requests after the page itself are the analytics beacon described above, sent to /cdn-cgi/rum during load, and, if you accepted analytics, requests to googletagmanager.com and google-analytics.com carrying the page address and the events listed above.

A shorter test: load the page, turn off Wi-Fi, then convert a file. It still works, because nothing needs the network.

What the maintainer checked

On 4 October 2026 the maintainer converted the fictional samples (the checking CSV on the home page and the QFX file on the QFX page) in a browser with every network request recorded, first on Cloudflare's local development server and then on qboready.com after this release was deployed. In both runs, zero requests were made during parsing, preview and download. On the live site the only requests carrying a body were the Cloudflare Web Analytics reports sent during page load; their content was the page address, referrer and timing figures, nothing from the sample file. An earlier run had found requests for other pages, sent because the site prefetched linked pages as they scrolled into view; they carried no file data, and prefetching was turned off before this release. This is the developer's own check, not an independent audit.

Email you send

The site has no forms and no server of its own, so nothing you type on any page is sent anywhere. The report a problem page and the “want to hear when it ships” note on converters that are not built yet are plain email links: an email you choose to send reaches the maintainer's mailbox and is handled as ordinary correspondence. Please do not attach a statement; the column names and the error message QuickBooks showed are enough.

Accounts

There are no accounts today. If paid features ship, this page will be updated first.

Contact

QBO Ready is run by one person. Questions about this page can be sent through the report-a-problem page or by email to zebinpan08@gmail.com.