Local-first processing is part of the product boundary.

Source files and reconciliation rows

Supported reconciliation source files are designed to be processed on the user's device. The Windows application processes them locally, and the web application processes supported files in the browser. Uploaded files, spreadsheet rows, transaction details, account data and reconciliation contents are not sent to ReconLoom servers as part of the reconciliation workflow.

Local recovery and trial data

ReconLoom may store run metadata, source-file fingerprints, mappings, rules, review decisions, finalization state, templates and export receipts locally to support recovery. Raw source cells are not persisted by default. The browser may also store local pre-launch trial state, such as the number of completed Pro trial reconciliations.

Trial and entitlement metadata

To verify and manage a browser Pro trial, ReconLoom may receive only minimal metadata such as your verified email, trial status, an anonymous device or trial identifier and an opaque completed-run ID. This does not include filenames, spreadsheet rows, transaction details, account data or reconciliation results. Paid access may require limited licence or subscription metadata, entitlement status, pseudonymous device metadata and necessary request or security metadata. A Merchant of Record will handle checkout, billing and tax information under its own terms when paid checkout launches.

Privacy requests

Privacy questions or requests may be sent to privacy@reconloom.com.

Before commercial launch

The final commercial notice will identify the legal operator and controller, business address, applicable lawful bases, retention periods, supported territories and jurisdiction-specific rights after professional review.