Treasury file data is not collected or transmitted.

What happens to a selected file

1. The browser exposes the selected local file to the current tab only after you choose it.
2. Lucaden reads it as ArrayBuffer chunks or text in browser memory and may use a browser-only Web Worker for large tables.
3. JavaScript validates, parses, compares, or generates the result on this device.
4. A download button creates a local Blob URL. The browser saves that Blob directly; it is not first uploaded to Lucaden.
5. Nothing persists unless you explicitly save a case to this browser's IndexedDB or download a portable case bundle.

What Lucaden does not receive from treasury tools

Lucaden does not receive or store the selected file, its content, its filename, its size, parsed account numbers, IBANs, BICs, balances, counterparties, references, invoice XML, validation findings, generated payment XML, or reconciliation output. The treasury tools have no upload API, server action, edge parser, or WebSocket.

Site requests and optional analytics

The application shell can make ordinary same-origin requests needed by the wider Lucaden site, such as an account-session check. Treasury routes do not emit analytics page views. Elsewhere, optional Google Analytics loads only after consent and is limited to page titles and paths; treasury inputs, filenames, file sizes, file contents, results, form values, and query strings are excluded. The treasury route CSP also blocks third-party runtime scripts on direct loads.

Your controls

Keep originals, close the tab to release session data, permanently delete saved local cases when no longer needed, protect exported case bundles with a passphrase when appropriate, and avoid pasting live banking credentials. A forgotten export passphrase cannot be recovered. Questions can be sent to privacy@lucaden.com without attaching a bank file.