Effective date: 30 August 2026.

KiloDrive is built around movement, so location and trip information are essential to parts of the service. We also know that seeing “Allow location in the background” can feel intrusive. This Privacy Policy explains, in plain language, what KiloDrive collects, why we need it, who can see it, how long we keep it, and the practical steps you can take to stop collection or ask us to delete information.

This Policy applies to the KiloDrive mobile applications, websites, portals, support channels, ride and parcel marketplaces, rentals, driver onboarding, payments, wallets, safety tools, and related services (together, the “KiloDrive Platform”). Country-specific notices shown in the Platform supplement this Policy where local law gives you additional rights or requires different handling.

1. Who this Policy covers

This Policy applies to riders, travelers, payers, drivers and driver applicants, parcel senders and recipients, rental customers, rental providers and team members, family or business profile managers and members, authorized guardians and dependants where a supervised-travel product is lawfully enabled, sole traders and driver businesses, portal users, website visitors, support contacts, and anyone whose information is provided in connection with a service. A person who books, supervises, or pays for someone else must have authority to provide the minimum necessary information and should direct that person to this Policy.

2. Who controls your information

The KiloDrive operating entity responsible for the country in which a service occurs is normally the controller of information required to provide that service. A separate entity may control payment, identity-verification, insurance, or regulated financial processing. The applicable operating entity and contact details must be identified in the country schedule, receipt, or support response. KiloDrive service providers process information under contract and instructions unless they act as independent controllers under law.

3. Information you provide

  • Account and profile information: name, email, phone number, country, language, timezone, profile photograph, account role, preferences, accessibility settings, referral information, and authentication details. Passwords are stored only as protected hashes.
  • Driver and business information: date of birth or eligibility evidence where required, licence, identity documents, selfie/profile photograph, address, prior-platform username or rating-import request, driver status, membership, business type, legal and trading names, registration and tax identifiers, business contacts, beneficial-owner or representative information where legally required.
  • Vehicle information: make, model, year, category, colour, plate, registration, insurance, inspections, photographs, document expiry dates, and administrative review notes.
  • Ride and delivery information: pickup, destination, stops, saved and recurring routes, requested time, proposed fare, bids, passenger or recipient details, parcel description and handling instructions, proof of pickup or delivery, ratings, cancellations, disputes, lost-item reports, and safety reports.
  • Payment and payout information: transaction amount, currency, payment method, provider reference, wallet and immutable ledger records, membership charges, refunds, chargebacks, cash obligations, escrow holds, cashout requests, masked payout destination, bank/branch selection, PayPal identifier, tax information, and fraud-review evidence. KiloDrive does not intentionally store full card credentials.
  • Communications and content: in-app chat, support tickets, contact forms, notification preferences, survey responses, ratings, photographs, documents, call metadata, and files or evidence you choose to submit. Private chat content is not written to operational application logs, but it remains stored where needed to provide chat, safety, support, or legal functions.

4. Information collected when you use KiloDrive

  • Location and route information: approximate or precise device location, pickup and destination coordinates, active-driver location, ordered trip GPS samples, route deviations, stops, speed or heading where available, traffic and ETA results, geofence confirmations, and last-known location. Location collection depends on your role, permissions, and whether a trip or safety feature is active.
  • Device, session, and network information: IP address, proxy and Cloudflare forwarding information, device and installation identifiers, operating system, app version, browser type, mobile network, push token, login/session activity, connected devices, security settings, App Check results, and diagnostics.
  • Usage and operational information: screens and features used, searches, button and notification interactions, request timing, API and provider outcomes, crash data, performance measurements, correlation IDs, and redacted security or audit events.
  • Safety and fraud signals: account linkage, unusual devices or locations, failed logins, payout and top-up velocity, cooldown events, route anomalies, duty time, disputes, reports, duplicate instructions, and risk or confidence scores used to refer activity for review.
  • Website technologies: essential cookies and local storage, consent choices, and—where enabled and lawful—analytics and measurement information described in our Cookie Policy.

5. Information received from others

We may receive information from other users involved in a service; driver businesses and authorized representatives; payment processors, banks, and payout providers; identity and document-verification services; mapping and traffic providers; app stores and social-login providers; communications providers; insurers and professional advisers; fraud-prevention and device-integrity providers; public records and lawful authorities; and people who make referrals, complaints, disputes, or safety reports. A recipient may provide proof of delivery or a rider may provide feedback concerning another participant.

