How your platform is hosted and secured.
How data is kept separate.
Between operators
Each operator has a separate server, database, web address and tracker ports. No other operator's devices report to your ports, and no other operator's users can sign in to your portal.
Between your clients
On your server, devices belong to accounts, and users see only what's assigned to them. API keys and webhooks follow the same rules, so a client's integration only gets that client's vehicles.
Roles and restrictions.
Give each account the rights it needs. You can add a restriction to any user, staff or client, and change it later.
| Setting | What it does |
|---|---|
| Administrator | Full control of the server, including settings, branding and all devices and users. |
| Manager | Creates and manages their own users, within the device limit you set. |
| Standard user | Works with the devices assigned to them. |
| Read-only | Can view the data but can't change anything. |
| Device read-only | Uses the platform but can't edit device settings. |
| No commands | Can't send commands to a unit, such as an engine cut. |
| Expiry date | The account stops working on a set date, which suits trials and contractors. |
| Disabled | Blocks sign-in but keeps the account and its history. |
Credentials and records.
Passwords
Passwords are stored as bcrypt hashes. Users reset a forgotten password through a link sent by email.
API keys
Each key is shown once when it's created, then stored as a SHA-256 hash. A copy of the database doesn't give anyone working keys.
Audit log
Each successful change in the portal or through the API is logged with who made it, when, from which IP address and with what result. Secrets are masked.
Tracker data
The server confirms a record to the unit only after saving it, so a database hiccup doesn't lose positions.
Video evidence
Original dashcam files stay unaltered next to the branded copies that people watch and download.
Links
Sharing links expire at the time you set. Driver links for dispatch use long random tokens.
What we look after
We supply free SSL certificates from Let's Encrypt for your addresses and renew them for you. We also handle platform updates, backups of your data and the server's capacity as it fills. Your card details for the plan stay with PayFast and never reach us.
What stays with you
You control your domain's DNS records, the devices and SIM cards, and who gets an account with which rights. The agreements with your clients are yours too. Our privacy policy sets out what we do with personal data.
Questions about security
Who can access the machine my platform runs on?
We keep admin access so we can apply updates, renew certificates and look after backups. Your staff and clients use the platform through the portal, the app and the API.
How are passwords and API keys stored?
Passwords are stored as bcrypt hashes. API keys are stored as SHA-256 hashes and shown in full only once, when they're created. A lost key can't be recovered, so you replace it instead.
Could another operator see my clients' data?
No. Operators don't share servers or databases. Within your server, the users of one client account can't see another client's devices.
Related pages
Try it on a server of your own.
Order online and we'll usually have your server live within a day, with your domain, your logo and the tracker ports all set up.