Archived analysis

This page is old. EaseMyTrip was reviewed on 2026-04-11.

This is a historical, policy-only review. Policies, product behavior and source URLs may have changed since this analysis was published.

For current public evidence from website trackers, policy findings and proof samples, go to State of Privacy 2026.

Travel

EaseMyTrip

Ready Score 48/100
Sushant Pasumarty
ANALYSIS SUPERVISED BY Sushant Pasumarty
📅 11 Apr 2026

Discuss this page with an LLM

EaseMyTrip does a great job explaining *what* they collect, but falls short on the *how* of the new DPDP law. Their policy still relies on old-school bundled consent and lacks the specific deletion and grievance rights that Indian citizens now possess.

How To Read This Analysis

This is an archived policy-only review of the company's public privacy policy. It is not a government certification and it is not legal advice.

For current public evidence from website trackers, policy findings and proof samples, see State of Privacy 2026.

We look for:

  • Notice and consent clarity
  • Purpose limitation
  • Data minimization
  • Retention and deletion language
  • Vendor and processor disclosures
  • Data Principal rights
  • Grievance redressal
  • Breach and security posture

Source Check

  • Source policy was reviewed for this archived analysis, but the old policy URL is not linked because public policy locations may have changed.
  • Date reviewed: 2026-04-11
  • Company: EaseMyTrip
  • Readiness score: 48/100
  • Policies and product behavior may have changed since review
  • Whether the current source policy still matches this archived policy-only review
  • Whether app, web and product flows match the policy

What To Do With This

If your company has a similar data model, use this analysis as a warning map. Do not copy the score. Map your own data flow.

Ask internally:

  • Do we collect similar categories of personal data?
  • Do we share data with the same number or type of vendors?
  • Can users understand why their data is shared?
  • Can we prove deletion, retention and grievance workflows?
  • What evidence would we show if questioned?

If this analysis resembles your business model, the next step is not a better privacy-policy paragraph. It is a data map and gap analysis.

Book a DPDP readiness call

⚠️ Compliance Gaps

  • Bundled consent—using the site implies you agree to everything
  • Vague data retention periods using 'as long as necessary' language
  • No mention of a dedicated Data Protection Officer or DPB escalation
  • Missing the right to nominate a representative under Section 14
  • Generic cross-border transfer clauses without specific country safeguards
  • Lack of clarity on how long 'offline' channel data is kept

✅ Strengths

  • Very clear breakdown of mobile app permissions (GPS, SMS, etc.)
  • Explicitly mentions RBI and LRS compliance for international travel
  • Strong explanation of why specific data (like PAN) is needed
  • Clear warning about third-party partner privacy policies

Overview

EaseMyTrip is one of India’s biggest travel platforms. Think about the sheer amount of info they have on you: your Passport details, Aadhar/PAN numbers, Vaccination certificates, and even your live location when you use the app.

When a company handles this much “Sensitive Personal Data,” the new law (the DPDP Act) treats them as a Data Fiduciary — basically, a person or company that decides how and why your data is used. You are the Data Principal — the owner of that data. If you’re a business owner reading this, you’re likely a Fiduciary too, and the rules just got much stricter.

DPDP Readiness: Section-by-Section Analysis

EaseMyTrip uses a classic “Take it or Leave it” approach. If you visit the site, they assume you’ve said yes to everything.

What the policy says: “By using or accessing the Website or other Sales Channels, the User hereby agrees with the terms of this Privacy Policy.”

What the law requires: Under the DPDP Act, consent must be free, specific, informed, and unconditional. You can’t just bundle it into the terms of service.

The problem: If a user wants to book a flight but doesn’t want their email used for “surveys,” they don’t have a choice. It’s all or nothing. For your own business, you’ll need to start offering tick-boxes for different uses of data.

Section 7 — Certain Legitimate Uses ✅

The law allows companies to process data without explicit consent in some cases — like if you voluntarily provide it for a specific reason (booking a flight) or for legal requirements.

What the policy says: “For international bookings, User… may be required to provide details such as their PAN information or passport details… as per the aforesaid requirements only.”

The strength: EaseMyTrip correctly identifies that for things like the RBI’s Liberalized Remittance Scheme, they have to collect your PAN. This aligns well with Section 7’s allowance for “legal obligations.”

Section 8 — Obligations of Data Fiduciary ⚠️

A Data Fiduciary (the company) is responsible for keeping your data safe, even if they share it with a third party like an airline or hotel.

What the policy says: “EaseMyTrip shall not be held liable” for how end service providers (like hotels) use your data once EaseMyTrip passes it to them.

The problem: The DPDP Act says the primary Fiduciary is responsible for any processing done on its behalf. While EaseMyTrip can’t control an airline’s internal leaks, the law expects them to have solid contracts in place to protect the Data Principal (you).

Section 9 — Data Retention 🔴

This is a major sticking point in the new law. You can’t keep data forever just because “it might be useful later.”

What the policy says: “EaseMyTrip will retain User’s Personal Information… for as long as is reasonably necessary.”

What the law requires: Data must be erased as soon as the purpose for collecting it is served.

The problem: “Reasonably necessary” is too vague for the DPDP Act. If I book a one-time flight to Goa in 2022 and never return, should they still have my passport copy in 2026? Probably not.

Section 11 — Rights of Data Principal ⚠️

The law gives you “Superpowers” over your data, including the right to correct it, erase it, or nominate someone else to manage it if you pass away.

What the policy says: Users can access their account to “correct or delete such personal information… except for such mandatory fields.”

The gap:

  • It doesn’t mention the Right to Nominate (Section 14).
  • It doesn’t explain how a user who didn’t create an account (maybe they booked via a call center) can exercise these rights.

Section 12 — Right of Grievance Redressal 🔴

If you’re unhappy with how your data is handled, you need a clear path to complain.

What the policy says: “you may do so by writing to the following email id: care@easemytrip.com.”

What the law requires: You must have a Grievance Officer and a clear process. If the company doesn’t fix the issue, you have the right to take them to the Data Protection Board of India.

The problem: Hiding the privacy complaints in the general “customer care” inbox is a recipe for a fine. The DPDP Act expects a much more professional and dedicated response system.

Section 16 — Cross-Border Data Transfer ⚠️

What the policy says: Data is processed in India and “other jurisdictions where a third party… may process the data.”

The problem: The Indian government will soon release a “Negative List” of countries where data cannot be sent. EaseMyTrip’s policy is a bit too broad here. They need to specify that they follow Government of India restrictions on where your data travels.

Risk Assessment

CategoryRisk LevelPotential Impact
Consent ValidityHighBundled consent (Section 6) is the easiest thing for the Board to penalize.
Data RetentionHighKeeping sensitive IDs like Passports indefinitely is a major liability.
Grievance RedressalMediumLack of a dedicated DPDP officer makes responding to legal notices harder.
Compliance FinesHighMaximum penalty of ₹250 Crore for failing to protect data.

Recommendations

If you’re a business owner looking at EaseMyTrip’s policy to learn what to do (or what not to do), here are 3 quick takeaways:

  1. Stop “Bundling”: Don’t make users agree to “Marketing Emails” just to buy a product. Use separate checkboxes.
  2. Define “End Dates”: Instead of saying “as long as necessary,” tell your users “we delete your KYC docs 6 months after your trip is completed.”
  3. Appoint an Officer: Even if you’re a small startup, designate one person as your Grievance Officer and put their direct email in your policy. It shows the government you’re trying.

Fix these compliance gaps today.

Book 1:1 Consultation >
Book clarity call