6. How we use information

  • create, authenticate, secure, and administer accounts, devices, roles, permissions, preferences, and tenants;
  • verify phone numbers, identities, drivers, businesses, vehicles, documents, insurance, memberships, and continuing eligibility;
  • locate nearby eligible drivers, widen an offer area, display driver availability, facilitate bids, match participants, route journeys, calculate distance, traffic-aware ETA, and estimated or proposed fares;
  • operate rides and deliveries, scheduled and recurring bookings, saved routes, chat, calls, notifications, trip sharing, live status, proof of delivery, trip replay, support, ratings, and receipts;
  • process wallet entries, external payments, holds, escrow, membership fees, cash obligations, refunds, chargebacks, cashouts, payouts, reconciliation, tax and accounting records;
  • protect users and the Platform through driver verification, duty limits, route-anomaly detection, safety check-ins, incident response, access control, fraud detection, abuse prevention, auditing, and investigation;
  • provide customer support, resolve complaints and disputes, recover lost property, enforce agreements, and establish, exercise, or defend legal claims;
  • maintain, troubleshoot, test, measure, and improve reliability, accessibility, product design, dispatch, marketplace health, and operational performance;
  • send transactional messages and, with any consent required by law, promotions or product communications; and
  • comply with transport, licensing, insurance, financial, sanctions, tax, accounting, privacy, safety, court, and lawful government requirements.

7. Automated processing and human review

KiloDrive uses rules and automated processes for nearby-driver discovery, offer ordering, traffic and ETA calculations, eligibility, duplicate-request prevention, account security, fraud signals, cashout blocks, and safety alerts. Inputs can include location, availability, service type, vehicle eligibility, request expiry, transaction history, device linkage, and reported incidents. These processes may delay, block, rank, or refer an action for review. They do not guarantee a match, price, outcome, or safety. Where applicable law grants a right to information, objection, or human review of a decision producing legal or similarly significant effects, you may request review through Contact Us.

8. When information is disclosed

  • Between users: drivers may receive the rider or sender’s first name, rating where enabled, pickup, destination, stops, proposed fare, service instructions, and limited recipient details needed for the service. Riders and senders may receive the driver’s name, photograph, rating, vehicle, plate, offer, ETA, and location during the service. A trip-share recipient receives limited live-trip information until the link expires.
  • Driver businesses: an authorized business account may receive information concerning its drivers, vehicles, assignments, earnings, compliance, and incidents, subject to role and legal restrictions.
  • Service providers: cloud hosting, Valkey/cache, mapping, traffic, identity, document storage and scanning, communications, analytics, customer support, payment, payout, fraud, security, reporting, and professional-service providers receive only information reasonably required for their function.
  • Payment and legal participants: processors, banks, card networks, PayPal, insurers, auditors, tax advisers, regulators, courts, law enforcement, emergency services, or other authorities may receive information for payment processing, reconciliation, incidents, legal obligations, or valid process.
  • Corporate events: information may be disclosed in a financing, reorganization, merger, acquisition, insolvency, or sale, subject to confidentiality and applicable law.
  • At your direction: we disclose information when you use a sharing feature, connect a third-party service, authorize a representative, or otherwise give valid instructions.

KiloDrive does not sell personal information for money and does not operate as a data broker. Certain analytics or advertising disclosures may be treated as “sale,” “sharing,” or targeted advertising under some laws; where applicable, consent and opt-out controls will be provided.

9. Location, active trips, RideCheck, and live sharing

9.1 When location is collected

Riders may choose to use device location to set a pickup, find a place, estimate a route, or follow an active trip. Drivers use location to go online, receive nearby work, navigate to pickup, and complete an accepted service. Outside those user-requested functions, KiloDrive does not use precise location for advertising and does not follow a driver merely because the person has a KiloDrive account.

9.2 Active-trip background collection

Once a driver has a server-confirmed trip in Assigned/approaching, Driver arrived, or In progress state, the driver app may continue collecting precise location while KiloDrive is in the background, another navigation app is open, or the phone is locked. This keeps the rider’s progress view current and supports navigation, trip replay, RideCheck, route-change detection, and investigation of a safety report or disputed journey.

Tracking starts from the visible active-trip experience after the required device permission and disclosure. Android displays an ongoing “KiloDrive trip in progress” notification while its active-trip location service is running. iOS displays the system background-location indicator. KiloDrive does not use microphone, phone-call, or background-audio access to keep this tracking alive.

