01
Where your data lives.
NavRecs is deployed inside your own Microsoft Azure tenant. Your files, your audit trail and your configuration stay in your environment, in your region. We hold no copy. We see your data only when you grant us access, on your terms.
02
Who can sign in.
Microsoft Entra sign-in only, using your own accounts, your own two-factor and your own leaver process. Three roles: viewer, reviewer, releaser. NavRecs never stores a password of its own.
03
The audit trail.
Every file read, every check run, every break, every sign-off and every configuration change is written to an append-only log. Each entry is chained to the one before it, so any edit after the fact breaks the chain and shows. Entries are never edited or silently removed. Retention follows your policy. Tolerance changes are part of the same record: who changed what, when, from what to what.
04
No outbound calls.
The solution opens no connection to the internet. Alerts and forwarding, if you want them, run on your own cloud's monitoring, never from inside the solution. Your data cannot leave, because there is no route out.
05
One copy per client.
Your own tenant, your own instance. No shared database, no shared anything, ever.
06
How the engine is tested.
The reconciliation engine is deterministic: the same files produce the same answer every time, and every figure can be traced to its source. No generative AI touches your numbers. The software itself is covered by more than 2,300 automated tests. Those are checks on the code itself. They run before every release and stop a change shipping if anything a reviewer relies on has changed.
07
Read-only on your systems.
NavRecs never writes to your accounting system, your custodian portals or anything else you run. It reads the files, runs the checks and records the result in its own audit trail.
08
Regulatory alignment.
Each check maps to a control named in the GFSC's pricing controls guidance and in CSSF Circular 24/856, the Luxembourg regulator's rules on NAV errors in force since January 2025. The mapping is available to your compliance team on request.
09
Continuity.
Source-code escrow is written into the contract, so the solution never depends on one person. Anything blocking a NAV release comes first, until the NAV is out.
10
Jurisdiction.
NavRecs is Guernsey-based. Guernsey data-protection law is recognised as adequate by both the EU and the UK.
