iOS + Android

Technically strong. A few seconds for the employee.

MesaiGo Mobile presents device enrollment, access, and attendance outcomes through a focused, accessible, and explainable flow.

P-256Device credential
BLEStandard
UWBHigh Assurance
OSLocal user approval
Mobile trust chain

The credential is created on the phone, and the private key never leaves it.

Hardware-backed Android Keystore and iOS Secure Enclave foundations are managed through device enrollment, verification, key rotation, revocation, and device-replacement lifecycles.

01

Device enrollment

Establishes the employee, organization, and device binding under a controlled flow.

02

Correct-point discovery

The app selects the correct entry point and gateway.

03

Transaction signing

The fresh attempt context is signed with the device private key.

04

Verified result

The user sees only the final result bound to the server and corresponding attempt.

Privacy and permissions

Every permission is used only for its stated purpose.

Bluetooth communicates with a nearby MesaiGo gateway; the camera scans MesaiGo QR contexts; network access supports device enrollment and server decisions. Attendance decisions are not based on GPS coordinates.

01

No biometric data

Local operating-system authentication templates are never transferred to MesaiGo.

02

No background GPS

Employees are not continuously location-tracked.

03

Employee self-service

Employees can view their own attendance events, schedules, and correction workflows.

Store distribution

One security contract across iOS and Android.

Store links, platform compatibility, privacy labels, and release notes are published with the corresponding release package.

MesaiGo mobile app icon
MesaiGo MobileiPhone · Android

Store badges appear only after verified product-page URLs are bound to the release configuration.

Experience MesaiGo on iOS and Android.

Store links and download QR codes are published with the release package.