Pillar
Privacy

What Data Is in a Boarding Pass Barcode? Privacy Guide

Boarding pass barcodes can expose your name, booking locator, route, flight, seat, and other data. Learn what they contain and how to share tickets safely.

5 min readAug 11, 2026Updated Sep 15, 2026
A boarding pass rests inside an amber shield as scanning beams bounce away

A boarding pass barcode is not just a picture that opens a gate. It is a structured travel message that can contain your name, booking locator, route, flight details, seat, and other operational data.

Treat the code and the visible booking reference as sensitive. This guide explains what an IATA Bar Coded Boarding Pass can contain, why its standard fields generally do not represent your full passenger name record, how carrier-defined fields can vary, and how to redact a ticket before sharing it.

The practical answer

Do not post an unedited boarding pass. If you must share an image, completely cover the entire barcode and the visible booking locator, then export a new flattened image and inspect that final copy. A digital signature can prove integrity, but it does not make the barcode confidential.

What a boarding pass barcode can contain

A standard BCBP normally carries a booking locator plus operational boarding fields. Conditional and carrier-defined fields vary by airline, route, and check-in context.

Identity and booking

The passenger name and booking reference, also called the record locator, are core identifiers commonly carried in the message.

Journey

Origin, destination, airline, flight number, and the flight date connect the pass to a specific journey.

Boarding

Cabin, seat, check-in sequence, and passenger status help airline and airport systems process boarding.

Conditional data

Baggage tags, frequent-flyer details, document checks, fast-track eligibility, and airline-only fields may appear when applicable.

IATA's Common Use standards page describes the standard for boarding-pass data encoded in a machine-readable two-dimensional barcode.

A standard BCBP is usually not your full PNR

A booking locator inside the barcode can point to a reservation. A standard BCBP normally carries that locator plus operational boarding fields, not a copy of the complete passenger name record. Carriers can add issuer-specific fields, so do not assume every barcode has identical scope. The standard payload focuses on the fields needed to identify and process a passenger at check-in, security, and boarding.

The United Kingdom government's PNR guidance explains that a full passenger name record may also include travel dates and itinerary, ticket information, contact details, the travel agent, payment information, seat number, and baggage information. What an airline knows and stores can therefore be broader than what the boarding-pass barcode exposes.

Why the locator still matters

The barcode does not need to contain the full reservation to create risk. A visible name and booking locator can be enough to reveal or unlock more information through an airline's booking-management flow, or to attempt changes to the booking.

Encoded, readable, and signed are different things

A BCBP is encoded so compatible airport systems can parse it consistently. Encoding changes how the message is represented. It is not the same as encrypting the data or hiding it from anyone with suitable decoding software.

Readable payload

Mandatory, conditional, and airline-specific fields remain part of the structured barcode message and can be read by compatible systems.

Optional signature

A security field may contain a digital signature that lets a verifier detect changes. It protects integrity, not confidentiality.

How to redact a boarding pass safely

Taiwan's national Administration for Cyber Security warns against sharing ticket images and recommends completely obscuring barcodes when sharing cannot be avoided. Use this stricter workflow for both paper and digital boarding passes.

1

Prefer sharing no ticket image

A destination photo or plain itinerary text communicates the trip without exposing a credential. This is the safest option.
2

Cover the code and locator completely

Place a solid opaque block over the full barcode, including its quiet margins, and over every visible booking reference. Do not rely on a crop that leaves part of the code or locator visible.
3

Flatten the redaction

Export the edited result as a new image with no editable markup layers. A removable shape or annotation is not a reliable redaction.
4

Inspect the exported copy

Open the exact file you plan to send. Check thumbnails, reflections, duplicate codes, text below the barcode, and any second page before sharing.

The same principle applies when asking for technical help. NeatPass explains its optional attachment redaction and the remaining review step in NeatPass bug-report privacy guidance.

Apple Wallet sharing is controlled by the issuer

Apple's Wallet sharing instructions say that only some tickets and passes can be shared. If the Share button is missing, the airline or other issuer has not enabled pass sharing in Wallet. Apple's Wallet privacy notice also explains that adding a pass can associate information shown on it with your Apple Account for display and management. That processing is separate from NeatPass's signing service.

What NeatPass changes, and what it preserves

NeatPass is designed to process ticket documents and barcode content on the iPhone. A converted Wallet pass preserves the sensitive barcode payload because the scanner needs the same data as the source. Moving it into Wallet does not make that payload safe to publish.

NeatPass keeps the source document alongside the pass. The NeatPass data-management guide explains the local library and deletion controls.

The exact network boundary

Ticket and barcode content is processed locally. For a valid Wallet pass, the signing service receives manifest.json containing cryptographic hashes of the pass files, not the ticket file. The service also processes a pseudonymous App Attest identifier plus IP address and technical request metadata for security. The current NeatPass privacy policy covers retention and legal details.

Import and processing can work without a network connection, as described in NeatPass offline mode. Adding the finished pass to Wallet still requires the brief signing request described above.

Keep sensitive boarding passes organized on your iPhone

NeatPass makes it easy to convert any ticket, pass, or loyalty card to Apple Wallet.

Common questions

Store the pass without publishing its data

Download

Treat the barcode like part of the ticket

A boarding pass barcode is compact, not harmless. Keep it private, separate its operational fields from the broader PNR, and use an opaque, flattened redaction whenever an image must leave your device.

Continue with related guides

Ready to migrate your cards?

NeatPass makes it easy to convert any ticket, pass, or loyalty card to Apple Wallet.