Security & compliance at Cenntrax

Every compliance-relevant action is recorded as an immutable, hash-chained event so records can be proven unaltered.

• Each audit event is hashed with SHA-256 over its contents plus the previous event's hash, forming a continuous chain.
• Any edit, deletion, or re-ordering breaks the chain and is detectable.
• Chain integrity can be re-verified on demand across the full history or a single module.
• Events capture who, what, and when for pickup, delivery, and cold-chain actions.

Temperature-sensitive freight is monitored against per-product thresholds with automatic excursion handling.

• Configurable temperature profiles (e.g. 2–8°C) per customer / product.
• Automatic excursion detection and alerting when readings fall out of range.
• Temperature auto-captured from telematics sensors at pickup and delivery, stamped to the proof record.
• Quality workflows: deviations, CAPA (corrective & preventive action), checklists, and a document vault.

Controlled and narcotic shipments carry an unbroken, evidenced custody record from pickup to delivery.

• Controlled / narcotic loads are flagged and require signature and custody capture at handover.
• Barcode scan verification ties each piece to the correct stop before pickup or delivery.
• Proof of Pickup / Delivery captures signature, photo, recipient, GPS, device, and temperature.
• All custody evidence is written to the tamper-evident audit trail.

Customer data is encrypted in transit — at the transport layer and again at the application layer — and access to it is tightly scoped.

• TLS 1.3 for all application and API traffic.
• Per-session application-layer payload encryption on top of TLS: authenticated API responses are wrapped in AES-256-GCM envelopes keyed to a unique 256-bit key issued at each sign-in, so API data cannot be read with a stolen access token alone.
• Payload session keys are generated with a cryptographically secure RNG, stored encrypted at rest, never logged, and rotated on every sign-in.
• Encrypted responses are integrity-protected (GCM authentication tags) — tampered payloads are rejected, never silently accepted.
• Evidence (signatures, photos) and audit metadata stored with integrity hashing.
• Secrets and credentials are kept out of source control and rotated on exposure.
• Backups managed by our cloud infrastructure provider.