Skip to content

Data and trust

What Odal Node can and cannot see.

Odal Node is built on a proof-bound architecture: the manufacturer's product data is validated, signed and stored on infrastructure the manufacturer controls, and every published field carries the manufacturer's signature. This is how the software works, whoever operates the node.

Guarantees

Three things that do not depend on trusting us.

  • Every field carries your signature

    Each published passport is signed with your key, so a change made after signing fails verification. Anyone can check that without us.

  • We cannot reach your node

    When you run the node, we are not part of the deployment and have no access to anything it stores.

  • Nobody signs for you

    Your signing key is generated and held on your own infrastructure. We cannot sign on your behalf.

Scan telemetry

What a scan count is, and what it is not.

When a passport is resolved, the node can record that it happened, as a count per passport per day, and nothing more. A scan count records nothing about the person who scanned: no IP address, device, location, identity or session. The software has no field to store any of it, so none of it can be kept or leaked. Generating a QR-code image is counted separately, because it measures label printing, not readers.

How it works

How it works, step by step.

  1. Import. Product data arrives at your node as CSV, Excel or an ERP export. This happens on infrastructure you control.
  2. Validate. The node checks the data locally against the product group's rules. Nothing is sent to a third party to be checked.
  3. Sign. Your private signing key, generated and held on your own infrastructure, signs the validated passport. The signature is tied to an identity on a web domain you control.
  4. Publish. The signed passport's public part becomes readable through its QR code and GS1 Digital Link; other parts are shown only to readers with a credential.
  5. Verify. Any consumer, authority or recycler checks the signature against the public identity published on your web domain. Verification does not need Odal to be online, or even to exist.