WMFC is a restricted vehicle-turnaround coordination service for authorised fleet operations. Access to operational information is controlled through administrator-approved users and paired devices.
INFORMATION WE PROCESS
WMFC may process an authorised user's name, email address, role and access history; paired-device name, assignment, secure device identifier and last-seen time; vehicle registration and MVA identifiers; operational job details including customer surname, rental-agreement number, bay, priority, stage, ETA and notes; and audit records showing changes, timestamps and the responsible user or device. WMFC does not use advertising identifiers or collect precise location. WMFC also stores an Apple push notification token for a paired device that has been enrolled for notifications, so the service can wake that device when the board changes, and a one-way hash of the network address a pairing or sign-in attempt was made from, used only to rate-limit repeated attempts; the address itself is never stored.
HOW INFORMATION IS USED
Information is used only to provide vehicle-turnaround coordination, authenticate and secure access, support authorised fleet lookups, maintain an operational audit history, troubleshoot the service and meet applicable business or legal obligations. WMFC does not sell personal information, display advertising or track users across other companies' apps and websites.
CAMERA ACCESS
Camera access is used only when a user chooses to scan vehicle text or a barcode. Scanning is performed on the device. WMFC does not upload or retain camera images.
NOTIFICATIONS
A paired Apple device may be sent notifications. There are exactly three, and none carries customer information: a silent background wake saying a counter's board has changed, a visible alert when a vehicle is added at that counter in an emergency, and a visible alert when a vehicle at that counter has run past its ready time. Each says which counter and nothing else - no registration, MVA, surname, rental-agreement number, bay or notes - because a notification can appear on a screen in a public area. The app fetches the board itself once opened. The push token is held only while the device stays paired: revoking a device, reissuing its pairing code or turning notifications off deletes it, and the token is never returned by the service, shown in the portal or written to a log. Refusing the notification permission leaves the device fully working, because the board refreshes every fifteen seconds regardless.
STORAGE AND DISCLOSURE
Information is stored in access-controlled service infrastructure and is available only to authorised operational personnel and service providers supporting WMFC. Vehicle identifiers may be sent to the organisation's authorised fleet service to return matching vehicle information. Information is not made public.
RETENTION AND YOUR CHOICES
Operational and audit records are retained for as long as reasonably required for fleet operations, security and compliance. Authorised users may ask their WMFC administrator to review, correct or delete personal information where applicable. Device access can be revoked immediately by an administrator.
SECURITY
WMFC uses encrypted network connections, access controls, device pairing and audit records to protect information. No system can guarantee absolute security.
CONTACT
For privacy enquiries, access correction or deletion requests, email stadoobie@gmail.com. Do not include passwords, pairing codes or customer details in an unsecured message.
SUPPORT
For device access, ask your WMFC administrator to create a one-time pairing code, then open the app's Setup screen and pair the device. Pairing codes expire after one hour and can be used once.
COMMON CHECKS
Confirm the device has internet access and shows the correct operational location. Use Refresh on the live board after connectivity returns. If access was revoked or the device was replaced, request a new pairing code from the WMFC administrator.
REPORT AN ISSUE
Email stadoobie@gmail.com with the device name, assigned location, time of the issue and a short description. Do not include passwords, pairing codes or customer details in an unsecured message.
Effective 13 September 2026