Fleet video data should be protected with the seriousness it deserves.
FleetView is built around secure platform access, controlled workflows and Australian-hosted data. This page gives operators, public sector customers and partners factual information about how video data is handled — without overstatement.
Six things that matter for
how video data is handled.
Described factually. No certifications
implied unless explicitly confirmed.
Australian-hosted data
Your footage stays in Australia.
FleetView stores video and associated telematics data on infrastructure hosted within Australia — no overseas residency, no complex data transfer arrangements.
Controlled access
You decide who sees what.
Role-based user access lets administrators scope permissions by vehicle, depot or function. Footage viewing, exporting and deletion are individually permissioned.
Evidence workflows
Structured export, not open access.
Every download and clip export is logged against a user account — creating an audit trail for internal governance and external evidence submissions.
Geotab alignment
Consistent with your telematics governance.
For Geotab customers, FleetView is designed to align with existing user management and access control structures where applicable.
Privacy-aware deployment
Guidance built in, not bolted on.
transiCAM works with customers to structure deployments with privacy in mind — including driver-facing camera policies, retention periods and staff notification requirements.
Retention and deletion
Keep what you need. Remove what you don't.
Configurable video retention periods let customers reduce ongoing data exposure. Footage outside retention scope can be deleted on customer-defined schedules.
What these capabilities mean in a
real deployment.
Written for fleet managers, IT leads and compliance staff — not marketing audiences.
Data residency
Video footage, metadata and user data processed through FleetView is stored on Australian-hosted infrastructure. This supports Australian data sovereignty requirements and removes the need to rely on international data transfer frameworks for operational data.
User and access management
Administrators define user roles and access levels within FleetView. Access can be limited by vehicle, fleet group, depot or user function. Footage viewing, downloading and deletion are each individually permissioned — not open to all users by default.
Audit and evidence trail
FleetView logs access events against authenticated users. When footage is viewed, exported or deleted, the action is recorded — supporting both internal accountability and evidentiary integrity of footage used in insurance, legal or regulatory contexts.
Driver and passenger privacy
Driver-facing and passenger-monitoring cameras capture sensitive personal information. transiCAM works with customers to establish appropriate access restrictions, retention policies and staff disclosure practices consistent with applicable privacy obligations.
Retention and deletion
Customers can configure footage retention periods appropriate to their operational and legal requirements. Footage outside retention scope can be systematically removed. Retained footage is stored in Australia and subject to the access controls defined by the customer.
Geotab integration context
FleetView video data is separate from Geotab telematics data but can be linked contextually within FleetView for joint review. Geotab's own platform security and data handling applies to Geotab data independently.
Straight answers beat vague assurance language.
Being specific about what FleetView is and isn't builds more useful trust than generic security marketing.
- 1 FleetView data is Australian-hosted. We describe this factually — not as a certified compliance outcome.
- 2 We do not currently hold ISO 27001, SOC 2 or ASD Essential Eight certifications. If your organisation requires verified certification, discuss this with us before proceeding.
- 3 Privacy compliance obligations sit with the fleet operator as data controller. transiCAM provides platform capability and deployment guidance — not legal advice.
- 4 Geotab's own security practices apply to Geotab telematics data. FleetView video data is governed separately.
Government and council fleets have stricter requirements. We understand that.
Public sector operators often face additional governance obligations — including data sovereignty requirements, privacy legislation compliance, records management obligations and procurement conditions that require factual data handling disclosures.
FleetView's Australian data hosting is a starting point, not an end point. transiCAM can discuss specific requirements, provide factual platform documentation and work through deployment approaches that align with your organisation's obligations.
If your procurement process requires a security questionnaire, data flow documentation or specific contractual representations, raise this early in the conversation.
Relevant for public sector procurement
- Australian data residency — video and metadata hosted in Australia
- Role-based access with user-level audit logging
- Customer-controlled retention and deletion schedules
- No third-party access to footage without customer authorisation
- Deployment guidance for driver and passenger privacy obligations
- Willingness to engage with security questionnaires and tender requirements
Need specific documentation? Contact transiCAM directly — don't rely solely on this page.
If security or data handling is a factor in your decision, let's have that conversation specifically.
Bring your questions, your procurement requirements or your compliance obligations. The transiCAM team can walk through how FleetView handles data in your specific context.