About this policy
TUKU is operated by T2 Technology. This policy describes TUKU’s Rider and Driver app (com.tukuride.tuku), its API and this website. Contact us using the privacy email below for personal-data questions or requests, and the support email for general product help.
Account and authentication
TUKU processes your mobile number, verification status, first and last name, language, account status and sign-in timestamps. Verification uses short-lived hashed codes and session credentials. Your phone number is sent to the messaging provider to deliver a verification message.
Rider location and planning
Precise location helps set pickup and find nearby eligible Drivers. Pickup, destination, route distance and duration, fare quotes and ride requests are processed by TUKU. Search terms, place identifiers and coordinates are used with mapping, place-search and routing services. Recent destinations and pending shared locations are stored on the device, not uploaded as a separate history. Confirmed ride locations become trip data.
Driver location while Online
When a Driver deliberately goes Online or has an active trip, TUKU collects and updates precise location, including while the app is minimized or the screen is locked through its operational location service. Location supports availability, discovery, pickup, navigation and trip progress. Nearby discovery limits precision; assigned-trip participants and active sharing-link recipients can receive relevant live location. Device permissions, connectivity and the operating system affect updates. Going Offline ends availability tracking; active-trip location has its own lifecycle.
Driver identity and vehicle review
Driver applications include an identity-document image, selfie, vehicle photograph, vehicle colour and identifier, review state and review actions. These support onboarding and approval. They are stored as private media and accessed through authorized administrative controls, rather than published in nearby discovery. The app does not currently offer general account profile-photo uploads.
Trips, chat and ratings
We store ride requests, offers, pickup and destination coordinates and service areas, trip states and timestamps, fare and cash-payment confirmation, cancellations, destination changes and ratings. Trip chat stores message content and sender information for the participants. Temporary trip-sharing links allow recipients to view limited active-trip information. Share links only with people you choose.
Devices, notifications and subscription records
TUKU stores installation identifiers, notification tokens, platform and language to deliver ride and chat notifications through Firebase Cloud Messaging. Driver subscription entitlement and status are stored. Operational records may also contain externally recorded subscription payment amounts, provider/reference details, review status and administrative notes; the mobile app does not provide subscription checkout.
Website visitors
This website adds no advertising pixels, analytics SDKs or tracking cookies. Hosting may process IP addresses, request information and security/access logs to serve and protect the site. Service Areas requests the public area list; Support and Contact request the current public WhatsApp setting without sending account credentials. The deletion form sends the phone number, verification code and request confirmation to TUKU’s API; verification credentials remain in memory, not browser storage or URLs. If you choose to contact us by email or WhatsApp, your contact details and message are processed to respond, using those services under their own terms.
Why data is used and who receives it
Data supports authentication, matching and operating rides, Driver review, navigation, chat, notifications, entitlement administration, support and abuse prevention. Providers include Google Maps Platform (maps, Places and Routes), Firebase/FCM (notifications), UltraMsg/WhatsApp (verification and configured Driver communications) and infrastructure hosting. External payment administration may reference WHISH records. Providers may process data in locations outside Lebanon under their own terms. We do not add advertising-data collection to this site.
Access, sharing and security
Riders, assigned Drivers, authorized administrators and selected sharing-link recipients receive the information needed for their role. TUKU uses access controls, private-media delivery, token controls and rate limits. No system can promise absolute security. Do not send identity documents, login codes or other sensitive material in ordinary trip chat.
Retention and deletion
Data is kept only as long as needed to operate the service, address legitimate security or dispute needs, or meet accounting and legal obligations where applicable. It is deleted or de-identified when no longer needed. Uninstalling the app does not delete the server account. Use Account deletion to verify your phone and submit an explicit request without installing the app. Requests are reviewed, with active rides, unsettled payments or specific unresolved cases addressed before processing. The deletion workflow removes your login identity, sessions, device tokens, Driver identity/vehicle media, unnecessary contact details, trip chat and precise trip locations. Completed-trip, payment and audit records remain without your name or phone number to preserve trip and financial integrity. These records can include dates, service areas, amounts, statuses and rating references; they are de-identified or pseudonymous, not guaranteed anonymous. Personal data is removed at successful completion unless a specific documented hold applies. Holds are reviewed and must remain justified; a restriction on ride eligibility alone is not a reason for indefinite retention. No fixed accounting retention period is stated here, and keeping financial integrity does not require your real name or phone number. We keep a minimal request and completion audit without your deleted contact details or verification codes. Older backups may temporarily contain pre-deletion data and expire under the normal backup lifecycle. If an older backup is restored, completed deletions must be reapplied before service resumes. Provider-side records follow the relevant provider’s capabilities and policies; local deletion does not promise erasure of a delivered message or provider infrastructure logs. Deletion requests can be submitted; processing is not yet enabled while operational readiness is verified.
Your choices and requests
You can update available profile details, control device permissions, go Offline as a Driver, stop sharing a trip, and request account deletion. Restricting permissions may prevent relevant features from working. For access, correction, privacy concerns or verification problems, contact the privacy email below. We need to verify your identity before acting on an account request. Never send a login code or password. The deletion form is a separate available request path.
Age and policy changes
You must be at least 18 years old to create or use a TUKU account. Registration does not currently collect date of birth or verify age. If you believe someone under 18 is using an account, contact our privacy email so we can review the concern. We will update this policy when the service or its data practices change, with the revision date displayed on this page.
Contact TUKU
Privacy and account-deletion requests: privacy@tukuride.com
General support: support@tukuride.com