Privacy Policy

Overview

This Privacy Policy explains what data Quick Bank Convert collects, how it is processed, and who has access to it. We believe in being transparent about how your data is handled.

1. How Bank Statement Processing Works

When you upload a bank statement to Quick Bank Convert, the following happens:

• Your file is sent from your browser to our server via an encrypted HTTPS connection
• Our server forwards the file to our parsing API (hosted on Google Cloud) for data extraction. If the PDF is password-protected, the PDF password you enter is sent with it so the file can be opened
• The parsing API uses third-party AI model providers to read the statement. Your statement content is sent to the provider that handles your file — currently Google (Gemini) or OpenAI; Anthropic (Claude) may also be used
• A copy of the uploaded file is saved to our cloud storage (Cloudflare R2)
• The parsed transaction data (dates, descriptions, amounts, categories) is returned to your browser

The file is not parsed in your browser: it leaves your device and is processed on our servers. We never ask for your online-banking login or credentials, and we do not connect to your bank.

For anonymous users (not signed in): Your file is processed and stored exactly as described above. We also keep a log entry for the conversion (file name, file size, bank name, number of transactions and a hashed form of your IP address and browser identifier, used to enforce the free limit). The parsed transactions are shown to you on screen and held for up to 24 hours, linked to a cookie in your browser, so that they can be saved to your account if you sign up. If you do not sign up in that time, that held copy expires and is removed.

For authenticated users (signed in): In addition to the above, the parsed transactions and statement details (bank name, account number as printed on the statement, statement period) are saved to your account so you can view and re-export past conversions from your dashboard.

2. Account Data

If you sign in via Google OAuth, we collect and store the following in our database (hosted on Neon PostgreSQL, US West region):

• Your name (from your Google profile)
• Your email address (from your Google profile)
• Your profile picture URL (from your Google profile)
• OAuth tokens for maintaining your session
• Account creation date

If you sign in with a link we email you instead, we store only your email address.

This data is used for authentication, session management, and subscription billing.

3. File Storage

Uploaded bank statement files are stored in Cloudflare R2 cloud storage, for both anonymous and signed-in users. Files are organized by upload date. Authorized administrators may access stored files for support and debugging purposes — for example, to investigate a statement that did not convert correctly.

Stored files are not shown to other users. To have a file deleted, see Data Retention below.

4. Payment Data

If you subscribe to a paid plan, payment processing is handled by Square. Your card number, CVV, and full card details are entered directly into Square's own secure form (hosted by them, embedded on our checkout page) and tokenized in your browser — these details never reach our servers.

• Square (Block, Inc.) — Direct card processor. Square processes the payment, stores the card on file for renewals, and provides us with a tokenized customer and subscription reference. We remain the merchant on record for these subscriptions and are responsible for any applicable tax. See Square's Privacy Notice.

5. Analytics and Tracking

We use the following analytics services:

• Google Analytics — Tracks pages visited, time spent, browser type, device information, approximate location (country/city level), and referral source
• Copper Analytics — Website usage analytics

These analytics services do not have access to the contents of your bank statements.

To understand who uses Quick Bank Convert, we derive a few broad labels from each statement you convert: whether the account looks like a business or a personal one, a broad industry (such as e-commerce or payroll), how many months the statement covers and how old it is, the bank's name, and your country. For this we never keep transaction text, names, amounts or account numbers. We never use these labels for advertising and never sell them. You can opt out below: that stops the labels and deletes the ones we already have. You can also email support@quickbankconvert.com to have them deleted.

6. Cookies

We use the following cookies:

• Session cookies — To keep you logged in (if authenticated)
• Anonymous parse counter — A cookie that tracks how many conversions you've performed without an account (resets every 24 hours). The same limit is also enforced server-side using a hashed form of your IP address and browser identifier
• Preference cookies — Whether you have already answered or closed one of our optional one-tap questions this week, and whether you opted out of statement labels in this browser
• Google Analytics cookies — For website usage statistics

We do not use advertising cookies or sell data to third-party advertisers.

7. Data Sharing

We do not sell or rent your personal data. We share data with the following third parties as necessary to operate the service:

• Our parsing API (hosted on Google Cloud) — Receives your bank statement file for data extraction
• AI model providers — Google (Gemini) and OpenAI, and potentially Anthropic (Claude), receive statement content from the parsing API in order to extract the transactions
• Cloudflare — R2 stores uploaded files for anonymous and signed-in users; Turnstile may run a bot check on repeat anonymous conversions
• Neon (PostgreSQL) — Stores account data, saved conversions and conversion logs
• Google — For OAuth authentication and analytics
• Square (Block, Inc.) — Card processor for direct-billed subscriptions (paid plans only). Holds the saved card and processes renewals.
• Copper Analytics — For website usage analytics
• Legal requirements — If required by law, court order, or government request

8. Data Retention

Account data is retained as long as your account is active. Uploaded bank statement files — from anonymous and signed-in users alike — and saved conversions are not deleted on a schedule: they are kept until you ask us to delete them.

To have an uploaded file, a saved conversion or your whole account deleted, email support@quickbankconvert.com or use our contact page. If you uploaded without an account, tell us the file name and roughly when you uploaded it so we can find it. We will delete your personal data and stored files within 30 days of your request.

9. Your Rights

You have the right to:

• Access the personal data we hold about you
• Request correction of inaccurate data
• Request deletion of your account, associated data, and stored files
• Export your account data
• Opt out of analytics tracking

California residents have additional rights under the CCPA. EU residents have additional rights under the GDPR. Contact us to exercise any of these rights.

10. Security

We implement security measures including HTTPS encryption for all data in transit, secure OAuth authentication, and encrypted database connections. File uploads are transmitted over encrypted connections. Access to stored files is restricted to authorized administrators. We never ask for, receive or store your online-banking login or credentials.

11. Children's Privacy

Quick Bank Convert is not intended for use by children under 13 years of age. We do not knowingly collect personal data from children.

12. Changes to This Policy

We may update this Privacy Policy from time to time. We will notify users of material changes via email or a notice on the website.

13. Contact

For privacy-related questions or to exercise your data rights, contact us at support@quickbankconvert.com.