Last updated
What is purpose and functionality of Abaxx Verifier?
Built on the proprietary ID++ protocol, Abaxx Verifier turns internal employee credentials into external execution power across the MarketOS™ transaction productivity suite, automating tamper-proof trust within and between organizations without centralizing sensitive data.
Where is the data associated with Verifier stored, and how is it secured?
When you create an identity or alias using Verifier, your private identity data including a unique encrypted identifier and cryptographic key is securely stored on your device within the biometric security chip.
How do I recover access if my device is lost/damaged?
Install the application and log back in to regain access to your Abaxx Verifier account.
Where can I find my Abaxx Verifier Aliases?
Navigate to the “Aliases” section within the application to view or create new Aliases.
Can I update my registered email address?
Yes. Verifier uses AbaxxOne to manage users. Your tenant admin can update your user email address in AbaxxOne. Contact your tenant admin to request the change.
What happens to my Abaxx Verifier account if I delete the App from my phone?
Uninstalling the application does not delete your account, credentials, or aliases. Reinstall the app and log back in to regain access.
Who owns and develops Verifier, and what are the licensing agreements?
Abaxx Technologies Inc. owns and develops Abaxx Verifier. Enterprise licensing agreements are available for institutional use. Open-source components adhere to licensing terms outlined in our Terms of Service. Abaxx maintains limited access to audit data strictly for regulatory compliance purposes.
What type of encryption does Abaxx Verifier use to secure my data?
Abaxx Verifier combines established cryptography with the security features built into your device.
-
Cryptographic sign-in approvals: Supported mobile devices use ECDSA P-256 digital signatures with SHA-256 to approve sign-in requests.
-
Hardware-protected approval keys: Private signing keys are generated and retained within Apple’s Secure Enclave or Android’s hardware-backed Keystore on compatible devices.
-
Device authentication: Protected operations use your device’s supported biometric authentication or passcode.
-
Protected local storage: When device security is available and enabled, the app uses a protected vault for saved sign-in information.
Security features depend on your device, platform, and settings. The browser version uses separate storage protections, including AES-256-GCM encryption, and does not provide the same hardware-backed protection as the native mobile apps.
Where can I get more help?
For questions not addressed in this FAQ, please contact our support team at support@abaxx.tech .