NearSeal

2026-09-25

A 2026 investigation found visa applicants' data sent over open email. What happens to your passport scan and bank statements?

On May 28, 2026, Lighthouse Reports published a year-long investigation, co-published with 14 outlets including Semafor, Le Monde, Politico, and the Indian Express, into VFS Global — the private contractor that runs the visa-application front end for 71 governments, including the US State Department, the UK Home Office, the entire Schengen zone, Canada, and Australia. If you've applied for one of those visas in the last decade, VFS Global is very likely who actually took your passport scan, your bank statements, and your fingerprints, in a storefront office nowhere near an embassy. The investigation — built on more than 150 internal EU inspection reports from 20 member states between 2020 and 2025, obtained through freedom-of-information requests — found what independent experts called "manifestly serious violations" of the GDPR in how that contractor actually handles what it collects.

What the EU's own inspectors found

Two of the specific findings go straight to the question this post is about. Luxembourg's 2023 review of its own VFS-run operations found that biometric information was being transmitted through open emails whenever errors occurred during collection or transmission — plain, unencrypted email, used as the fallback path the moment the normal system hiccupped. Separately, inspectors documented that applicants' biometric data and supporting documents were "stored on unencrypted compact discs and transferred insecurely between VFS offices and consulates," with old discs holding sensitive applicant information never destroyed despite shredders being available on-site. A 2025 Hungarian consulate report added a third: applicant data more than a month old was still accessible in the VFS system in New Delhi, roughly three weeks past the Schengen Code's own seven-day deletion mandate. VFS Global processed roughly 26 million people in 2024 alone, across more than 160 countries — this isn't a small vendor's paperwork problem.

What a visa application actually asks you to hand over

Most non-immigrant visa applications bundle a specific, high-value stack into one submission: your passport's bio page, several months of bank statements or other proof of funds, an employer or leave letter, sometimes a sponsor's invitation letter or property documents — plus, taken on-site, your fingerprints and a photograph. The financial and identity documents in that stack are files that exist on your own device before they ever reach a VFS counter or portal: a scanned passport page, an exported bank-statement PDF, a signed letter saved to Downloads. Those are the ones this post is about — not the fingerprint scan itself, which VFS collects directly and which no browser tool on your side ever touches.

Where a visa applicant's documents travel Your device, before submitting Passport scan, bank statement PDF, sponsor letter in Downloads → yours to encrypt: NearSeal, in the browser, before it becomes an upload or attachment VFS Global's own handling EU inspectors found open, unencrypted email used on errors, unencrypted CDs → out of reach on submit: your own encryption choice never touches their copy The destination consulate Forwarded onward once VFS finishes processing — a separate system again → outside both: your control and, per the reports, VFS's own stated safeguards Only the left column is still under your control by the time you're reading this
The same passport scan and bank statement travel through three systems on their way to a consulate — and only the first one is still yours to protect.

Two different problems, and encryption only touches one

The EU's inspection reports describe a problem encryption on your end cannot fix: how a government contractor's own staff move data between its offices and a consulate. That's their infrastructure, their CDs, their fallback email process during an outage — a browser-based tool running on your laptop has no way to reach a process that happens entirely on VFS Global's side after you've already handed the file over. The problem NearSeal can actually reach is narrower and sits earlier: the plaintext scan and PDF sitting on your own device, in your own backups, and in your own Sent folder if you emailed a document to a sponsor or agent before or alongside the official submission. That copy is entirely yours, for as long as you keep it, regardless of what VFS Global does with the one it received.

What encrypting your own copy actually fixes

NearSeal runs entirely in the browser — nothing uploads anywhere — so encrypting the passport scan and bank-statement PDF sitting in your Downloads folder costs nothing and removes one plaintext copy of both from your own hard drive, your own backups, and any cloud-sync folder you keep for your records. If a visa agent, sponsor, or relative needs a document by email rather than through the official portal, that only protects anything if the passphrase travels a separate way — a text or a phone call, never the same email thread as the file. And because the finished container still keeps the original filename in its header, plainly readable even though the contents aren't, a file named something like bank_statement_march2026.pdf.nearseal still announces what it is; rename it to something unremarkable first, or use the opt-in age-encryption.org format available in the same tool, which carries no filename field at all.

What it honestly can't do

Encryption can't make VFS Global's own portal or counter accept a file it can't read: whatever form actually takes your passport scan or bank statement needs the real document to process your application, so the copy you formally submit has to exist in the clear at the moment they receive it. Nothing about NearSeal changes what happens to that copy once it's in VFS Global's system — the open-email fallback and the unencrypted CDs the EU's inspectors documented are failures in their process, not yours, and no tool running in your browser reaches a server you don't control. It also doesn't retroactively protect any document you've already submitted for a past application, and, like every file NearSeal seals, there is no passphrase recovery of any kind — worth weighing before encrypting a bank statement or sponsor letter you might need to reopen for the next application in a year or two.

Where NearSeal fits

Roughly 26 million people went through VFS Global's process in 2024 alone, and the EU's own inspectors — not outside critics — are the ones who found open email and unencrypted discs behind the counter. NearSeal doesn't change anything about that back end, and this post won't claim it does. What it changes is the part still sitting on your side of the transaction: the passport scan and bank statement don't have to exist in plaintext on your own device for one minute longer than it takes to attach them. AES-256-GCM, a passphrase-derived key via PBKDF2-SHA256 at 220 iterations, entirely client-side, for the copy that's still yours to protect.