Who this policy covers
BankStatementConverter operates the bank-statement conversion service at bankfileconverter.net. This policy explains how we handle information when you browse the website, upload a document, sign in where that option is available, or contact us. For privacy questions or requests, email [email protected].
Information we process
When you upload a PDF, PNG or JPG, we process the document content and file details needed to extract transaction rows. A statement may contain account holder names, account identifiers, transaction descriptions, dates, balances and other financial information. The extracted result can contain the bank name, account holder, masked account digits, statement period, currency, transactions and extraction warnings.
If you sign in with Google, we receive a verified account identifier and may receive your name, email address and profile image. For guest page limits, we derive a keyed hash from the visitor IP address supplied by Cloudflare and store that hash with page-use records; the application does not store the raw IP in the quota ledger. Signed-in usage is tied to your account. We also process basic request information to operate the service and limit abuse. If you email support, we process your message and contact details to respond.
Why and how documents are processed
We use the uploaded file only to provide the conversion you request, return the result for review and protect the service from misuse. The application reads the original file in server memory and sends it to OpenRouter and the selected AI model provider for extraction. We do not store the original uploaded file bytes in our application database. Provider systems may process and retain requests under their own policies; our routing request excludes providers that collect user data, but it is not a promise of zero retention by every service involved.
Saved results and retention
An anonymous conversion is returned to the browser without an application conversion-history record. If account sign-in is available and you are signed in, we save structured results and conversion metadata in your account history so you can return to them. Those records remain until the account or records are deleted in response to a valid request, unless a longer period is required by applicable law. Support correspondence is kept for as long as needed to resolve the enquiry and maintain an appropriate record of the response. Hosting and security logs may have separate operational retention periods.
Service providers and international processing
We use hosting and database providers to run the website, OpenRouter and a selected model provider for document extraction, Google for optional sign-in, and Stripe if online paid checkout is enabled. These providers may process information in countries different from yours. We do not sell uploaded statement content or use it to target advertising. Card details are handled by Stripe rather than entered into our converter.
Cookies and browser storage
When sign-in is available, we load Google's sign-in component on website pages so eligible visitors can be offered One Tap. That component may use Google cookies or browser storage under Google's policies, whether or not you choose to sign in. If you sign in, we use a signed, HttpOnly session cookie that expires after 30 days; it is not a marketing cookie. We use browser session storage to avoid showing One Tap again in the same tab after you sign out. Export files are created in your browser from the reviewed result.
Your choices and requests
You can use the converter without connecting a bank account. Do not upload a document if you do not want it sent to the extraction providers described above. You may ask to access or delete account data, or raise a privacy concern, by emailing [email protected]. We may need to verify that you control the account before fulfilling a request. Rights and exceptions vary by applicable law.
Security and changes
We limit upload types and sizes, use server-side identity verification for account sign-in, and keep raw uploaded files out of the application database. No online service can guarantee absolute security; please avoid sending unnecessary sensitive information in support emails. We may update this policy as the service changes. The date above identifies the current version.