Privacy

The short version

• Everything but a PDF is never uploaded. A CSV, spreadsheet, OFX, QFX, QBO, IIF, QIF or MT940 is read from your disk into your browser's memory, converted there, and offered back as a download. It does not cross the network at all.
• A PDF is the exception. It is sent to our server, held in memory while it is read, and gone when the request ends — we never write it to disk and keep no copy. Reading it uses OpenAI's API, and they keep a copy for up to 30 days for abuse monitoring before deleting it. That is the whole of it, and it is set out below.
• Nothing you convert is kept either, unless you switch on saved history. That is a paid-account setting and it is off unless you turn it on. With it on, the file a conversion produced is stored so you can download it again later, for 30, 90 or 365 days as you choose, and then deleted. It never applies to the statement you uploaded — that is dropped when the request ends whether this is on or off.
• The converters need no account. Every format, on every tool page, works without signing up, and that will not change. A paid plan for PDF pages does need one — and then the only thing we hold about you is an email address and a password. The password is stored hashed by our authentication provider, which means it is not readable by us or by anyone who obtained the file.
• The site sets no cookies unless you sign in. No advertising cookies and no analytics cookies at any point, ever. An account brings one kind and one only: the cookie that keeps you signed in.
• If you pay, Stripe takes the payment and we never see your card. You leave this site to pay on Stripe's own page. What they hold, and what comes back to us, is set out below.
• No analytics or tracking scripts. No page-view counter, no session recorder, no advertising pixel.

You do not have to take the first of those on trust. Open your browser's developer tools, go to the network tab, and convert a CSV or a spreadsheet. No request carries your statement, because none is made. Convert a PDF and you will see exactly one request, to this site, and nothing following it.

Who we are

StatementSmith is operated by Laantri Marketing LLC, 1309 Coffeen Avenue, STE 1200, Sheridan, WY 82801, United States. For anything on this page, write to contact@statementsmith.com.

What happens to a file you convert

Everything except PDF

When you choose a statement, your browser reads it from disk into memory on this page. The parsing, the balance check and the writing of the converted file all happen in that tab, in JavaScript, on your own machine.

The converted file is handed back to you as a download generated locally. At no point does the statement, or anything derived from it, cross the network.

When you close or reload the tab, everything is discarded. There is no history, no recent-files list and no recovery — which is the trade being made, and it is the right way round for a document holding somebody's bank transactions. A paid account can switch on a history of what it converted, which is off unless you turn it on and is described under Accounts.

This is why the site can say those files never leave your browser rather than promising to delete them later. The two are not the same claim, and only one of them is verifiable by the person making the decision.

PDF

A PDF cannot be handled that way. Reading one needs a parser far too large to send to a phone, and a scanned statement is a picture of a page that has to be read by a model rather than parsed at all. So a PDF is sent to our server.

There, it is held in memory while it is read. It is never written to disk, never placed in a bucket or a database, and never retained after the response has been sent. When the request ends the bytes are gone, and there is no copy anywhere for us to return to you, lose, or be compelled to produce.

The transactions are sent back to your browser as text, and the file you download is written there, exactly as it is for every other format. Nothing about the conversion itself moves to the server — only the reading of the PDF does.

If a PDF is more than we can read, or you would rather it never left the machine at all, most banks will export the same statement as CSV or a spreadsheet from the same screen you downloaded the PDF from. Those never leave your browser.

Who else sees a PDF

One party, and only for PDF. Reading a statement means a model has to work through it, and we do not run one ourselves — that step is performed by OpenAI, through their API, under their commercial terms.

OpenAI state that data sent to their API is not used to train or improve their models unless the customer explicitly opts in, and we have not. They do keep a copy for up to 30 days for abuse monitoring, after which it is deleted. That is the one place a statement of yours exists for longer than the few seconds it takes to read, and it is theirs rather than ours — we keep nothing at any point.

