Privacy
Privacy policy
Effective August 3, 2026
Your files stay on your device
CSV parsing, transaction previewing, normalized CSV creation, and QBO creation happen locally in your browser. Bank2QBO does not upload, transmit, or store the contents of the files you select. The site does not ask for bank-login or QuickBooks credentials.
What local processing includes
Your browser reads the chosen CSV, holds the working rows in the page while you map them, and creates a download from the converted data. Refreshing or closing the page clears that in-page working state. Bank2QBO does not provide cloud file storage or an import history.
Analytics
With your consent, we use Google Analytics to measure aggregate visits and product events such as loading a CSV, creating a preview, or downloading an output file. We do not send transaction contents, filenames, mapped values, account identifiers, or downloaded CSV or QBO data to analytics.
Local storage and consent
Your analytics preference is stored in your browser so the site can remember it. Clearing browser storage removes that preference and causes the analytics choice to be requested again. Advertising consent is managed separately by Google where a regulatory message is required.
Advertising
The Google AdSense publisher tag is present on Bank2QBO so Google can verify the site and, once advertising is active, deliver advertising and certified privacy messages. For visitors in the EEA, UK, and Switzerland, advertising storage, user-data use, and personalization default to denied until Google receives an appropriate consent signal through its certified consent platform.
Declining Bank2QBO analytics does not itself record an advertising choice. Where required, Google presents a separate message for advertising consent and provides controls to accept, reject, or manage that choice. Google handles information collected by its services under its own policies; read more about Google advertising technologies.
Information you send directly
If you email us, we receive the address and information you include in that message. Do not attach bank statements, CSV or QBO files, account credentials, or other financial records to a support or privacy inquiry.
Security limits
Local processing reduces exposure by keeping transaction files off our servers, but it cannot secure your device, browser, downloaded files, email, or QuickBooks account. Use an up-to-date browser and protect exported and generated files according to your organization’s record-handling practices.
Policy changes
If these practices materially change, this page will be updated with a new effective date. Continued use after an update is governed by the revised policy.
Contact
Questions about this policy can be sent to privacy@mockupmaestro.com. For product guidance that does not require sharing private records, visit the conversion guide library.