# Trust centre: what you can verify yourself.

Reconora holds no security certifications and does not display badges. Instead, you can verify the parts that matter: read the anonymiser's full source code before it runs, check SHA-256 fingerprints on every package, review our planted-marker test results including the weak spot, and see every sub-processor and how each published number is produced.

**We don't show badges. We show what you can verify.**

## What you can verify yourself

The Reconora trust model rests on checks your own team can run, not on statements you have to accept.

- **The anonymiser's source code.** The module that anonymises your data runs inside your perimeter. It is delivered with its full source code, on request, so your security team can read every line before it touches your data. It runs offline and uses only the Python standard library. [How the anonymiser works](https://reconora.com/security/anonymiser)
- **Fingerprints on every package.** Every package and every source file carries a SHA-256 fingerprint. Each package comes with a verification report. Evidence in a claim can be traced to the exact file and row.
- **Record balance.** Every record is accounted for: parsed, skipped by rule, or quarantined with a reason. On one anonymised merchant day: 1.5 million records = 1,187,215 parsed + 329,997 skipped + 9,635 quarantined.
- **A tamper-evident audit trail.** Each entry carries the fingerprint of the previous one, so a change after the fact breaks the chain. Five roles with separated rights. [Audit trail](https://reconora.com/product/audit-trail)

## Planted-marker test results, including the weak spot

The anonymiser test plants fictional personal values in a copy of a full day and counts how many fail to reach the output. On that test, e-mails were caught at 100%, phone numbers at 100%, card numbers at 100%, IBANs at 100% and IP addresses at 100%, and names at 99.1%. Document numbers with no marker word next to them were caught at 26.4%. Our release threshold is 95%, so that category does not meet it yet. A passport or tax number in free text looks like any numeric ID. Under known field names it is caught completely. We publish the weak spot because your security team would find it anyway. The full table is on the [security page](https://reconora.com/security).

## Sub-processors

The sub-processors below handle data about visitors to this website and people who contact us. They never receive merchant payment data: that is anonymised at your site and reaches Reconora only as anonymised artifacts. The same list appears in the [privacy notice](https://reconora.com/privacy).

| Provider | Purpose | Location |
|---|---|---|
| Vercel Inc. | Hosting, security logs, analytics | USA |
| Resend, Inc. | Delivery of pilot request e-mails | USA |
| Google (Google Workspace) | Our e-mail | EU and USA |

Where a provider processes personal data outside the European Union, the transfer is covered by the EU–US Data Privacy Framework or by the European Commission's Standard Contractual Clauses.

## How every number is produced

Every figure on this site comes from one anonymised merchant day, measured by the reconciliation engine. Each figure is recorded once, in one file, with its internal source. The site refuses to build if a page carries a number that is not in that file. A figure that has not been measured is not shown, rather than shown as zero. One measured day is not an industry benchmark, and we say so next to every figure. The [methodology](https://reconora.com/methodology) page explains the dataset, the denominators and the editorial policy. The structural figures are also published as open data, so anyone can check that the numbers on our pages match the file they come from. Found an error? Write to us and the page will be corrected, with a new date.

## Documents on request

The following documents are available to prospective and current clients. Write to [product@reconora.com](mailto:product@reconora.com).

- **Data processing agreement (DPA).**
- **The anonymiser's full source code**, for review by your security team before installation.
- **The security brief**, also available as a [PDF download](https://reconora.com/downloads/reconora-security-brief.pdf).

## Security contact

To report a vulnerability or a security concern, write to [product@reconora.com](mailto:product@reconora.com). Our machine-readable security contact file is published at `/.well-known/security.txt`. The [security page](https://reconora.com/security) describes how data moves and what never leaves your company, and [what runs where](https://reconora.com/security/architecture) shows it as one diagram. Your security team can follow our [review checklist](https://reconora.com/security/review).

## What we do not claim

The list of what Reconora does not claim is as important as the list of what you can check.

- **No certifications.** We hold no third-party security certification and no audit attestation report. We describe how the system is built and tested, and give you the code to check it.
- **No public source repository.** The anonymiser source code is given to clients on request, not published openly.
- **No status page.** We do not run a public uptime page today.
- **No moving of money.** Reconora is an information layer. It never holds, routes or moves funds.
- **No personal data.** Reconora does not receive your customers' personal data, so there is none for us to protect, lose or decode.
- **Known gaps stay published.** The document-number weak spot above stays on this page until it is fixed.

[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/trust · Updated 2026-10-18
