Driver & delivery policy

1. Scope, status and who is responsible

This policy accompanies terms version 2026-09-13.droplog.17 and remains a review draft. It describes standards for restaurant/takeaway delivery operations and authorised driver use. The business must give drivers access to it and obtain any agreement or acknowledgement required for their engagement. Publication alone does not create a direct contract with a driver.

dropLog. supplies software. Businesses create offers and assign work; drivers choose whether to accept. UNLIMIT DIGITAL LTD does not provide delivery work, employ or supply drivers to businesses, run their deliveries or pay their drivers. The actual operating arrangements and mandatory law determine each party’s obligations; this statement does not remove responsibility for the platform’s own conduct.

The engaging business must establish its duties for each driver and country of work. Drivers have their own legal and safety responsibilities. The platform retains its own duties; a label, disclaimer or uploaded document cannot transfer statutory obligations or settle employment status.

A driver can connect with multiple businesses and accept or reject each proposed shift. Existing accepted commitments have priority; another overlapping shift cannot be accepted until the conflict is resolved. A driver can reject a previously accepted, unstarted shift with prompt notice to the business; the app records that decision, not any legal consequence. Revised times need renewed acceptance. Non-working rules do not cancel accepted shifts. Businesses receive generic conflict and workload warnings without another business’s identity, exact private schedule or the driver’s private time-off rules. Configurable workload alerts do not determine compliance with working-time or rest law.

Before offering replacement work, the business must state the shift, duties, fixed pay, any additional delivery fee, payment method and timing, expenses, breaks and applicable terms. Drivers must review the offer before accepting and promptly notify the business if unable to attend. Acceptance records the agreement and reserves a schedule; it does not start a shift, transfer payment, determine employment status or remove either party’s statutory duties. The business remains responsible for lawful pay, right-to-work, licensing, insurance and safe scheduling. Provider or device failures may delay reminders, so parties must maintain an appropriate contact and attendance process.

The development pilot includes native phone accounts, business-directed compliance review, shift reminders, receipt scanning and route tools. Store release, live notification providers, automated arrival messaging and a shared cross-business network remain subject to release work. The presence of a tool does not establish that a particular driver has passed the required checks.

2. Restaurant and takeaway responsibilities

• Identify the entity engaging each driver, the country of work and the actual working arrangement. Carry out the right-to-work checks legally required for that engagement before work starts, repeat checks when required, observe restrictions and retain the prescribed evidence. A declaration by a driver or an uploaded document does not replace the required check.
• Check driving entitlement for the actual vehicle and maintain evidence of valid insurance covering the actual delivery activity, including hire-and-reward cover where required. Verify applicable vehicle registration, roadworthiness, MOT or local inspection requirements. Confirm cover with the insurer; ordinary private-use insurance must not be assumed to cover deliveries.
• Record who checked each requirement, when, the method, evidence, restrictions and any expiry or follow-up date. Review changes in vehicle, licence, insurance or work entitlement promptly. Do not allocate work that the driver is not lawfully entitled or insured to perform. Arrange a safe handover of an affected live delivery.
• Give drivers clear engagement, pay, expense, cash-handling and safety instructions. Meet applicable employment, minimum-pay, working-time, rest, tax, pension and health-and-safety duties. A per-delivery fee or a self-employed label does not determine legal status or remove statutory rights. Do not use a ledger discrepancy to justify an unlawful deduction.
• Control staff access, supply this policy to authorised drivers and arrange any necessary valid acknowledgements or agreements. Take reasonable steps to ensure authorised users comply. Do not let another business use your account or share a driver across businesses through an unapproved arrangement.

3. Driver responsibilities

