Privacy

Last updated 2 September 2026.

The tool collects nothing

Tieout runs entirely in your browser. The financial exports you load are parsed and computed on your own machine and are never transmitted. There is no upload, no server-side processing, no account, no cookie, and no analytics on the tool page.

This is enforced rather than promised. The page ships a Content-Security-Policy that forbids outbound connections, so you can open your browser's developer tools, disconnect the network, and watch the whole reconciliation run without a single request.

What stays in your browser

None of this leaves your machine unless you deliberately export it.

Buying a licence

Purchases are processed by Paddle, which acts as the merchant of record. Paddle collects the billing and tax information the transaction requires, under its own privacy policy. We receive the order and the email address needed to send you the key.

That email address is used to deliver the key and to answer you if you write. It is not added to a marketing list, sold, or shared. We keep a record of which orders had a key issued, so that a repeated request does not mint a second key for one payment. That record holds the order, the tier, the date and your email address — never the key itself, and never anything about your files.

The licence key itself

A key carries a version, a tier, an opaque licence identifier and an issue date. It deliberately contains no name, no email address, no file allowance, no usage count, and no address to call home to. Verification is a signature check performed by your own browser.

Hosting

The site is hosted on Cloudflare Pages. As the hosting provider, Cloudflare may process ordinary request and security information needed to deliver and protect the page.