We send them the statement and nothing else: no name, no email address, no account identifier. That holds whether or not you have an account — having one does not attach you to a file on its way to be read. There is nothing travelling with your statement that could say whose it was.

For every other format, no third party is involved at any point, because the file never leaves your machine for one to be involved in.

Accounts

You do not need one. Every converter on this site works without signing up, and the paragraphs above describe the whole of what happens when you use them. An account exists for one reason: a paid plan has an allowance of PDF pages, and an allowance has to belong to somebody.

If you make one, here is everything it holds: your email address, a hashed password, which plan you are on, whether the subscription is active, how many PDF pages you have used this billing month, and how many top-up pages remain. If you switched on saved history, it also holds the conversions you saved, for as long as you chose to keep them. That is the list, not a summary of it.

Signing in takes your email address and a password. Making an account also takes a code, which we send to that address so we know it reaches you, and the account cannot be used until it does. If you forget the password, the same kind of code lets you set a new one. Nothing we email you will sign you in by itself.

No statement you upload is ever stored, with or without an account. A PDF is dropped when the request ends, and what the account counts is how many pages were read, not what was on them. There is one thing an account can be asked to keep, it is the file the conversion produced rather than the one you gave it, and it is described in the next two paragraphs.

A paid plan can switch on a conversion history, and there are two kinds. Both are off until you turn them on. The browser history is written to a database inside your own browser, on the machine you converted on: what you converted, when, whether it reconciled, and the converted file so you can download it again. It never reaches us, it is not part of your account, and it does not follow you to another computer. Clearing it is one button in your settings, and signing out clears it.

Saved history is the other kind, and it is the one thing on this site that puts a file of yours on our servers. Switch it on and the file each conversion produced is stored in a private bucket only your account can read, so the list and the files are there on any machine you sign in on. You choose how long: 30, 90 or 365 days, after which the file and the record are deleted together. There is a ceiling of 500MB per account, and reaching it stops new conversions being saved rather than deleting any of the ones you already have. Turning it off stops new saves, deleting a conversion deletes the file with it, and closing your account takes all of it. The statement you uploaded is not part of any of this and never will be.

Closing an account is a button in your settings and takes the email address with it, along with any saved conversions and the files behind them. Nothing is kept back for a retention period we are waiting out, and nothing in it was ever wanted for anything else. A completed payment is the one exception, for the reason given under Payment.

Payment: what Stripe sees

Payments are taken by Stripe, Inc., a payment processor in the United States. They are the second and last third party this site involves, and only if you buy something.

We never see your card. Paying takes you off this site and onto a page Stripe hosts on their own domain, where you enter your details. The card number does not pass through our server, is not stored by us, and is not something we could produce if asked, because we have never held it.

Stripe receives what a card payment requires: your card details, the name and billing address on the card, your email address, and the technical signals they use to tell a real payment from a fraudulent one, such as the IP address the payment came from. They act as their own controller of that data and handle it under their own privacy policy, which is worth reading if you want the full picture — it is linked from the payment page itself.

What comes back to us is deliberately thin: whether the payment succeeded, an identifier for the customer and the subscription, the brand and last four digits of the card, and the billing email. The last four digits are there so you can tell which card you used, and are the most we hold about it.

Changing or cancelling a plan happens on Stripe's pages too, through the billing settings on your account. We open the door and Stripe handles what is behind it — so a cancellation is something you do rather than something you ask us for, and the card you update is one we never see either.

No statement, no transaction and no converted file ever goes to Stripe. They handle the payment for a plan. They are never told what you did with it.

Payment records last longer than anything else described on this page, and that is worth stating rather than glossing. A completed payment is a financial record, and both Stripe and we are required to keep those for a period set by tax and anti-money-laundering law — years, not the thirty days that applies to a PDF. Closing your account does not erase a payment that has already happened, and no business is permitted to let it.

What we do hold: server logs

