Sign-in
People sign in with their Tafsee account. Tafsee Logistics itself never receives or stores passwords. Each organisation's data is kept separate, and every request is checked against the organisation it belongs to.
Access by role
Each person has a role made of permissions (see Team & roles). The service checks the permission on every action, so hiding a button is never the only protection. Stock write-offs and overrides, cash settlement, settings and API keys each have their own permission.
A history of changes
Reports › History lists who changed what and when, and the warehouse keeps a scan log of every barcode scanned. Cash handovers keep who received the cash and when, and a difference needs a written note.
Proof of delivery
Each delivery keeps its proof: the photo, signature or delivery code the settings require, who received it, and how far the driver's phone was from the customer's pin. A delivery code locks after five wrong tries.
What customers see
The tracking page shows the order's steps, the driver's first name and, only while the order is on the way, the driver's phone. Thirty days after the delivery ends, the page no longer shows the photo, signature or driver.
Connections
API keys are shown once and only a fingerprint is stored; a key can be revoked at any time. Webhooks are signed with a secret, sent only to https addresses on the internet, and switched off after repeated failures.
Search engines
The Logistics app itself asks search engines not to index it and refuses AI crawlers; only these public pages are meant to be found.
