Current figures
Not yet published. The first figures will appear after at least four weeks of use and at least twenty detected crossings, whichever comes later, and will be given per platform. Android is marked "not yet measured" until it has its own crossings. Until then, treat detection as a convenience that still needs your confirmation, which is how the app treats it too: a detected crossing counts nothing until someone confirms it.
What is counted
Every crossing the phone detects is written to a log on the account, encrypted like the trips themselves, and updated when a person decides what it was:
| Term | Meaning |
|---|---|
| Detection | The phone concluded that the person entered a country and wrote a pending trip, or attached its fixes to a trip already recorded for that arrival. |
| Confirmed as detected | Someone confirmed the pending trip without changing the country or the arrival time. |
| Confirmed with changes | Someone confirmed it after changing the country or moving the arrival by at least a minute. The change in minutes is kept; its median is reported. |
| Matched a recorded trip | The trip had already been typed or scanned when the crossing was detected; the detector agreed with it. |
| Merged into a recorded trip | A trip typed or scanned afterwards for the same arrival took the pending detection over. |
| Not a crossing | Someone removed the detection: it was wrong. |
| Still to confirm | Nobody has decided yet. Left out of the rates. |
| Missed crossing | A trip recorded by hand or scan that enters a country while detection was switched on, with no detection for that country within twelve hours of its arrival. Trips inside the United States are left out (state crossings follow their own rules), as are trips whose origin and destination are the same country. |
| Precision | Of the detections someone decided on, the share that were real crossings (confirmed, with or without changes, matched or merged). |
| Recall | Of the real crossings (those detections plus the missed ones), the share the phone caught. |
| Time to record | Median minutes from the first fix in the new country to the entry reaching the account. |
How it is measured
- On the device, from real travel. Nothing is simulated. The figures come from the family accounts that use detection day to day, on their own phones, and later from any account whose owner chooses to share counts.
- Counts only leave the account. The log never leaves the account's encrypted data. The owner or an assistant sees "Accuracy on this account" in the app (Profile → Border crossing detection) and can copy the counts. What is published here is the sum of counts shared with us: numbers, platforms and dates of the window; never a trip, a country or a time.
- Per platform. iPhone and Android use different location services and are reported separately.
- Window. The in-app figures cover the last ninety days. Published figures name their window and the number of phones.
- Honest about the gaps. A crossing the phone misses while it is switched off, out of battery or without permission is not a missed crossing in these figures, because the phone could not have seen it; the figures say how many days detection was on. Entries that cannot be read are counted and the in-app figures say so.
How to read the figures
They will come from a small number of people who travel often. A high precision on twenty crossings is encouraging, not a guarantee; a missed crossing on a route you take weekly matters more to you than the average. Detection is there to catch what you forgot to record; your trips, your documents and your confirmation remain the record. Atrium counts days from that record and does not decide where you are resident.
See also the security page for what the phone sends and when.