Answers, without the fog.
The questions we get most often about TRU: what it is, how it works, how it deploys, and how it stays secure.
TRU
Unit-Identity Resolution for Physical Goods
TRU is a unit-identity enforcement rail for physical goods that cryptographically binds a unique identity to each product, records every interaction as an immutable event, and enforces real-world outcomes across channels.
Every TRU interaction generates an immutable transaction record on a private blockchain. Blockchain is used as an enforcement and audit layer — not a speculative or consumer-facing feature. TRU operates independently of public chains and does not require tokens, wallets, or user participation to function.
No. TRU is designed for tap-based verification without requiring an app. Deployment options vary by use case.
No. TRU is designed to make unit truth enforceable at the moment of interaction. Static identifiers do not enforce outcomes or resist real-world failure modes on their own.
No. RFID and GS1 systems are identification layers, not enforcement layers. TRU complements existing programs by binding a secure unit identity to each product and enforcing outcomes at the moment of interaction — something traditional barcodes and RFID were never designed to do.
Deployment
How TRU rolls out in the real world.
Returns Integrity is typically the fastest path to measurable impact because it addresses a clear operational surface (desk/dock) with immediate enforcement outcomes.
A pilot focuses on one use case, one environment, and clear success metrics. The goal is to prove measurable risk reduction and operational fit before expanding.
Wherever the unit is handled: returns desks, docks, service intake, distribution handoffs, retail intake, resale verification, and selected consumer touchpoints.
Security
High-level posture and controlled disclosure.
Not publicly. This FAQ and the Security page are intentionally high-level. Deeper details (binding, key handling, threat model specifics) are shared during the demo process under NDA.
Common real-world patterns: copying, replay-style behavior, swapping identifiers between units, spoof attempts against verification, and operational bypass.
TRU is designed to minimize data collection. Many deployments can return outcomes without personal data. Event trails and retention can be scoped by deployment.
Integrations
How TRU fits with systems and channel surfaces.
Yes. Integration depth depends on the workflow. Some pilots run lightweight; production/enterprise deployments can integrate deeper where needed.
TRU enables unit verification and outcomes wherever the unit appears. Marketplace and resale flows vary—details are shown in demo based on your surface and threat model.
Pricing
How TRU packaging and ranges work.
TRU pricing is aligned to verified units and the enforcement surfaces you want to activate. We publish ranges on the Pricing page; exact quotes depend on volume and integration depth.
No. TRU is not a tag resale business. Tags are hardware substrate; TRU is the identity rail and enforcement engine.
Still have a question?
Tell us your category and your primary failure mode (returns, counterfeits, diversion). We'll show the right flow.