Status: draft for attorney and compliance review before public launch.
MeGo connects customers, mobile mechanics, shop partners, parts drivers, and operations staff so vehicle service can be requested, dispatched, completed, paid for, reviewed, and supported.
Information MeGo Expects To Collect
•
Account information: name, email address, phone number, password credentials, role, and profile status.
•
Vehicle and service information: vehicle year, make, model, trim, mileage, service request details, diagnostic notes, photos or evidence provided by users, estimates, approvals, cancellations, reviews, and disputes.
•
Location information: customer service address, shop address, mechanic service area, parts pickup/drop-off locations, route status, and approximate coordinates used for dispatch and delivery.
•
Payment information: payment method identifiers, authorization status, payment plan or installment selection, refunds, disputes, payout records, and provider event history. MeGo should not store raw card numbers.
•
Verification information: mechanic, shop, and parts-driver onboarding documents, license or insurance status, background-check status, and admin review notes.
•
Device and notification information: push tokens, platform, notification preferences, delivery attempts, and in-app notification history.
•
Support and safety information: audit events, fraud signals, support messages, no-show records, cancellation reasons, refund evidence, and trust-and-safety review history.
How MeGo Expects To Use Information
•
Create and secure user accounts.
•
Match customers with eligible mechanics, shop overflow partners, and parts drivers.
•
Price, schedule, dispatch, complete, and support vehicle-service jobs.
•
Process payments, installment options, refunds, disputes, tax reporting, and mechanic payouts.
•
Send transactional notifications by in-app message, push notification, email, or SMS.
•
Verify operators, prevent fraud, enforce platform rules, and improve safety.
•
Debug, monitor, audit, and improve MeGo products and operations.
•
Comply with legal, regulatory, payment-network, tax, insurance, and app-store obligations.
Sharing
MeGo may share limited information with the users and providers needed to complete a job, including customers, mechanics, shop partners, parts drivers, payment processors, notification providers, hosting providers, analytics or monitoring providers, identity or background-check providers, insurance or legal support, and government authorities when required by law.
Retention
Production launch needs a final retention schedule. Expected retention categories include account records, completed service records, payment and tax records, safety/audit logs, support records, and deleted-account records that must be retained for legal or fraud-prevention reasons.
User Choices
Users should be able to update account information, manage notification preferences, request account deletion, request access or correction where required, and contact support for safety, privacy, refund, or dispute issues.
Children
MeGo should not be marketed to children. Public launch materials should state the minimum age required to use the service.
Security
MeGo should use encrypted transport, hashed passwords, least-privilege production credentials, provider tokenization for payments, audit logging, operational monitoring, and controlled staff access before public launch.
Contact
Privacy questions can be sent to the support contact below. The company legal name and mailing address shown publicly will be finalized before public launch.