Trust & governance
Management intelligence is only worth acting on when access to the data is controlled, the calculations follow rules the business agreed, and every material finding can be traced back to the figures behind it. That is the standard HENIOCHOS is built to.
01
Data access
Authenticated, tenant-scoped access to the client's own data
Access controlled
02
Business rules
Agreed KPI definitions, periods, hierarchy and thresholds
Rules first
03
Validated analysis
Deterministic calculation on an approved dataset
Calculated
04
Evidence
Figures, period and context retained behind each finding
Traceable
05
Management decision
People decide; the analysis supports the decision
Human control
The trust model runs in one direction: access, then rules, then calculation, then evidence — and the decision stays with your management team.
Four pillars
Four things have to hold at once: your data stays yours, the rules come before the answer, the evidence stays visible, and the decision stays human.
Each client environment is kept separate, and access is governed by the authenticated user and their organisation — enforced at database level rather than only in the interface.
Canonical KPIs are defined with your business and calculated deterministically. The language layer explains results; it does not create them.
Material findings carry the figures, period and context they came from, so management can verify a statement instead of accepting it.
HENIOCHOS is analysis and decision support. It surfaces what changed and what deserves attention — your team decides what to do about it.
Security controls
These are technical controls applied in the production platform and checked as part of our internal security baseline — described plainly, without certification claims.
Data access is restricted at database level, scoped to the authenticated user and their organisation.
Raw import infrastructure is restricted at both application and database level, even for clients with full access to their own analytics.
Import storage is private, with no anonymous access policies.
Anonymous privileges were removed from production business and security tables in the latest permission-hardening step.
Administrative operations are not exposed for anonymous execution.
Production database infrastructure is hosted in an EU region (Ireland).
Technical evidence note: at the latest verified baseline, row-level security is enabled across 49/49 current public production tables. Two anonymous verification endpoints remain public by design, so that a code issued on an evidence record can be checked without an account.
Verifiable evidence
When a security or control check is completed, HENIOCHOS issues an evidence record into a security evidence register. Each record carries a unique HEV code, the date and platform revision it refers to, a public-safe summary of what was checked, and a SHA-256 integrity reference.
Security evidence verification is available on request during evaluation. The public verification portal goes live with the production domain.
Security evidence record
Illustrative format only. This is not a verified record and contains no live values. Evidence records are issued from completed control checks and can be matched against the HENIOCHOS security evidence register.
Deletion & offboarding
Offboarding should be as evidenced as onboarding. HENIOCHOS is designed so that removal of production data can be measured and recorded, rather than promised.
01
Client access to the environment can be withdrawn at the point offboarding begins.
02
What is held in production for that client can be inventoried before anything is removed.
03
Production database and storage can be checked for a zero state as part of offboarding, rather than asserted.
04
The HDC certificate architecture supports a verifiable deletion record with an HDC code and SHA-256 integrity reference.
This is a verification framework available as part of an offboarding process — not a self-service purge button. Production purge verification and infrastructure backup-retention status are reported separately, with retention periods stated precisely rather than implying that every backup copy disappears immediately.
Data residency
Data residency is one part of a wider governance picture. Security and privacy controls across the services HENIOCHOS relies on are assessed as part of our governance model, and we do not claim that every external service or subprocessor operates exclusively within the EU. Where residency matters to your organisation, we will walk through the specifics during evaluation.
Analytical governance
The order matters. Authorised data is validated, business rules are applied, KPIs are calculated deterministically — and only then does the AI analyst explain what the numbers show. AI is not the source of your canonical KPIs.
01
Only data the client has provided and permitted.
02
Structure, completeness and consistency checks first.
03
Agreed definitions, periods, hierarchy and thresholds.
04
Canonical KPIs calculated deterministically.
05
Language layer explains results it did not invent.
06
Management interprets, judges and decides.
Facts are calculated before they are explained.
Unsupported causes are not presented as facts.
Evidence remains visible behind material findings.
Unknowns are identified rather than invented.
Plain speaking
Precision is part of the product. The limits we state are as deliberate as the controls we describe.
We describe the controls that are in place and the evidence behind them, and we keep improving them.
Only checks that have actually been performed become evidence records.
The rules and the approved dataset remain the source of truth for every canonical number.
A SHA-256 value is an integrity reference that proves a record has not changed — nothing more.
See how HENIOCHOS applies your rules, isolates your data and keeps the evidence behind every material answer.
