Reviews · 6 min read

Nomad eSIM Terms: Refund Named 3 Times in Section 4

edit Nadezhda Semenova · updated 7 Sept 2026

This is not a Nomad eSIM review built from impressions. It reads the Nomad eSIM Terms and Conditions the same way this site read Saily’s contract. You accept this document with a click, the same as you would Saily’s. This page reports what it says, with the date it was read.

The source is Nomad’s own Terms and Conditions, headed on the page itself “Nomad eSIM Terms and Conditions Explained.” It carries a version marker at the top: “Last Updated: March 19, 2026.” We read it on 3 September 2026, about five and a half months after that date.

The saved copy runs 36,316 characters, counted with Python’s len() on the file decoded as UTF-8 text — not wc -c, which counts bytes and runs higher because the file carries non-ASCII characters (curly quotes, em dashes) that take more than one byte each. That is not the shortest of the four eSIM contracts on file here. Ubigi’s runs 29,524 characters and Holafly’s 30,447. Saily’s runs 93,052 — the same figure our reading of Saily’s contract states, more than double Nomad’s. Nomad sits between the two pairs: longer than Holafly and Ubigi, less than half the length of Saily. Character count alone does not answer the question this page asks. Refund-clause density does.

Four contracts, measured two ways

The Nomad Returns and Refunds Policy names “refund” three times, and all three sit in the section heading and clause 4.2: once in the heading itself, twice inside 4.2 — “may request a refund” and “eligible for a refund.” Clause 4.3 names no refund at all. That total, three, is fewer than Holafly’s 11 and Ubigi’s 8, counted the same way, in files checked on 3 September 2026.

Two counts make that comparison, and you can redo both independently. The first is file length in characters, not bytes — the files carry non-ASCII characters that inflate a byte count:

The second is a case-insensitive, word-boundary regex search for “refund” and its forms: refund, refunds, refunded. It runs with Python’s re.findall(r"\brefund\w*\b", text, re.IGNORECASE) against the full text of each saved file. That search returns 4 hits in Nomad’s file, 11 in Holafly’s, and 10 in Ubigi’s.

Those totals need one adjustment before they compare fairly. In Nomad’s file, only 3 of the 4 hits sit inside the contract’s own Returns and Refunds Policy — one in the section heading, two inside clause 4.2. Clause 4.3 carries none. The fourth of the four whole-document hits sits in an unrelated clause, section 13.2, about the Apple or Google App Store refunding the price of the app itself, not the eSIM plan. In Ubigi’s file, 8 of the 10 hits are the noun “refund” or “refunds”; the other 2 are the verb form “refunded,” describing the same non-refundability rule a neighboring noun mention already states. Scoped to each contract’s own refund terms, the count is Nomad 3, Holafly 11, Ubigi 8 — under a third of Holafly’s and under half of Ubigi’s.

Section 4 of the Nomad eSIM Terms and Conditions is titled Returns and Refunds Policy. It is one of 18 numbered sections in the document, and it runs exactly three clauses: 4.1, 4.2, 4.3.

What fewer refund mentions means, and what it doesn’t

Fewer refund mentions means fewer cases Nomad settles in advance, not a better or worse contract. A refund clause is a list of pre-agreed outcomes. It says what happens if you cancel before you use the service, what happens if the service fails, who decides, and how long you wait. Holafly’s 11 mentions and Ubigi’s 8 spread across more pre-agreed outcomes than Nomad’s 3.

That does not make Nomad’s contract friendlier or harsher toward you if you run into a problem it does not name. It makes that outcome a matter of what Nomad’s support team decides at the time, not something written down in advance for either side to point to.

The document’s own final line adds a second, unrelated fact worth reading alongside the first: "Parts of the Terms and Conditions were generated by Termly’s Terms and Conditions Generator." Nomad’s contract names a generator for at least part of its own text — a credit that Saily’s longer, more bespoke contract does not carry anywhere. Neither fact, the short refund section or the generator credit, says whether Nomad’s actual support practice runs generously in the cases it leaves open for you. The Nomad eSIM Terms and Conditions settle three refund cases and leave the rest to Nomad’s own judgment. This page reads the document for you. It does not test the support team on your behalf.

Refund before installation, not after

The Nomad eSIM refund policy splits eligibility into exactly two windows. Before you install and activate the eSIM, a refund is available by choice. After activation, it is available only for a known technical problem the clause pins on Nomad. Clause 4.2, quoted in full from the saved copy:

"Customers may request a refund or a change prior to the installation and activation of the E-sim or there is a known technical problem originating from NOMAD after activation of E-sim. Please refer to your plan’s description (including associated terms and conditions) to check whether your plan is eligible for a refund."

Clause 4.1 sets the other half of the timing: "Customers will be charged upon the purchase of E-sim." The charge lands at purchase, before installation — the same window clause 4.2 leaves open for a refund by choice, with no reason required.

The clause does not say who decides that a technical problem is “known,” or what evidence establishes that the problem originates from Nomad rather than a partner network or your device. No definition of “known” appears anywhere else in the document — checked by search across the full text, not assumed. Clause 4.3 routes complaints to Nomad’s own Help Center inside the app, or to an email address, and names no other party. Nomad’s own support team is the only body the text names to make that call.

The download step tied to the same clause

Clause 2.2.3 requires the same download that, once complete, ends the window clause 4.2 opens for a refund by choice:

"On purchase, Customers must download the eSIM onto the Customer device in order for the data plans to be configured as per your order."

Clause 2.2.4 completes the sequence — download first, then activation:

"To implement Service, the Customer must first download the eSIM, then activate the data plan attached to the eSIM in order for service to commence."

Downloading is not optional paperwork here. It is the step that configures the plan you bought, and it is also the step clause 4.2 uses to mark the end of a refund by choice. If you install the profile to confirm it works, you have, by that same act, moved past the window where a refund does not require a known, Nomad-side fault.

This shape is not unique to Nomad’s document. A prepaid eSIM contract read closely enough tends to show the same pattern: the technical step needed to use the product doubles as the step that closes the easy refund path. What Holafly’s or Ubigi’s own terms do with that same shape is a separate reading, done at the same depth, on its own page. That reading exists: refund triggers, identity checks and the word “unlimited” compared across all four contracts in one place. This project reads every source contract under one editorial policy; our reading of Saily’s contract applies the same method to a different clause.

One more clause is worth naming for contrast. Nomad’s governing-law clause, 7.1, sets disputes under “the laws of the State of California, USA,” and names no arbitration clause or class-action waiver anywhere across the 18-section document — checked by search, not assumed. That question is settled in advance. If you hit a case clause 4.2 does not name outright — a problem you can’t prove originates from Nomad, say, or one your plan’s own terms don’t cover — the refund question is not settled for you before you ask.

Sources cited only — expert review pending. For individualized advice, consult a licensed professional.