Κανών
Kanon. Data moves by the rules
Versioned rulesets evaluated per recipient: what may flow, what must be masked, which obligations attach, over which channel it is delivered.
A person replies, not an autoresponder.
Transmissions you can explain
Every evaluation is snapshotted, so a transmission from three years ago is reconstructible against the rule that was live at the time, in front of a regulator.
The situation today
Customer data reaches subsidiaries over feeds built years ago by people who have left, governed by a spreadsheet, and documented nowhere. The question a regulator eventually asks, who received this field, under which rule, on that date, becomes a project.
What Kanon does about it
Kanon evaluates versioned rulesets per recipient and snapshots every evaluation. What may flow, what is masked, which obligations attach and over which channel it is delivered are policy, not integration code, and every historical decision is reconstructible against the rule that was live at the time.
Runs alone as
A policy-enforced distribution layer for customer data inside the group, replacing point-to-point feeds and spreadsheet-governed extracts.
Data moves by the rules, in four parts.
Rules per recipient, not per feed
A ruleset is written against who is receiving and why, so adding a recipient is a policy change rather than an integration project.
Masking as policy
Fields are withheld or masked by the rule, not by whoever built the extract. The recipient sees exactly the shape the policy allows.
Obligations that travel
Retention, purpose limits and downstream restrictions attach to the transmission itself, so the receiving system inherits them.
Versioned and snapshotted
Rulesets are versioned and every evaluation is captured. Reconstructing a historical decision is a lookup, not an investigation.
Reference set shown: UK. EU and EEA equivalents on request.
What changes once it is running.
Point-to-point feeds retired
Recipients are added by policy change rather than by another bilateral integration.
Masking by rule, not by builder
The recipient sees exactly the shape policy allows, decided centrally and applied consistently.
Obligations that travel
Retention, purpose limits and downstream restrictions attach to the transmission itself.
Answers instead of investigations
Reconstructing a decision from three years ago is a lookup with the rule version attached.
Phase one, one number
Point-to-point feeds retired
Every remaining transmission explainable, with the rule version attached.
Written to the evidence rail
worked example
- RULESET_EVALUATEDv4.2, 2 fields masked, channel api
Stronger with Synesis. Consent in, governed transmission out.
Four weeks. One number for Kanon.
We map Kanon against two entities in your group and quantify phase one, point-to-point feeds retired, with no integration required to produce the number.
A person replies, not an autoresponder.
Proven in production at a systemic European bank: transmission to regulated subsidiaries with full consent management and audit trail.
- Enquiries
- info@trustnexus.eu
- Partnerships
- Become a provider