How your files and saved records are handled

Public tools and local Reconcile

CSV, TSV, JSON and supported XLSX files are read in browser memory. Running these tools does not upload source files to ReconNimble. Local CSV, XLSX and PDF exports are generated on your device. Closing the page discards in-memory sources; your original files and downloaded exports remain under your control.

Saving account records

Save metadata in local Reconcile sends the job name, SHA-256 file hashes, row counts, column names, matching rules, summary counts and bounded accept/reject decisions identified by hashes. It excludes raw source files and exception rows. You can remove your saved job metadata from Account → Saved local jobs.

Saving a workflow recipe to a Pro or Team account sends its identifier, name, workflow type and key column names. It does not send source files or result rows. Account → Saved workflow recipes lets you reopen or delete these definitions. Team sharing sends selected column rules to the members of that team, not source files or local results.

Optional server workspace

Open the separate server workspace only when you want server processing, profiles, scheduled reports or server exports. This path uploads selected files after an explicit disclosure and consent step. Staged sources and generated exports are protected by authenticated routes and configured retention controls. A browser-local recipe cannot run automatically on files that are no longer open on your device.

Public share links

Publish result sends counts, column names, a title and tool identifier. It excludes result rows. Formula publishing sends typed formula parameters and generated output. Anyone with a link can view its published information. Review names and parameters for confidential information before publishing. Contact support with the URL to request removal.

Offline copies and evidence packs

Prepare offline tools downloads public application pages, scripts, fonts and sample assets. The offline cache does not contain account pages, source files or saved account metadata. Local recipes are stored in IndexedDB. When an online Reconcile workspace is opened, its browser limits are cached for up to seven days for offline use; without a current cached limit, the offline workspace uses free limits.

The offline page's removal button clears its cache, local recipes and cached limits. Browser site-data controls offer the same broader removal option. Downloaded files are separate and must be removed through your device. Evidence PDFs include counts, rules, hashes, self-declared reviewer details and notes; exception fields are included only when you select them. The application does not upload the generated PDF or evidence workbook.

Support chat, issue context and screenshots

The support widget can record the current route, tool identifier, error text/reference and the message you send. It never uploads the spreadsheet you are processing merely because you report an error. Screenshots are uploaded only when you paste or select one, are restricted to supported image types and are kept outside public web storage. If you continue on WhatsApp, the handoff contains the support reference and page context; the screenshot remains in the protected web conversation unless you separately choose to send it through WhatsApp.

Retention and deletion

Account records and saved metadata remain until deleted or handled through a verified request. We rotate encrypted database snapshots; the default backup retention setting is 14 days. A deleted database record can remain in an older snapshot until rotation, and deletion requests must be reapplied after a restore. Security logs and retained server files follow our hosting and cleanup policies. Account → Security and privacy lets you submit an erasure request. ReconNimble support completes erasure requests by hand rather than deleting data instantly.

Optional service providers

Hosting and configured email services handle operational data. Optional analytics uses the selected GA4 or GTM mode after consent. Optional AI receives the typed prompt you submit. Payment information is entered in the payment provider's checkout; ReconNimble stores order and payment identifiers, plan, amount, status and access dates, not card details. Newsletter signup records consent and requires email confirmation. Enabled providers may process data in other countries; current providers are listed in the Privacy Policy.

Your control and questions

Process only information you are authorised to use. Check identifiers, scope, totals and matching rules before acting on outputs. Use Contact for access, correction, deletion or privacy questions; never send a password. Read the Privacy Policy, Cookie Policy and privacy verification steps.