Privacy policy

Last updated 2026-10-14

RowBalance is operated by Forclev LLC ("we"). This policy explains what data RowBalance handles.

Your statements stay on your device

When you convert a file, it is read and processed by JavaScript running in your browser. The file, its transactions, balances and account details are not uploaded to us or to anyone else. The converter uses the open-source PDF.js library, served from our own site.

What we do store

• Your account (only if you create one): sign-in is run by Clerk, Inc., our account processor. Clerk stores your email address, your name and profile picture if you sign in with Google, and sign-in records such as dates, browser and IP address, under Clerk's privacy policy. Clerk never receives your bank files: they stay in your browser.
• Plan records: in our own database we keep your Clerk user ID, your Stripe customer ID, plan, subscription status, billing period and the number of pages converted in the current day or period. We do not record file names or contents.
• Payments: purchases are sold through Link, Stripe's merchant of record, which handles payment, tax, receipts and transaction support. When you buy a plan we give Link and Stripe your account email address; they collect your payment details and may collect your name and billing address under Stripe's privacy policy. We never see full card numbers.
• Free-plan page counter: to enforce the free daily allowance, your browser tells our server how many pages a file has (a number, never the file or its contents). We store that count against a salted one-way hash of your IP address for the current UTC day and delete older days. The hash cannot be turned back into your IP address. The same hash, with a count per hour, limits how often the page counter, checkout and billing can be used. Cloudflare Turnstile checks that a request comes from a real browser; it sees your IP address and browser signals under Cloudflare's privacy policy.
• Server logs: our host, Cloudflare, processes IP addresses and request metadata to deliver and protect the site.

Cookies and local storage

If you sign in, Clerk sets essential cookies (such as __session and __client_uat) that keep you signed in. If you choose a paid export and go to checkout, the statements you converted and the export you picked are kept in your browser's IndexedDB storage, on your device only, so the export can finish when you return from payment; they are deleted once it has downloaded, or after an hour. We use no cookies for advertising or analytics, and visitors who do not sign in get no cookies from us. If you turn off usage statistics (below), that choice is saved in your browser's local storage.

Anonymous usage statistics

To learn which pages help people and where the converter gets stuck, we count what happens on the site. We do this without cookies and, unless you opt out, without storing anything in your browser, so there is nothing to accept or decline. If you would rather not be counted, this button turns the statistics off in this browser. It saves one setting (rb-no-stats) in your browser's local storage, and this browser sends no usage statistics while it is on. A completed purchase is still recorded by our server when Stripe confirms it.

Turn off usage statistics in this browser

• What we count: pages viewed; the site or campaign link (utm_ tags) that brought you; how far down a page you scrolled (25, 50, 75, 100%) and which parts of it came into view; clicks on our menus, links and buttons; FAQ questions opened; converter steps (a file was chosen, read or not read, the balance check result, an export format chosen, the free limit reached, the bot check passed or failed); locked features clicked and the plan prompt shown (and why); sign-in steps (started or finished, and whether Google or an email code was used); checkout steps (plan chosen, how long checkout took to open, a completed purchase and its plan, the export finishing after payment); and JavaScript error names with the script file and line number.
• Details attached: the file type (for example PDF or CSV), a page-count range (for example "2-5 pages"), the statement currency and account type (for example "USD checking"), the reason a file could not be read (for example "scanned PDF"), and whether a converted file was one of our samples. Plus your country and device type (desktop, mobile or tablet), worked out from the request.
• Never recorded: file names, file contents, transactions, amounts, balances, account numbers, your IP address, your email address, your account ID or anything you type. Statistics are the same whether or not you are signed in, and cannot be linked to your account.
• Daily visitor code: to count visitors and follow a visit from page to page, our server combines your IP address and browser name with a random value that changes every day, and keeps only a scrambled code made from them. The daily value is deleted the next day, so the code cannot be turned back into your IP address or linked to your visits on other days, not even by us.
• Cloudflare Web Analytics also counts page views and page speed without cookies, under Cloudflare's privacy policy.

These statistics are stored with Cloudflare and kept for about three months. They are used only to improve RowBalance and are never sold or used for advertising.

Sharing

We do not sell personal data. We share data only with the processors above (Clerk, Link and Stripe, Cloudflare) to run the service, or when the law requires it.

Retention and your rights

Account and plan records are kept while you have an account and, for paid plans, for as long as tax and accounting law requires afterwards. You can ask for access to your data, or for your account to be deleted, by emailing support@rowbalance.com. Residents of the EU, UK and California have the rights given by the GDPR, UK GDPR and CCPA.

Changes

We will post changes to this policy on this page and update the date above.