# What runs where.

Anonymisation runs inside your perimeter, offline. Only an anonymised package crosses to Reconora: codes, hashed identifiers, amounts, statuses and timestamps, with a verification report and SHA-256 fingerprints. Reconora reconciles it and returns the result in the same codes. The encoding table never leaves your company, so only you can decode the result.

Architecture: inside your perimeter — logs and statements are exported and anonymised offline; the encoding table and the secret stay with you. Only the anonymised package (codes, hashed identifiers, amounts, statuses, timestamps, a verification report and SHA-256 fingerprints) crosses to Reconora, which reconciles it and returns the result in the same codes. You decode it at your site with your own table.

## Inside your perimeter

Your team exports one day of the orchestrator log and the provider statements, as they are. The [anonymisation module](https://reconora.com/security/anonymiser) runs on an ordinary computer at your site. It works offline, uses only the Python standard library and makes no network calls. You receive its full source code, so your security team can read every line before it touches your data.

On the first run the module creates the [encoding table](https://reconora.com/glossary/encoding-table) and the secret. Both stay at your site. Without them the codes in the package cannot be reversed.

## What crosses the line

Only the anonymised package leaves your company:

- provider and currency codes instead of names;
- identifiers as shape-preserving hashes, so matching still works;
- amounts, statuses and timestamps;
- a verification report and SHA-256 fingerprints of every package and source file.

Names, e-mails, phone numbers, IP addresses, full card numbers, IBANs, document numbers and provider names never leave. Neither do the encoding table and the secret. [What leaves, what never does](https://reconora.com/security)

## At Reconora

Reconora first checks the package: the declared record count must equal parsed plus skipped plus quarantined records — the [record balance](https://reconora.com/glossary/record-balance). A package is used only after your controller accepts it. The engine then reads every provider’s messages in their native format, translates them into one [canonical model](https://reconora.com/canonical-model) and reconciles your log, the notifications and the statements line by line. Every action — intake, runs, approvals, claims, rule changes — goes into a [tamper-evident audit trail](https://reconora.com/glossary/tamper-evident-audit-trail).

## What comes back

The result comes back in the same codes: every payment in one of four outcomes, discrepancies with reasons and the addresses of their source rows, claim candidates with evidence, and blind spots where no statement exists. You decode it at your site with your own table. Reconora never moves money: there is no pay, block or refund button.

## What you do not need

No access to your production systems, no API integration to start, no personal data and no change to your finance team’s processes. [How the pilot works](https://reconora.com/pilot)

[Start a free pilot](https://reconora.com/pilot) · [Book a 20-min call](https://calendar.google.com/calendar/appointments/schedules/AcZssZ2qcg1D27PGeYQ91fuYaSo7oy6D4tQ0onTGhC2mSdAWZpCuMUozMxIan4qYWtSk56H-hZTTZAC7)

---
Source: https://reconora.com/security/architecture · Updated 2026-10-18
