Android and iOS: the current conclusion
The brand-facing application page makes two different descriptions: an Android APK and browser-based access on iOS. Neither description establishes a reviewed native binary. A page title saying “official app” is an assertion, not a developer identity.
Platform-by-platform assessment
| Platform / product | What the page describes | What was independently established |
|---|---|---|
| Android | APK availability is asserted | No file, package identity or signing certificate was authenticated |
| iPhone / iPad | Browser access with a home-screen option | No native App Store listing was authenticated |
| Mobile web | A browser interface | Page description only; no logged-in device test |
An APK can be a native program or a wrapper around web content. A home-screen icon can simply open a browser experience. The appearance is not enough to determine which product is actually present or what permissions it has.
What an Android assessment would require
A useful assessment identifies the exact package, developer, release version, distribution source and signing identity. It then describes what was tested: permissions, network behaviour or another defined property. “Android supported” and “security tested” are very different claims.
No executable was downloaded in this investigation. This page therefore offers no file and makes no malware-free assurance. A security conclusion should be tied to a specific version, not carried indefinitely by the brand name.
What an iPhone assessment would require
To describe a native product, identify its precise store listing, developer and bundle identity. Browser access does not supply those identifiers. Similar names returned by a store-indexed search should be excluded unless their connection to the service can be authenticated.
The present evidence supports an attributed description of browser access, not a conclusion that a native iOS app exists. It also does not prove that one cannot exist in another distribution region.
Domain identity comes first
The Safety article distinguishes the licence-listed domain from other brand-facing pages. A download destination needs its own authentication. A site using familiar branding should not inherit a register match for a different hostname.
Review boundary
No installation workarounds, mirrors or executables are supplied. Platform availability, software provenance, legal permission and security behaviour are separate questions. The remaining tests are listed in the claim record; the published page describes only the evidence actually obtained.