AVGEEK
Digi Yatra’s design choices around efficiency, privacy and consent
Suresh Khadakbhavi explains Digi Yatra’s origins, identity architecture and governance, discussing passenger choice, airport processing and the prospects for airline integrations and international interoperability.
The conversation
A deep dive into the tech, governance, and everyday friction of modern air travel with the person who helped turn a fringe idea into India’s biometric travel backbone. Suresh Khadakbhavi walks us from a muddy auto ride before his BIAL interview to the pilot with Jet Airways that proved passenger-first biometrics could scale nationally and explains how Digi Yatra is designed to enable seamless journeys without becoming a surveillance system.
What you’ll hear in this episode
• A vivid origin story of how aviation and Suresh found each other, including a memorable muddy-ride interview anecdote that ended with an emergency wardrobe buy.
• The spark inside BIAL’s Innovation Lab that birthed the “walk-through-all-touchpoints-with-no-one-stopping-you” idea and how rapid passenger feedback at BLR turned a developer’s dream into a national program.
• How the 2017 Jet Airways pilot validated core assumptions, which insights convinced stakeholders to scale, and the unexpected operational learnings from working with airlines.
• A clear, technical separation between Digi Yatra’s decentralized self‑sovereign identity model and centralized surveillance systems, plus exactly what data touches external servers during a Digi Yatra transaction.
• The governance and technical design choices made to prevent mission creep and ensure passenger privacy.
• Practical reasons why adoption feels voluntary yet operationally nudged, and how airports balance efficiency with genuine choice.
• Measurable operational wins, including reduced processing times at entry gates and the downstream economics that happier, faster passengers bring to airports and retail.
• The role of partner integrations—airlines, OTAs, and apps—in making Digi Yatra the travel stack for India and the roadmap to gate-level boarding automation.
• International ambitions, collaboration with IATA’s One‑ID work, and the vision for Digi Yatra to interoperate with EU credentials and other global systems for borderless travel.
• Near-term product roadmap highlights: AI-driven multilingual chatbots, anti-spoofing measures, expanded onboarding flows, and pilots beyond airports into hotels and other travel touchpoints.
Vishal Mehra - @vishal1mehra
Key Takeaways
- Airport processing can be redesigned before terminal buildings are expanded; Digi Yatra began as a throughput challenge.
- The Foundation describes an on-device identity wallet rather than a central biometric database.
- Credential data and flight data can be transmitted temporarily to an airport; decentralised architecture does not mean zero processing outside the phone.
- The claimed 24-hour deletion window and third-party audit process are material, testable safeguards—not grounds for declaring risk impossible.
- Voluntary adoption must be assessed in the actual airport environment, including viable non-app queues.
- Cross-border facial processing requires more than a software update: passports, border authorities and international agreements matter.
- Multilingual design and genuinely accessible user journeys are part of the programme’s public-value case.
Editorial analysis
Digi Yatra as a passenger-processing infrastructure layer
The origin story is a practical airport-capacity problem, not a fascination with biometrics for their own sake. Suresh Khadakbhavi recalls Bangalore airport struggling to accommodate rapid passenger growth without continually building more terminal space. He describes a 2015 idea for a traveller to move from the airport entrance toward the aircraft without repeated document checks, followed by pilot trials with Jet Airways in 2017. This history illuminates the product thesis: throughput can improve when identity checks are redesigned, even without a larger building. The dates and implementation history are given as his recollection.
Trust, consent and the limits of airport biometrics
The interview is most important where it tests that convenience against civil liberties. The host challenges the Foundation on centralised biometric storage, wider surveillance, external hosting, data retention and whether passengers can realistically refuse enrolment when physical gates appear to favour users. Khadakbhavi describes a decentralised credential wallet on the passenger’s device, selective sharing with the departure airport, infrastructure hosted in India and destruction of local airport data within 24 hours after departure. Government statements published in 2023 and 2024 describe a similar design and audit model. Crucially, a system architecture claim is not proof that every airport and vendor has always implemented it without error.
Operational implementation across airlines and airports
The pressure point is voluntariness. Khadakbhavi says users can enrol and delete credentials on their own device and that airports allocate gates between biometric and non-biometric passengers. The unresolved question is empirical: what are actual queue times, does a traveller receive equivalent access without the app, and are alternative identity checks reliably available? Genuine opt-in is a service-design and governance outcome, not simply a line in the terms of use.
The travel-stack opportunity and its boundaries
The later proposals—boarding-gate integration, electronic passports, use by foreign travellers, hotel identity verification and additional Indian-language interfaces—suggest that Digi Yatra could grow into a broader credential ecosystem. They also enlarge the surface for consent, commercial reuse and regulatory accountability. The interview’s proposed timelines are ambitions, not completed deployments. Each new use case would need fresh disclosure of participating entities, verification method, consent scope, retention and remedy for error.
Questions & answers
Why was Digi Yatra conceived?
Khadakbhavi says airport growth prompted a search for more efficient passenger-processing methods; an early pilot was run with Jet Airways.
Where is the traveller’s personal information held?
He describes an on-phone wallet with temporary disclosure to the airport, not a central catalogue of every enrolled passenger.
When does airport-held data disappear?
He states a 24-hour purge following scheduled departure and cites audits; independent operating compliance is not established by the interview alone.
Is Digi Yatra genuinely optional?
He says yes and describes airport gate allocation, while the host raises whether non-participants experience unfair queues.
Can foreign passengers use it for border crossing?
Electronic-passport and cross-border use were plans under discussion, dependent on approvals and interoperability.
Sources & attribution
Original conversation: The Indian AvGeek — Episode 52. Originally published 19 October 2025.
Historical context: This editorial analysis reports and interprets positions from the original 2025 conversation. Estimates, forecasts, commercial relationships and policy statements must not be mistaken for current conditions or independent verification as of October 2026.
Editorial Q&A: Questions and answers are explanatory editorial paraphrases, not verbatim dialogue.
Privacy qualification: Operational and privacy-related claims about biometric processing should be checked against the then-current program documentation and applicable policy; the interview alone is not a compliance audit.