Driver Telematics, GPS & Mobile App Policy

1.1 Low-Level Hardware Permissions:

• (a) Operation of the mobile application mandates the granting of high-precision Global Navigation Satellite System (GNSS/GPS) access permissions at the operating system level:
  • Apple iOS: CoreLocation framework authorization set to "Always Allow" or "While Using the App";
  • Google Android: ACCESS_FINE_LOCATION and ACCESS_BACKGROUND_LOCATION permissions.
• (b) Operating System Autonomy: The Customer and Driver acknowledge that mobile operating systems independently control hardware power states, antenna polling intervals, and permission dialogs.

1.2 Distinction Between OS Permission and App Duty State:

• (a) Granting background location permissions to the device operating system enables the software container to execute location polling when the application interface is minimized.
• (b) Hardware De-coupling: Revocation of physical satellite querying can only be executed by the end-user directly through device system settings (Settings → Tachyo → Location → Never).

2.1 Strict Shift-Bound Processing Window:

• (a) Telematics data processing, geographic vector calculations, and database persistence occur strictly and exclusively during an active duty shift.
• (b) An active duty shift is initiated programmatically when the driver completes the digital check-in sequence ("Start Shift" / "Asset Coupling") and concludes definitively when the driver executes "End Shift".

2.2 Post-Shift Packet Dropping at Edge Perimeter:

• (a) Any stray GNSS telemetry packets transmitted by a device hardware background process while in an inactive or uncoupled shift state are dropped at the API edge gateway without ingestion, persistence, or display.
• (b) Tachyo LTD covenants that it maintains zero historical database records, analytical profiles, or real-time maps of driver geographic positioning outside active operational shift logs.

3.1 Environmental Attenuation Factors: The accuracy, continuity, and availability of telematics data points are subject to external technical and atmospheric constraints beyond Tachyo LTD's control, including:

• (a) Signal blockage caused by transit through tunnels, subterranean loading bays, metal-clad logistics distribution hubs, or deep urban topography;
• (b) Battery preservation protocols enforced by mobile operating systems (e.g., Apple iOS Low Power Mode, Android Doze Mode, OEM memory managers);
• (c) Mobile cellular network dropouts, SIM card data starvation, or regional roaming latency.

3.2 Tachograph & Driving Hours Primacy:

• (a) Calculations displayed on the mobile interface (e.g., 4.5-hour continuous driving counters, 6.0-hour Working Time Directive meters) are mathematical estimators derived from mobile motion vectors.
• (b) In the event of any divergence between Tachyo mobile software telemetry and the digital vehicle tachograph unit (VU / Smart Tacho 2), the calibrated on-board vehicle tachograph and driver smart card maintain absolute legal precedence under Retained Regulation (EC) 561/2006.
• (c) Tachyo LTD accepts zero liability for roadside DVSA driving hours infringements resulting from telemetry drift, lost pings, or device power depletion.

4.1 Limited Optical Access Scope:

• (a) Device camera hardware access permissions are utilized solely to capture contemporaneous evidence of vehicle roadworthiness defects during daily walkaround checks and physical fuel pump purchase dockets.
• (b) The application does not maintain automated background camera access, video streaming capability, or facial recognition biometric processing.

4.2 EXIF Metadata & Geostamp Verification:

• (a) Photographs submitted through the walkaround defect inspection workflow automatically extract embedded EXIF metadata, capturing exact device timestamps and geographic coordinates at the moment of shutter actuation.
• (b) This metadata is processed to provide the Transport Manager with auditable cryptographic proof that the physical inspection was performed in proximity to the commercial asset, fulfilling DVSA Guide to Maintaining Roadworthiness evidentiary expectations.

4.3 Commercial Fuel Receipts & OCR Limitations:

• (a) Photographic captures of fuel and AdBlue dockets are processed via optical machine vision solely to extract transactional integers (litres dispensed, total value in £ GBP, VAT numbers).
• (b) Drivers and dispatch staff must manually verify parsed figures against the raw receipt image. Tachyo LTD disclaims liability for fiscal or HMRC VAT filing errors resulting from folded, faded, or illegible paper dockets.

5.1 Prohibition of Account Sharing: Drivers shall not disclose authentication credentials or share active mobile sessions with any other driver.

5.2 Vehicle Registration Association: The driver is strictly responsible for ensuring that the vehicle registration mark (VRM) entered during mobile check-in accurately matches the physical tractor unit and trailer coupled during the shift.

5.3 Tampering & Mock Locations: The use of mock-location developer tools, GPS spoofing software, or modified operating system kernels (jailbreaking/rooting) is strictly prohibited and results in immediate automated account suspension and formal notification to the Operator Licence holder.