If connectivity is lost, the app keeps a protected, account-bound queue of no more than 500 unsent samples and removes queued samples older than 24 hours. It sends valid queued samples when service returns, using unique sample identifiers to prevent duplicates. A location sample alone can never complete, cancel, charge, refund, or settle a trip.

9.3 What the rider and other people can see

The assigned rider can see the driver’s trip progress, vehicle and plate, estimated arrival, and a freshness label such as “Live,” “Last updated,” or “Driver location temporarily unavailable.” The driver receives the rider’s pickup, destination, approved stops, and the limited instructions needed to perform the service. KiloDrive does not give either party unrestricted access to the other person’s location history.

A rider or driver may deliberately create a live-trip share link for a trusted person. The current link expires after 120 minutes unless revoked sooner. The public view exposes only limited trip context and a coarsened, bounded location history: by default, no more than the latest 15 minutes, sampled for display at approximately 30-second intervals. Anyone who receives the link may be able to view it until it expires, so do not post it publicly. A trip participant can revoke active links from the trip-sharing controls.

9.4 How RideCheck works

RideCheck compares active-trip telemetry with the planned route and trip state. It can identify signals such as a material route deviation, an unexpected prolonged stop, or a gap in fresh location updates. When appropriate, KiloDrive asks the rider whether everything is okay and offers choices such as allowing the route change, contacting support, or calling local emergency services. The rider’s response, the alert, relevant timestamps, and limited supporting location evidence are logged so the event can be reviewed.

RideCheck is a safety aid, not an emergency-response service and not a guarantee that KiloDrive will detect every dangerous situation. It does not automatically contact police or medical services unless a separate feature clearly says so and the user takes the required action. If there is immediate danger, call the local emergency number first.

9.5 How to stop location collection or sharing

  • Finish the active service: tracking stops when the trip is completed, cancelled, or unassigned, or when the server rejects or revokes the active-trip session.
  • Do not rely on closing the app: swiping KiloDrive away, opening another app, or locking the phone may not stop an active trip because background collection is the feature being provided.
  • Use device controls: you can disable KiloDrive’s location permission in Android or iOS Settings, and Android users can stop the visible foreground service. This stops new device location collection, but live progress, navigation, nearby matching, RideCheck, and continued performance of an active assignment may no longer work. The other party will see that location is stale or unavailable.
  • Log out: logout revokes the active session and stops KiloDrive’s native active-trip tracker. An active trip must first be completed, cancelled, or otherwise resolved where the Platform requires it.
  • Stop live sharing: revoke the trip-share link in the trip-sharing controls. Disabling a share link does not stop the driver’s operational active-trip telemetry; it stops access through that link.
  • Delete or restrict data: use Settings → Privacy & Safety → Delete account, submit a privacy request in Support, or use Contact Us. The retention limits below still apply to records we must keep.

9.6 Accuracy and access controls

Location can be delayed or inaccurate because of GPS conditions, device settings, battery controls, connectivity, maps, or provider outages. KiloDrive shows freshness instead of pretending stale data is live. Access to full trip replay is limited to authorized support, safety, and administrative roles, is audited, and is used only for legitimate operational, safety, dispute, fraud, insurance, or legal purposes.

10. Legal bases

Depending on jurisdiction and context, we rely on performance of a contract or steps requested before entering one; compliance with legal obligations; legitimate interests such as safety, fraud prevention, support, platform security, service improvement, and legal claims; protection of vital interests in an emergency; and consent for processing that requires it, such as optional marketing, some analytics, precise background location, or device permissions. You may withdraw consent prospectively, but withdrawal does not affect prior lawful processing and may make a feature unavailable.

11. Retention, account deletion, and legal holds

We do not keep every kind of information for the same length of time. We set retention by purpose, sensitivity, legal obligation, the period in which a charge or incident may be disputed, and whether the record is needed to protect a user.

  • Active location in the fast location service: the latest driver-location value normally expires after about 10 minutes unless refreshed.
  • Unsent location on the device: limited to 500 samples and 24 hours, then automatically discarded.
  • Live-trip sharing: the access link normally expires after 120 minutes or when revoked. The public view is limited to location from the latest 15 minutes by default.
  • Trip replay and safety breadcrumbs: ordinary active-trip location samples are scheduled for deletion after 365 days. A smaller incident evidence bundle may be retained longer when a safety case, insurance matter, charge dispute, court process, or legal hold is still open.
  • Account and profile: kept while the account is open, then eligible fields are deleted or irreversibly anonymized through the account-deletion process.
  • Driver, vehicle, and verification records: kept while required to decide or prove eligibility and for the applicable transport, insurance, complaint, and limitation periods.
  • Transactions and legally required records: wallet entries, accounting journals, payments, payouts, refunds, chargebacks, tax records, and the minimum service record are kept for the period required by applicable financial, tax, anti-fraud, insurance, and recordkeeping law. These records are restricted and are not kept for marketing.
  • Support, security, and audit information: kept for the configured operational period, or longer only when an unresolved case, fraud investigation, legal claim, or legal obligation requires it.

