MatchDock

Privacy and local processing

Your spreadsheet contents stay in your browser.

MatchDock reads, reconciles, and exports your selected CSV or XLSX files on your device. Spreadsheet contents are not uploaded to MatchDock servers.

Start reconcilingReview limitations

Browser boundary

Spreadsheet processing stays inside

Local

  1. 01

    Select files

  2. 02

    Parse and inspect

  3. 03

    Reconcile

  4. 04

    Generate Excel export

Spreadsheet contents do not cross this boundary to MatchDock servers.

The local boundary

What stays local

The following document-related data stays inside the browser while you work.

  • Selected file bytes and filenames
  • Selected sheet names and column names
  • Mapped fields, key definitions, and comparison rules
  • Cell values, source rows, and result rows
  • Generated workbook bytes

MatchDock does not upload this spreadsheet content to MatchDock servers or create a server-side copy of the reconciliation result.

Public infrastructure

The public website and measurement

MatchDock's public host serves the application you use in your browser. Like any hosted website, the selected production host may process ordinary request information needed to deliver and secure the site, such as the requested path, IP address, user agent, and security logs. Spreadsheet contents are not included in those requests.

MatchDock uses Umami Cloud as its V0.5 analytics provider. The integration is enabled explicitly at build time and remains disabled when that configuration is absent.

When enabled, MatchDock sends only the approved funnel event name and either the public entry page or flow kind. Umami also receives ordinary web measurement context for that request, such as the page path without its query or hash, referrer, browser, device, screen size, language, and approximate country. Umami forms anonymous sessions from request information without MatchDock setting a cookie or persistent identifier.

MatchDock disables Umami's automatic page, click, performance, heatmap, and replay tracking. It does not call identify, set a distinct ID, or save session properties. The typed V0.5 event contract rejects filenames, sheet names, columns, keys, values, rows, counts, file types, formats, and other metadata derived from uploaded documents before an event reaches the provider adapter.

Tested boundary

Privacy by test, not slogan

Automated browser tests exercise the complete local workflow with a unique marker. The tests fail if that marker appears in an outgoing request.

  1. 01

    Upload

    Files are selected locally. Spreadsheet contents stay in the browser.

  2. 02

    Parse

    CSV and XLSX contents are read and validated locally.

  3. 03

    Reconcile

    Matching and rule evaluation run in browser workers.

  4. 04

    Results

    Exceptions and explanations remain in browser memory.

  5. 05

    Export

    The workbook is generated locally in a dedicated export worker.

  6. 06

    Request check

    The unique test marker must never appear in an outgoing request.

Export boundary

Local export, same privacy boundary

The Excel workbook is assembled in a dedicated Web Worker and downloaded through a browser Blob. Source rows, results, rules, and workbook bytes are not sent to MatchDock servers to create the download.

Workbook created locally

Worker → Blob → browser download

V0.5 scope

What V0.5 does not do

  • No accounts
  • No server-saved workflows
  • No server-side spreadsheet processing
  • No session replay

The saved-workflow prompt records only an anonymous intent event. It does not save a workflow or spreadsheet data.

Reconcile inside the browser boundary.

Start with two CSV or XLSX exports, or review the current browser and file limits first.

Start reconcilingReview limitations

Need help configuring a comparison? Read the MatchDock help guide.