Security

Every company is walled off from every other

Savanna Fleet is shared by many transport companies, so the most important control is the one that keeps them apart. Every record in the database carries the company it belongs to, and every request is scoped to the company of the person signed in. This is enforced in one place, on the server, for every read and every write; it is not something a page or a client can opt out of. A user cannot reach another company’s data even by guessing an identifier.

Who can see and do what

• Role-based access.Each user is given a role by their company’s administrators, and each role is a set of specific permissions such as view trips or edit purchase orders. Permissions are checked on the server for every request, per record, not just per page.
• Administrators stay in control. Roles can be tailored per company, but a company can never lock itself out: the administrative floor cannot be removed, and a user cannot alter their own role.
• Approval before activation. A newly registered company must verify its email address with a one-time code and is then reviewed by us before it is activated.

Accounts and sign-in

• Passwords must be at least 8 characters with upper- and lower-case letters, a number and a symbol, following current OWASP and NIST guidance. They are stored only as salted hashes, never as text, and we cannot read them.
• Brute force is throttled. Sign-in attempts, registration, password resets and verification codes are all rate limited, and a verification code locks after repeated wrong guesses.
• Sessions are held in a secure, HTTP-only cookie, expire after 7 days, and can be reviewed and revoked from the security settings page, where each active session is listed with its device and address.
• Invitations, not shared logins. Staff are invited by an administrator and set their own password through a single-use link. Removing a user takes effect immediately.

Encryption

• In transit. All traffic between your browser or phone and our servers, and between our servers and the database, is encrypted with TLS.
• At rest. The database and file storage are encrypted at rest by the providers that run them.
• Secrets you give us, such as a telematics access code, are additionally encrypted with a key held only by the application. They are write-only through the interface: once saved, they can be replaced but never displayed.
• Uploaded files — proof-of-delivery photos, vehicle and driver documents — live in a private bucket that is not publicly readable. They are served only through short-lived signed links.

Infrastructure

Savanna Fleet runs on established cloud providers rather than on hardware we maintain ourselves, so that patching, physical security and resilience are handled by teams who do nothing else. The application is hosted on Vercel; the database on MongoDB Atlas, as a replica set with automated backups; and files on Cloudflare R2. Each provider holds independent security certifications such as SOC 2 and ISO 27001. The full list of providers and what each one handles is in the privacy policy.

Access to production systems is limited to the people who operate the service and is protected by multi-factor authentication.

The mobile app

The Android app talks to the same API as the web application, with the same session, permission and rate-limit controls. It requests no location permission of any kind: truck positions come from the vehicle’s tracking hardware, never from a driver’s phone. It contains no analytics or advertising SDK. Camera and photo-library access are requested only at the moment a user chooses to attach a file, and only the chosen file is read.

Monitoring and audit

• Audit log. Changes to significant records — rates, roles, subscriptions, documents, money — are written to an audit log that records who did what and when.
• Request logging keeps enough context to diagnose faults and investigate abuse, without recording more personal data than necessary.
• Payment webhooks from our payment gateway are verified by signature and de-duplicated, and we never store card numbers; those stay with the gateway.

How we build

Every change goes through automated tests — unit, integration and end-to-end against a live server — before it is merged, and the branch that is deployed is the one that passed them. User input is validated with a schema at every API boundary. Database queries are built with an object model, never by joining strings. Dependencies are kept current, and we review third-party packages before adopting them.

If something goes wrong

If a security incident affects your data we will tell you, and the relevant authority, as quickly as we reasonably can — with what happened, what was affected, and what we are doing about it. You can ask for a copy or deletion of your data at any time; see Delete your data.

Reporting a vulnerability

If you believe you have found a security weakness in Savanna Fleet, please tell us before telling anyone else. Email support@savannafleet.com with the subject “Security report” and enough detail to reproduce it. We will acknowledge your report within two working days, keep you informed as we fix it, and credit you if you wish. We ask that you act in good faith: do not access or alter data that is not yours, do not disrupt the service, and give us reasonable time to fix the issue before disclosing it. We will not take action against researchers who follow these guidelines.

Contact us

Security questions from customers and prospective customers are welcome at support@savannafleet.com or through the contact form.