Trust Center

Frequently asked questions

Common questions from security teams about how Cenntrax protects your data.

Do you encrypt data?
All application and API traffic is encrypted in transit with TLS 1.3. Data at rest is stored on managed cloud databases with provider-level encryption, and integrity-sensitive records (audit events, proof of delivery) are additionally protected with SHA-256 hashing.
How do you prove records haven't been tampered with?
Every compliance-relevant action is written as an immutable, hash-chained audit event. Each event's hash includes the previous event's hash, so any change, deletion, or re-ordering breaks the chain and is detectable. Chain integrity can be re-verified on demand.
Is one customer's data ever mixed with another's?
No. Each customer runs in its own isolated tenant with a separate database, so cross-customer access is not possible.
How is cold-chain compliance handled?
Temperature thresholds are configured per product/customer (e.g. 2–8°C). Readings are auto-captured from telematics sensors and checked against the threshold; out-of-range readings trigger excursion alerts and are recorded against the delivery.
Do you use customer data to train AI models?
No. AI features are optional and cost-controlled; customer data is not used to train third-party models. AI output is treated strictly as data — it is schema-validated and can never execute as code or write to the database unchecked.
Can we get your security documentation?
Yes — security teams and prospective customers can request our security overview and related documents under NDA using the Request access link, or at cenntrax.com/contact.