Privacy Policy
Last updated: 27 June 2026
In one sentence: PayBatch keeps everything on your own computer, encrypted, and does not collect, transmit or share any of your data.
What we collect
Nothing. PayBatch has no accounts, no sign-up, no analytics, no telemetry and no tracking. We never see your payees, payment amounts, bank details or files.
Where your data lives
Your saved payees, batches and settings are stored only on your computer, in your operating system's user-data folder, and are encrypted using your operating system's secure keychain (Keychain on macOS, DPAPI on Windows). Other apps and users can't read them, and they are never uploaded anywhere. Payment files you export are written only to the location you choose.
Network use
PayBatch runs fully offline. The only network request it can make is an optional check to GitHub to see whether a newer version of the app is available. That request sends no personal or payment data — it simply reads the latest public release number. You can ignore the update banner at any time.
Error logs
If something goes wrong, PayBatch writes a short error note (with a reference code) to a local log file on your computer so you can troubleshoot or share it if you ask for help. This log stays on your machine and is never sent automatically. You can view or clear it anytime from Help → Report a problem.
Third parties
There are none. PayBatch contains no advertising, no third-party analytics and no third-party SDKs that phone home.
Open source
PayBatch is free and open source. You (or your IT team) can review exactly what it does, line by line, on GitHub.
Contact
Questions? Open an issue on GitHub. PayBatch is created by Victor Saly and is an independent tool, not affiliated with any bank.