Security
Your data stays with you.
Reconora never receives your customers’ personal data. An anonymisation module runs inside your perimeter, offline, and replaces names, e-mails, card numbers and provider names with codes. We reconcile the anonymised artifacts and return the result in the same codes; only you can decode it.
Think of an external auditor who receives a ledger where every name is a code — and the codebook stays in your safe. What runs where · A review checklist for your CISO
What leaves, what never does, what comes back
| Leaves your company | Never leaves | Comes back |
|---|---|---|
| Provider and currency codes | Names, e-mails, phone numbers, IP addresses | The reconciliation result, in the same codes |
| Amounts and timestamps | Full card numbers, IBANs, document numbers | Discrepancies with reasons and row addresses |
| Payment statuses | Provider names | Claim candidates with evidence |
| Identifiers as shape-preserving hashes | The encoding table and the secret | A verification report |
Audit the code yourself
The anonymisation module is delivered with its full source code. Your security team can read every line before it touches your data. It runs offline and uses only the Python standard library — no network calls, no third-party packages.
What we don’t need
- Access to your production systems.
- An API integration to start.
- Any personal data.
- Changes to your processes.
How every package is verified
- Manifest and record balance. The package declares its record count; we check it: 1.5 million = 1,187,215 parsed + 329,997 skipped + 9,635 quarantined.
- Fingerprints. Every package and every source file carries a SHA-256 fingerprint, so evidence in a claim can be traced to the exact file.
- Residual personal data. After anonymising a full day: 0 residuals under the module’s own rules.
- A human decision. A package is used only after your controller accepts it.
Tested with planted markers — and honest about the weak spot
We plant fictional personal values in a copy of the data and count how many fail to reach the output.
| Kind | Caught |
|---|---|
| 100% | |
| Phone | 100% |
| Card number | 100% |
| IBAN | 100% |
| IP address | 100% |
| Name | 99.1% |
| Document numbers without a marker word | 26.4% |
A passport or tax number with no marker word next to it looks like any numeric ID. Under known field names it is caught completely; in free text it is our known weak spot, and our release threshold of 95% is not met there yet. We would rather tell you than have your security team find it. Read about the anonymiser
Every action is recorded
Package intake, reconciliation runs, approvals, claims and rule changes go into an audit log where each entry carries the fingerprint of the previous one (a SHA-256 chain). Change any entry after the fact and the integrity check shows the break. Five roles with separated rights; a rule change by an operator is only a proposal until a manager approves it. Audit trail
We never move money
Reconora is an information layer. There is no “pay”, “block withdrawal” or “refund” button. A payment instruction, where needed, is exported as a document and executed by you.
What we don’t claim
We do not claim certifications we do not hold. We describe how the system is built and how we test it, and we give you the code to check it.
Questions
- Can Reconora re-identify my customers?
- No. The encoding table and the secret are created at your site and never leave it. Without them the codes cannot be reversed.
- Does the module send anything over the network?
- No. It runs offline and uses only the Python standard library. You can verify this in the source code.
- Do you receive card numbers?
- No full card numbers. Card data is removed or masked before the package is created.
- Can we sign a DPA?
- Yes. Request our DPA at product@reconora.com.
By Reconora Research · Updated