Security
Transport operators trust TripDesk with passenger records, revenue figures and staff accounts. This page describes how we protect that data and what we expect from operators.
Accounts and sign-in
- Passwords are stored as salted hashes using ASP.NET Core Identity. We cannot read them.
- Repeated failed sign-in attempts temporarily lock the account.
- Web sessions use secure cookies. The mobile app uses short-lived access tokens (8 hours) with refresh tokens that expire after 7 days and are revoked when you sign out.
- Administrators can deactivate a user and reset a user's password at any time.
Access control
- Every user has a role, and each role can only use the features it needs.
- Data is separated by company. Users see only their own company's records, and branch-level users are limited to their branch where set.
- Key records store who created and last changed them.
Data in transit and at rest
- Traffic between your browser or app and TripDesk is protected with HTTPS. [confirm HTTPS-only and HSTS in production]
- Data is stored in a PostgreSQL database. [confirm encryption at rest, backup frequency and retention, hosting provider]
Ticket officer app
- The sign-in token is kept in the device's secure storage, not in plain files.
- Tickets carry QR codes that are checked against the server when scanned.
- Bluetooth printers are paired by the officer on their own device.
What operators should do
- Give each person their own account. Never share logins.
- Deactivate accounts as soon as someone leaves.
- Use strong, unique passwords and lock officers' phones and tablets.
- Limit administrator and revenue-report access to people who need it.
If something goes wrong
We monitor for suspicious activity. If a personal data breach is likely to put people at risk, we will tell the affected operator without delay and notify the Nigeria Data Protection Commission within 72 hours where the Nigeria Data Protection Act 2023 requires.
Report a vulnerability
If you find a security problem, email security@tripdesk.ng with the steps to reproduce it. Please do not access other people's data, disrupt the service, or share the issue publicly until we have fixed it. We will acknowledge reports promptly and will not pursue good-faith researchers who follow these rules.