• Provide accurate information and authentic, current evidence requested through the authorised check process. Promptly tell the engaging business about relevant changes, restrictions, expiry, suspension or cancellation affecting the work. Do not drive when you lack the required entitlement or cover; do not falsify or alter evidence.
• Follow road traffic law, applicable safety requirements and lawful delivery instructions. Stop safely before handling the app or changing a route. Never speed, use a hand-held phone unlawfully, enter unsafe premises or drive while impaired or unfit to meet an ETA or accept an extra job. Report safety concerns and take required breaks.
• Use only your authorised account and approved vehicle. Do not share credentials, impersonate another driver, spoof GPS or falsely record a delivery, cash collection, mileage or shift. Any substitute must go through the applicable business authorisation and legal checks; this does not itself create a right of substitution.
• Handle food, sealed packages and customer cash carefully in accordance with the business instructions. Record the amount actually collected, return money as agreed and report discrepancies, damage, failed deliveries and incidents promptly. A reminder does not authorise an extra charge or prove that a customer owes money.
• Use customer addresses, phone numbers and delivery instructions only for the authorised job. Do not retain contacts for personal use, send marketing, disclose them to another driver without authority, or publish customer information. Do not harass or discriminate against customers, colleagues or other road users.
• Protect your device and report suspected account compromise or data loss promptly through the engaging business and the platform contact route as appropriate. Do not send passwords, full identity documents or payment-card details in ordinary support messages. In an emergency contact the emergency services; the platform is not an emergency-response service.

4. Evidence, changes and expiry

The business must use the applicable prescribed check method, record the reviewer, decision and date, and follow up on restrictions or expiry. The driver must provide accurate information and notify changes. Use a secure approved channel for required evidence; do not upload driver documents into the current business-application evidence facility or delivery notes.

An automated reminder, uploaded file, scanned image or business approval is not verification by a government authority, insurer or the platform. Until driver-check tools are enabled, the business must maintain its own checking and renewal records. When tools are enabled, it remains responsible for reviewing evidence and following up even if a notification fails.

Do not start or allocate work that is not lawfully permitted or appropriately insured. If a concern arises during a delivery, stop new allocation and organise a safe resolution with the engaging business. Preserve cash and delivery records. Do not bypass a restriction by using another account or falsely changing vehicle details.

5. Tracking and customer information

Tracking must be transparent, necessary and limited to an authorised work purpose. The business must provide the driver notice, establish a lawful basis, assess monitoring risks and restrict access. A phone permission or policy acknowledgement is not blanket consent to employee monitoring. Covert or off-duty tracking is prohibited.

The current backend accepts location only for an active shift, stores the latest point and limited stop anchors, and clears the latest point when the shift ends. It records observed stop durations, waiting and break periods, battery reports and delivery timing for review. During active paid-subscription shifts, accepted GPS reports are also archived for journey review. Businesses can see thirty days; authorised administrators can access older records for a recorded purpose until reviewed erasure. The archive has no automatic deletion. Businesses must explain this monitoring and the justified retention criteria before recording begins. GPS gaps cannot be reconstructed, and this record is not guaranteed to capture every movement. Drivers and customers can use the privacy notice and GDPR rights routes to raise concerns; system records are not conclusive proof of conduct.

Customer details may be used only for the authorised delivery. Future SMS/WhatsApp arrival notices need the relevant notice, preferences and channel permissions; do not infer opt-in from a phone number. Do not export contacts for personal use or disclose job details to unassigned drivers or other businesses.

6. Reporting concerns and fair review

Report unsafe instructions, suspected fraud, lost devices, data incidents and inaccurate records promptly to the responsible business and, where relevant, the platform contact route. Contact emergency services for immediate danger. Do not delay a legally required report while waiting for an app response.

A concern may justify immediate proportionate access restriction where needed for safety, security or law. Preserve evidence, explain the reason when lawful and practicable, and provide an appropriate correction or human-review route. Do not retaliate for lawful reporting or use disputed GPS/cash records to make unlawful deductions.

Nothing in this policy removes non-excludable rights, authorises discriminatory treatment, determines employment status, makes a driver guarantee another party’s debts or prevents complaints to a regulator, court, tribunal or insurer. Working electronic support and incident channels must be finalised before public launch; the published company postal contact remains available for non-urgent correspondence.