Security & data protection
Your data stays yours — and provably so.
CETAIN is multi-tenant: many companies share one platform. That only works if each company's data is fenced off by design, every change is attributable, and the privacy rights of drivers, receivers and staff can be honoured without an engineer.
01 — Isolation
One platform, hard walls between companies.
Tenant filter on every query
Tables that hold a company's data can only be queried through one helper that adds the entity filter. A repository test fails the build if code queries those tables any other way.
One deliberate exception
The receiver identity — one login across several carriers — is the only place built to join across companies. It is an isolated module, linked only through a verified e-mail address.
Public tracking that can't be mined
Tracking needs both the code and the delivery postal code, is rate-limited per IP address, and answers a wrong guess exactly like a missing one — so valid codes can't be enumerated.
02 — Access & accountability
Least privilege, and a record of who did what.
Sign-in protections
Passwords are stored as bcrypt hashes. Every authentication endpoint is rate-limited, with progressive lockout after repeated failures and token-based password reset.
Short-lived staff sessions
Staff sign-ins use signed access tokens that expire after 15 minutes by default and are renewed with refresh tokens. The sign-in method belongs to each user, not the company.
Six roles
Sender user, receiver user, dispatcher, driver, transport administrator and platform administrator — each sees only what the job needs.
Validated input, hardened headers
Request bodies are validated against schemas before they reach the database, and standard security headers are set on API responses.
Audit trail
Status changes, edits after submission, consent changes and data-subject requests are recorded with actor and timestamp.
Private uploads
Proof-of-delivery photos, signatures and compliance documents are only served to signed-in users.
03 — Privacy rights
GDPR and DPDP, as workflows instead of e-mails.
A transport company's privacy contact can handle a request from start to finish in CETAIN, with the deadline that applies to the entity's jurisdiction.
| Workflow | Europe — GDPR | India — DPDP Act 2023 & Rules 2025 |
|---|---|---|
| Request types | Erasure, export, access, correction, restriction, objection | Erasure, export, access, correction, grievance, nomination |
| Due date | One month | 90 days |
| Erasure | Personal fields are anonymised; legal records such as consignment notes are kept, and the anonymisation is logged so it can be reviewed. | |
| Breach register | 72-hour deadline to notify the supervisory authority | Intimation without delay; detailed report to the Data Protection Board within 72 hours |
| Consent | Consent recorded per purpose, with withdrawal recorded the same way. | |
| Portability & offboarding | A full export of an entity's data, for portability or when a customer leaves. | |
Export and erasure requests and the breach register are in the app today; the other request types, consent screens and entity export are being completed — see the platform status. White paper WP-04 explains the design.
This website, too. It sets no cookies, loads no third-party scripts, fonts or trackers, and sends a strict Content-Security-Policy. The only data it collects is what you type into the demo form — see the privacy notice.
Next step
See your own lanes on one record.
Tell us where you ship and how you work today. We'll walk through CETAIN with your documents, your jurisdiction and your roles — and tell you plainly what is ready and what would need configuring.