Privacy policy

Last updated: October 7, 2026.

We process email, account/session data, Polar billing identifiers, and export counters to provide accounts and paid access. When you start a checkout, your client IP address is forwarded to Polar so Polar can detect and prefill the billing country and calculate applicable taxes. Polar processes checkout and billing information under its own privacy terms.

If you use Google sign-in, Google provides your name, email address, profile image, and Google account identifier. We use this information only to create or access your ACH File Generator account. We do not request access to Google Drive, contacts, or other Google services.

When you use the web app, payment files, routing numbers, account numbers, recipients, amounts, bank profiles, mappings, and generated ACH files are not sent to our servers. Profiles and mappings saved by the user remain in local browser storage. If you sign in or check out in the middle of building a file, the unfinished file is kept in this browser tab's session storage and removed as soon as you return.

We count product usage with PostHog (EU servers): pages viewed, steps such as importing a file or downloading an export, with row counts and file type but never payment contents. Once you sign in, these events are linked to your account ID and email. PostHog stores an identifier in local storage, not a cookie.

If you use the API or the MCP server, the payment rows you submit are transmitted to our servers, processed in memory to validate or build the file, and returned in the response. They are not stored or logged. API keys are kept only as hashes and can be revoked at any time.