Why a hash chain
An insurance claim or a carrier dispute turns on what was recorded and when. A chain makes after-the-fact editing detectable rather than arguable.
Trust and security
When a claim comes, you need a record.
Every checkpoint on a shipment is hashed into a SHA-256 chain. If a record is changed after the fact, the chain stops linking — and the verification page says exactly where.
Chain integrity verified · 5 / 5 checkpoints
Illustrated- #0Verified
booked
4f9a1c…e2b7
- #1Verified
pickup
8c30d5…91af
- #2Verified
in transit
b7e412…4d0c
- #3Verified
in transit
1d68fa…77e3
- #4Verified
customs entry
a7f3c1…04bd
The chain proves records were not altered after they were written. It does not prove the underlying carrier event occurred — that distinction matters in a dispute, so we state it on the verification screen too.
An illustrated chain. A real one is verified per shipment and exportable as JSON for an insurance claim or a dispute.
Encryption
Traffic between your browser and the platform is encrypted in transit. Your session is kept where scripts on the page cannot read it, and a shipment or document that is not yours cannot even be confirmed to exist.
What we do not claim
The chain proves records were not altered. It does not prove the physical event happened — the carrier feed is the source for that, and we label it as such. Nor is it a certification by a third party.
KVKK and GDPR
PROCUX Teknoloji A.Ş. is the data controller. Personal data is processed under Turkish KVKK and, for EU counterparties, GDPR; you can ask what we hold about you, and have it corrected or deleted, at [email protected]. Shipment data is never shared with carriers you did not select, and we hold no card details — payment is handled by the provider.