Effective Date: April 30, 2026
This Privacy Policy describes how Vizualkei LLC ("we", "us", "our") handles personal data in connection with the Neuma mobile application ("the App"). It applies only to the App and not to any third-party services or websites.
Neuma is a privacy-protecting identification system. All identification work happens on your device. The App does not transmit any personally identifiable information (PII) to Neuma servers, partner servers, or any other server. The only thing the App may transmit, after a verification completes, is a zero-knowledge cryptographic proof of the verification outcome, and that proof is sent only to the Neuma server for verification. The proof contains no PII, cannot be reversed to reveal the underlying data, and is cryptographically bound to the verification session in which it was produced.
When you initiate a verification, the App requests the following org.iso.18013.5.1 data elements from your Google Wallet, with explicit per-request consent shown by the wallet itself:
given_name — your first name. Used as the ground-truth value the App compares against your typed input during the optional knowledge-based challenge.family_name — your last name. Used as the ground-truth value the App compares against your typed input during the optional knowledge-based challenge.birth_date — your date of birth. Used as the ground-truth value the App compares against your typed input during the optional knowledge-based challenge.portrait — your portrait image. Used as the reference image the App compares against your live face capture for biometric verification.The App also receives the cryptographically signed ISO/IEC 18013-5 device response that backs these values, used solely for on-device verification.
The App uses your device's camera to capture a live image of your face. The capture is used only to compare against your mDL portrait.
If, after the biometric step, the App challenges you to type your first name, last name, or date of birth, the values you type are held in the App's working memory only for the duration of the comparison with the corresponding mDL fields. They are never written to persistent storage, never transmitted, never hashed, and never used for any other purpose.
The four mDL elements, the live face capture, and any typed challenge input are used for one purpose: privacy-protecting identification. The App:
We do not use any of this data for advertising, profiling, analytics, or any purpose other than the verification session itself. We do not transmit any of the underlying PII to any server.
We do not retain disclosed mDL values, the device response, the live face image, or anything you type in the challenge step. The data is held in the App's working memory (and, transiently, in the App's local working storage in the case of the live face image) only for the duration of the verification session and is released immediately after the comparison completes or when the App is closed.
No PII or PII-derived data is written to long-lived storage, sent to any server, hashed, or shared with third parties by the App.
All biometric and mDL data processing happen on the user's device. The cryptographic verification of the mDL device response uses the California DMV's IACA root certificate, which is bundled with the App at install time. The face-to-portrait biometric comparison and the optional knowledge-based challenge comparison are likewise performed entirely on the device. The zero-knowledge proof of the verification outcome is also computed locally on the device; no PII is sent off-device at any stage of this pipeline. None of these steps require a network call.
Neuma works exclusively with users of our well-known partners — that is, people who have already signed up with one of our partners to use that partner's service. The App is not a standalone identity provider; you arrive at Neuma because the partner you have an existing account with has asked you to verify, in a privacy-protecting way, that you are the same person who holds that account.
When a verification completes, the App transmits the resulting zero-knowledge cryptographic proof only to the Neuma server (operated by Vizualkei) for verification. The proof attests to the result (for example, that the on-device biometric and knowledge-based checks succeeded) without containing your name, date of birth, portrait, mDL data, or any other PII, and it cannot be reversed to derive any of that data. The proof is cryptographically bound to the partner's specific request so it cannot be replayed to or accepted by a different session. The Neuma server verifies the proof and reports the verification outcome to the partner so the partner can complete its own user flow. No user PII is sent to the Neuma server or to the partner through this process. How the partner manages the account that initiated the verification is governed by the partner's own privacy policy, not by this Policy.
Because the App does not retain or transmit personal data, there is no Vizualkei-held record to access, export, correct, or delete. You can:
If, in the future, the App is updated to collect, retain, or transmit personal data, this Policy will be updated and the change will be communicated through the App and at the URL where this Policy is hosted.
The App imposes no age restrictions. Neuma performs identity verification only and does not assess, infer, or report the user's age. Anyone who holds an eligible mobile driver license in their wallet may use the App to authenticate themselves to a partner service.
We may update this Policy from time to time. The "Effective Date" at the top of this page will be updated and the current version posted at the same URL.
Questions about this Policy can be sent to:
Email: dev@vizualkei.io
Website: https://www.vizualkei.io