One file, one password.
The unlocked copy downloads with -unlocked on the name. The original stays untouched on your machine, and if the file was never locked in the first place you get it straight back and we say so.
Before you upload anything.
Fair questions — a statement is the most personal document most people handle in a month. Short answers first: not stored, not logged, not read, 25 MB, any bank.
What happens to my file?
It is sent over HTTPS to our server, unlocked in that request's memory, and sent straight back. It is not written to disk, not stored, not logged, and not looked at by anyone. When the response finishes, the file is gone from our side.
What happens to the password?
It is used once, to open the file, inside the same request. It is not stored and it does not appear in any log. If you later import statements into Paperflight, you can choose to save a statement password to your account there — that is a separate, deliberate action.
Which passwords work?
Any password the PDF actually opens with — the NRIC + date-of-birth style Singapore banks use, the PAN-based ones Indian banks use, or anything else. The underlying engine is qpdf, which handles every PDF encryption vintage from RC4-40 to AES-256.
Why does the bank lock the file at all?
Because email is not private and a statement is. The lock protects the file in transit to you. Once it is in your hands, on your machine, removing it is your call — the file is yours.
Is there a size limit?
25 MB, which is far more room than a bank statement needs. If yours is bigger, something other than the statement is in that file.
If you are unlocking a statement to read it, the next question is what is in it. That part is the actual product.