You can request account deletion in the app through Settings → Privacy & Safety → Delete account, through the support/privacy workflow, or through Contact Us. Before deletion, you may need to finish or cancel an active trip or open request, allow a pending cashout to finish, and withdraw or expressly forfeit a remaining wallet balance. This prevents deletion from silently abandoning another user’s trip or money.

When deletion is completed, KiloDrive revokes sessions and credentials, removes contact and authentication data, disables the account, and replaces eligible profile fields with a non-identifying deleted-user record. It does not rewrite immutable financial journals or erase a trip, safety, dispute, fraud, insurance, or legal record that must remain. Where possible, retained records are separated from direct contact details and access is restricted. A lawful suspension or fraud-prevention record may be kept to prevent immediate re-registration. Backups age out through their normal protected rotation rather than being altered in place.

A documented legal hold pauses ordinary deletion only for information relevant to the hold. When the reason ends, the normal retention schedule resumes. Country law may require a shorter or longer period; the applicable country notice or a response to your privacy request will explain a material difference.

12. Security

Measures include encrypted transport; private network services; protected secret storage; short-lived signed sessions; password rules; optional two-factor authentication and biometric app lock; device/session controls; tenant and role isolation; rate limits; private document storage; file type, size, and malware controls; Firebase App Check where enabled; idempotent financial operations; wallet locking and immutable ledger references; fraud review; correlation and audit records; sensitive-data redaction; readiness monitoring; backups; restoration and incident procedures. No system is completely secure, and users must protect credentials, devices, and one-time codes.

13. International and cross-country processing

KiloDrive uses a control plane and country transaction cells. A service requested while travelling normally belongs to the country where it occurs and uses that country’s currency and timezone. Providers may process information outside your country. Where required, KiloDrive uses contractual, technical, organizational, consent, adequacy, or other lawful transfer safeguards. Cross-country wallet conversion is not offered unless expressly disclosed under a compliant feature.

14. Your choices and rights

Depending on applicable law, you may request access, confirmation, correction, a portable export, deletion, restriction, objection, withdrawal of consent, information about automated processing, or human review. You may manage devices, permissions, notification categories, marketing choices, saved routes, payout methods, and certain profile information in the Platform. Device-level location, camera, photo, microphone, notification, and biometric permissions can be changed in operating-system settings. Changing a permission stops new access through that permission but does not erase information already lawfully collected; use the deletion or privacy-request process for that.

Submit a request through Contact Us or the available in-app privacy workflow. We may verify your identity, authority, country, and account before responding. We will not unlawfully discriminate against you for exercising a right. We may deny or limit a request where permitted—for example, when identity cannot be verified, another person’s rights would be affected, the request is manifestly unfounded or excessive, or retention is legally required. You may complain to the relevant privacy or data-protection authority.

15. Children, dependants, and supervised travel

No minor may register as a driver. KiloDrive does not enable a teen or dependent-travel product merely because a family profile exists. Where a country-approved supervised-travel product is offered, it requires verified guardian authority, age-appropriate disclosures, scoped trip visibility, explicit participant roles, revocation controls, and separate safety rules. KiloDrive does not silently expose the private rider-driver conversation to a guardian. If we learn that information was collected from an ineligible child without lawful authority, we will restrict the feature and take appropriate deletion or retention action.

16. Third-party services

Maps, app stores, social login, payment pages, external websites, and provider services have their own terms and privacy practices. KiloDrive is not responsible for independent processing by those parties. Review their notices before directing information to them.

17. Changes and contact

We may update this Policy to reflect product, legal, or operational changes. The effective date will change, and material changes will be communicated through an appropriate channel before they take effect where required. Previous versions should be retained for accountability.

For privacy questions, rights requests, or complaints, use Contact Us or email [email protected]. We will identify the responsible operating entity and, where applicable, the relevant regulator in our response. Do not include passwords, authentication codes, full payment credentials, or unnecessary identity documents in an ordinary message.