How this data is gathered and checked

Every eligibility verdict on this site carries a source and a date, and nothing unverified is published. This is how that works.

One dataset, versioned in the open

The eligibility data lives in a single file, versioned in source control. Its history is the provenance trail: every change to a verdict is a recorded edit, with who changed it and when. The same dataset feeds this site and the Momo app, so the two never disagree.

How a verdict is made

Each claim names one provider and one account type, and lands on one of three verdicts: opens, opens with strings, or skip. The verdict is backed by a source, a public policy, an application flow, or a direct statement from the provider, and stamped with the date it was last checked. A confidence level records how firm the evidence is.

Shown honestly, marked where unconfirmed

Every verdict is shown with its standing. A verdict drawn from a credible source is published and then confirmed against a primary source shortly after; a verdict that rests only on a thin lead is still shown, but marked "not yet verified" so you are never misled about where it stands. Marked verdicts are held back from the page's structured data, and a page is listed in search and the sitemap only once it carries at least one verified verdict. A verdict presented as settled when it is only a guess costs more trust than an honest "not yet checked".

Dates are real

The last-checked date you see on a page is the same date the structured data reports as the modified date. It reflects when the underlying claim was verified, not when the site was rebuilt. If a date looks old, treat the claim as due a recheck and confirm it.

What this is not

This is an information service, not advice and not a regulated recommendation. Acceptance policies change without notice and your own facts may differ from the general case. The data is a map of where to start, not a ruling on your situation.