Please enable JavaScript.

Coggle requires JavaScript to display documents.

Legal Framework of Uber’s Metro Ticketing Terms, Predictability for…

- - - - Explanation: Contract formed by affirmative act (use of app / browsing). No handwritten signature needed.
      - Key legal principle: Acceptance by conduct; enforceable if terms are reasonably brought to user’s attention.
        
        Contract breakdown
        
        Acceptance: User’s access/use = acceptance (click/browse).
        
        Consideration: Payment for tickets / convenience.
        
        Offer: Uber offers the Services via platform.
      - Statutes to cite: Indian Contract Act, 1872 (what constitutes valid contract — offer, acceptance, consideration, free consent).
    - - Explanation: Pre-drafted, non-negotiable; take-it-or-leave-it.
      - Legal consequence: Courts may enforce but can examine fairness; consumer protection principles apply.
      - Subnodes: predictability for business vs. inequality of bargaining power for consumer.
    - - Quote: “Uber may amend the Terms… Your continued access or use of the Services after such posting constitutes your consent.”
      - Legal analysis: Clause permits unilateral changes by Uber; user consent constructive via continued use.
      - Implications: Users may be bound to future changes they didn’t read.
      - Counterpoint: Reasonable notice & material change standards (good practice) — courts may scrutinize surprise/unconscionable changes.
    - - Quote: “Uber may immediately terminate these Terms or any Services with respect to you… at any time for any reason.”
      - Legal analysis: Broad termination right; commercial flexibility for Uber (security, abuse, legal compliance).
      - Implications for user: Sudden service loss; need to retain receipts/proof for disputes.
    - - Quote excerpt: “In provision of the Services, Uber may collect and share your personal information. By accepting these Terms, you will be providing your consent to Uber to collect, process, transmit, store, use, disclose, share, deal, handle, and transfer personal information.”
      - Statutory context: DPDP Act, 2023 (data protection), IT Act references.
      - Subnodes: scope of data, third-party sharing (insurers/claims processors), user rights (access, correction subject to law).
    - - Quote: “Supplemental terms may apply… Supplemental terms shall prevail over these Terms in the event of a conflict.”
      - Practice: Event-specific terms (promotions, refunds) can override base T&Cs; always check linked policy pages.
    - - Courts examine fairness/unconscionability under consumer protection jurisprudence (not automatic invalidation).
      - Materially unfair terms (e.g., deceptive or contrary to statute) can be struck down.
      - Practical tip: Encourage capturing timestamps and screenshots on acceptance, changes, receipts.
    - - Immediate actions: Preserve booking receipts, transaction IDs, screenshots of terms at time of booking.
      - Remedies: Raise internal dispute to Uber support → if unresolved, consumer forum/NDPS/Appropriate court.
      - Evidence strategy: Show timeline (notice of change, booking date, service failure).
    - - Are unilateral amendments fair? Where should the line be for “material” changes needing active re-consent?
      - Should users have statutory minimum protections (notice periods; opt-out)?
      - How does DPDP Act change implied consent rules?
- - - - Explanation: Uber provides marketplace tech and payment facilitation but does not operate transport.
      - Legal labels: Intermediary / platform operator / limited payment collection agent (as contract states).
      - Why this matters: Allocation of legal responsibility — Uber attempts to avoid being treated as carrier/provider.
    - - Concept: Tickets and transport services are offered by independent Transportation Service Providers (e.g., DMRC, CMRL).
      - Legal effect: Primary contract for carriage is between user and the transport provider → privity.
      - Implication: If train/coach provider fails, user's claim is against operator primarily; Uber’s liability limited.
    - - Contract language: Uber disclaims guarantee for accuracy/completeness of information (schedules, images).
      - Risk: Misinformation risk for users (e.g., wrong timetable).
      - Mitigants for user: Cross-verify with operator’s official site; check ticket confirmation.
    - - Explained: Uber helps process payments, handle support tickets, and may arrange pickups. It may act as payment collection agent.
      - Legal nuance: Acting as collection agent can make Uber a conduit for payments — but not necessarily liable for operator’s contractual obligations.
      - Practical: Refunds & charge adjustments are governed by Uber’s payment rules + operator policy.
    - - Quote: “Services are made available solely for your personal, non-commercial use.”
      - Effect: Prevents resale or commercial exploitation via the platform (policy enforcement ground).
      - Enforcement: Account suspension/termination for misuse.
    - - Explanation: Services are offered through ONDC — open network that promotes interoperability of digital commerce in India.
      - Legal & policy significance: Shows compliance with government-enabled platform architecture; increases reach but can complicate liability chains.
    - - Legal tension: Intermediary disclaimers vs Consumer Protection Act, 2019 — consumers retain rights; an intermediary cannot evade statutory duties where law imposes affirmative obligations.
      - Example disputes: Wrongful cancellation, duplicate booking, non-availability despite confirmation.
      - User path: Raise complaint with operator + escalate to Uber; consumer forum if unresolved.
    - - Causes: Platform downtime, ONDC outages, operator system glitch.
      - Contract line: Uber disclaims interruption liabilities.
      - Mitigation (user): Capture timestamps; ask for operator’s written confirmation; bank chargeback if payment erroneous.
    - - Scenario A: User books DMRC ticket via Uber — DMRC cancels service → who refunds? (Operator primarily; Uber facilitates inquiry).
      - Scenario B: Ticket price displayed incorrectly due to typo → Uber disclaimers + possible corrective action (refund/adjustment if Uber decides).
    - - Role: Facilitator (not carrier)
      - Payment agent: processes payments on behalf of operator
      - Third-party responsibility: operator liable for carriage/service
      - Accuracy disclaimer: schedules/images may be illustrative only
      - Personal use only: no resale
      - ONDC integration: interoperability & policy implications