The pages themselves are served by a host, and hosts log requests. For each request that log typically records the IP address it came from, the time, the page requested, the browser's user-agent string and the response status.

That is standard infrastructure logging, kept for security and to see whether the site is working. It records that a browser asked for a page. It records nothing about any file you converted, because the file never reached a server to be recorded.

To prevent automated abuse of PDF extraction, we also keep a short-lived request counter. For a signed-in visitor it is keyed from the account; otherwise from the network address and broad browser family. Before anything is stored, that value is turned into a keyed one-way identifier. The database holds only that identifier, the count and its expiry — never the address, account identifier, statement, filename or transactions. The counter stops affecting requests when the hourly window ends, and expired rows are removed as housekeeping.

We do not combine these logs with anything else, do not use them to build a profile of you, and do not share them with advertisers or data brokers.

Cookies and local storage

If you have not signed in, the site sets no cookies of its own, which is every visitor who uses it as a converter. There is no consent banner because there is nothing to consent to: no advertising cookie, no analytics cookie, and nothing to weigh up.

Signing in sets one cookie, and only one kind. It keeps you signed in and it does nothing else: it is set for this domain alone, it does not follow you between sites, and there is nowhere for it to report to. It is also marked so that only our server can read it and no script running on the page can — including, if one ever got there, a script that had no business being there. It persists between visits, which is what stops you signing in again on every page, and signing out clears it.

Either way the site stores nothing in local storage or session storage. Your format choice and column mapping live in the page's memory and go when the tab does. The one thing that can outlast the tab is the conversion history a paid account can switch on, off unless you turn it on — kept in this browser's own database, and on our servers as well if you switched on saved history.

See cookies for the longer version, which is not much longer.

Fonts and third-party requests

The typeface is served from this domain rather than from a font provider. That is a deliberate choice: a font request would tell a third party which page you were reading and from what IP address, which is exactly the sort of quiet leak a site making this promise should not have.

There are no advertising networks, no embedded widgets, no social buttons and no chat popups. No page on this site loads anything from anywhere else — open the network tab on any of them and every request goes to this domain.

Paying, and later changing or cancelling what you pay for, are the two places you reach Stripe — and both are links rather than scripts: you navigate to a page of theirs and come back when you are done. Nothing of Stripe's runs on ours. That is a deliberate choice and not merely how it turned out — an embedded payment form would put their code, and their cookies, on every page carrying it, and the sentence above would stop being true.

If you email us

If you write to contact@statementsmith.com, we hold that email — your address, what you wrote and anything you attached — so we can answer it and keep a record of what was said.

Please do not send a client's bank statement to that address. We do not need it to help, and sending it would put a file on a mail server that the product exists to keep off servers. If a file will not convert, describe the columns or send a version with the figures replaced.

Your rights

Depending on where you live, you may have the right to ask what personal data we hold about you, to have it corrected or deleted, to object to its processing, or to receive a copy.

You can exercise any of these by writing to contact@statementsmith.com. For anyone who has used a converter and nothing else — which is almost everyone — the honest answer is that we hold nothing beyond server logs and nothing that identifies you by name, because there is no account to look you up by. If you have an account we hold what the account section lists, and we can show you it or delete it on request. If you have emailed us, we hold that email and can delete it too.

We do not sell personal information, and we do not share it for cross-context behavioural advertising.

Children

This is a tool for bookkeeping, aimed at businesses and the people who keep their books. It is not directed at children and we do not knowingly collect anything from them.

Changes to this page

An earlier version of this page promised that if the site ever gained an account or a payment step, it would be rewritten before that shipped rather than after. This is that rewrite, and it was written before either arrived rather than in response to them.

Nothing above changed when accounts arrived, or when paying did, and nothing needs to change if a third thing ships — every claim on this page is written to hold whether or not you have an account, because a page that has to be edited on the day something ships is a page that gets edited the week after.

The claims here are not aspirations. They describe how the code works today, and they are only true because it works that way.