For compliance and legal teams
A Digital Product Passport is a regulated record that must stay accurate and accessible for a decade. TrustRise treats it as one: role-based access, a hash-chained audit trail, and claims that cannot publish without their evidence.
Access control the regulation requires
The ESPR distinguishes between what a consumer sees, what an economic operator sees, and what market surveillance sees. A passport that publishes everything is not compliant, however transparent it looks.
TrustRise enforces the separation at the field level. Operator contacts and conformity certificates are authority-only. Chemical data and absolute footprint values sit at legitimate interest. The consumer sees the product record.
Each field carries its own visibility, not a blanket setting.
One record resolved differently by who is asking.
Access levels follow the JRC draft, field by field.
An authority field cannot be published by mistake.
An audit trail that holds
Every change is written to an append-only log with a hash chain — each entry hashed together with the one before it. A daily job walks the chain and reports any break.
The log records who changed what, when, from which address, and the before and after values. A deleted user leaves their events in place with the actor pseudonymised, so the record survives staff turnover.
One honest limit: this is tamper-evident, not tamper-proof. Anyone with direct database access could alter a row; the chain reveals that it happened rather than preventing it. We would rather state that than let you assume otherwise in front of an auditor.
Claims that cannot embarrass you
Claim gating holds back any sustainability claim whose evidence falls short of verified. Document-backed is not enough, and a field carrying a blocking validation flag is not enough either.
The practical effect is that a marketing hire cannot publish what legal would not sign. The system refuses before anyone outside sees it.
Claims and their evidence move together or not at all.
You see which field is short, and by how much.
Arithmetic that can be waived is evidence of nothing.
A lapsed certificate drops the claims that relied on it.
When an authority asks
The full evidence trail exports — what each supplier submitted, when, with which document attached, and the verification status of every certificate behind it.
Supplier submissions are hashed and timestamped at the point of submission, so what was sent and when is not reconstructed from memory.
Where we are honest with you
Two things worth knowing before procurement asks.
Data is held on EU infrastructure in Germany. Full-disk encryption at rest is not in place; specific fields are encrypted, and evidence files are served only through short-lived signed URLs.
Two-factor authentication is enforced for supplier owners and admins. The brand side does not have it yet. It is on the roadmap.
We publish both because you would find them in a security review anyway, and finding them there is worse than reading them here.
Review it yourself
Ten passports free, no card. Publish one, export the audit trail, and judge the record on what it contains.