This policy is maintained at https://palingen.com.au/privacy/mtfc. Support: https://palingen.com.au/support/mtfc.
Updated 16 October 2026 · iPhone, iPad, Android and manager portal
MTFC (Move The Fleet Car) is a restricted workforce tool for vehicle movements, check-ins and fleet operations. Device access is issued by a fleet manager.
Records can include the driver’s name and Work ID (WWID), vehicle registration and MVA, odometer, selected origin/destination or check-in site, timestamps, notes, device identifier and assigned zone. Authorised fleet and VAR tools also display vehicle availability and related operational records. A note can contain personal information if somebody enters it; include only information needed for the work.
Movement origins, destinations and check-in sites are selected or entered depot names, not GPS positions. The mobile app does not request device location. Camera scanning reads plates, MVA numbers and invitation QR codes on the device; scan frames are discarded and are not uploaded. Fleet reference images managed in the portal are separate from mobile scanning.
Movement records are summarised for fleet planning. Management reports contain fleet totals rather than a driver league table. The reporting page shows fleet totals; names remain attached to individual work records so a particular movement can be checked. Estimated hours derived from the first and last movement of a day are a planning measure, not a timesheet. These records must not be the sole basis of decisions about pay, performance, discipline or hours.
Enrolled devices can register Apple APNs or Google Firebase Cloud Messaging push tokens to receive fleet messages. Android also checks with signed requests. Declining notification permission leaves messages available inside the app. Manager identities, sign-in and administrative/security activity are processed to restrict and support access.
Current records are sent over HTTPS to the fleet’s Cloudflare Worker and D1 service. Authorised fleet integrations provide vehicle and VAR information. Historical records from the former system remain in a protected read-only Google Workspace archive. Resend delivers sign-in codes, vehicle alerts and management reports and processes the recipient address and message. Apple and Google deliver platform notifications. Records are available to authorised operational staff and providers supporting the service.
Device submissions are signed with credentials issued at enrolment. The mobile apps use a fixed endpoint allowlist, and signing credentials and local operational records are excluded from device backup. Acknowledged local records are pruned. Fleet business records remain for as long as the operator needs them for administration, auditing, reporting and applicable obligations. Revoking access does not itself erase previously submitted business records.
MTFC has no advertising or third-party analytics SDK and does not sell information. Ask your fleet administrator or the privacy contact below to access, correct or request deletion of your information. Some employment or business records may need to remain for a legal or legitimate operational reason; the responsible operator can explain this. MTFC is a workplace tool, not a children’s service.
Palingen publishes this app and this notice. Where your organisation uses the app for workplace operations, that organisation controls the operational records it enters and the staff who can access them. Contact your administrator about those records, or contact Palingen for help routing a request.
Hosting, security, email and platform providers process information needed to deliver their services. Cloudflare hosts this policy website and relevant Cloudflare services described above. Provider networks and subprocessors can process information outside Australia. Provider logs, recovery snapshots and backups can have separate retention periods. These policy pages do not send a visit to Palingen’s visitor-printer feed.
Use the contact below for privacy questions, access or correction requests, deletion requests and complaints. Include the app name and enough detail to locate the relevant information, without passwords, enrolment codes or unnecessary customer information. Identity may need to be verified. We will consider the request and explain any limits, including records controlled by your organisation, legal retention, backups or copies already printed or shared.
If a concern is not resolved, you can contact the Office of the Australian Information Commissioner where applicable. This policy will be updated at this address when practices change.
Contact: privacy@mtfc.net.au
MTFC support · OAIC privacy complaints