Legal Readiness
How MATO D2D collects, uses, protects, and stores passenger, booking, payment, wallet, support, waitlist, and tracking information.
MATO D2D policy framework
This page explains the passenger, platform, payment, privacy, and journey rules that apply while using MATO D2D services.
MATO D2D may collect passenger name, mobile number, email, route, pickup and drop point, passenger details, selected berth, booking history, payment reference, wallet transactions, support messages, feedback, complaints, luggage records, notification preferences, device signals, and journey tracking events.
Passenger data is used to process bookings, issue QR tickets, manage boarding, track luggage, send journey alerts, operate wallet and refunds, provide support, prevent fraud, improve safety, calculate reliability metrics from real data, and maintain the MATO D2D operating platform.
MATO D2D may store payment status, transaction references, order identifiers, refund status, wallet ledger entries, cashback, compensation, loyalty credit, and recharge history. Sensitive payment credentials are handled by authorized payment providers and should not be stored in plain text by MATO D2D.
Data may be shared only when needed with payment gateways, communication providers, support staff, verified drivers or crew, operational administrators, fleet partners, legal authorities, or service vendors who help complete the passenger journey. MATO D2D does not sell passenger personal data.
MATO D2D uses role-based access, passenger ownership checks, protected dashboards, secure API flows, audit-ready records, and limited staff visibility. No digital platform can guarantee absolute security, but the system is designed to reduce unauthorized access and data exposure.
Booking, payment, wallet, support, tracking, and compliance records may be retained for operational, legal, audit, tax, and dispute-resolution purposes. Passengers may contact support to request correction, review, or reasonable deletion of eligible personal information.
