This is the full text published in the Phase 7 package. Effective dates, responsible contacts and contract-specific parameters are maintained in the corresponding release and deployment records.
Audience and scope
This notice is for a person enrolling a palm at a relying organization. The deployed notice must identify the responsible entity, capture locations and contact route. Marketing-website behavior is explained in a separate website notice.
What information is processed?
Depending on the deployment, RGB/IR images support checks and extraction; the system creates a reference and records identity, binding, session, device and results. eID/SSO/ShareInfo attributes are received only within authorized scope. The notice must name the actual categories, not merely say "biometrics".
Purposes and basis
The responsible entity explains whether use concerns patient reception, access, exams or another workflow. The processing basis is established in advance; where consent is used, it is separately requested and recorded. Presenting a palm for one service is not consent to every other service.
Choice and consequences
Explain the non-palm alternative and the concrete effect of not enrolling, withdrawing consent or deleting a reference. A default notice must not coerce biometric use. Children, supported users and representatives require an approved pathway appropriate to their circumstances.
Who receives data and where?
The project-specific notice identifies the relying organization, Mobile-ID and any subprocessors, along with processing locations and support conditions. The confirmed model has no cross-customer sharing by default. Transfers outside the environment must be explained and authorized before they occur.
Retention and protection
Retention is not inferred from membership or patient status. Separate schedules cover raw images, references, bindings and evidence, with approved exceptions and procedures for copies. A protected biometric reference remains controlled information and is not automatically anonymous.
Requests and contact
Contact the capturing organization or its published route to ask for explanations, exercise rights or report concerns. info@mobile-id.vn is Mobile-ID's general contact; do not email palm images, references, passwords or sensitive records. Subsequent identity verification and data exchange use a channel confirmed by the responsible entity.
Notice changes
Each notice has an ID and version linked to enrollment. Changes to purpose, data categories, recipients or choices require reassessment, communication and fresh consent where necessary. Prior versions are retained to explain the conditions at the time of processing.
Responsibility & deployment annex
Detailed responsibilities are determined by activity and deployment records; this public document does not replace customer-specific contractual annexes.
- The relying organization defines business purposes, populations and operational authority within the deployment.
- Mobile-ID supplies and operates components within the agreed scope, including integration, control configuration and related evidence.
- Device suppliers support models, firmware, SDKs and maintenance within authorization; data access is never implicit.
- Legal, security and service ownership assignments are maintained in each organization’s operating records.
Execution and evidence cycle
- Record purpose, organization, data/device scope and the business reference.
- Verify authority, applicable conditions, configuration and relevant obligations.
- Execute with data minimization, authorization and necessary evidence.
- Close with confirmations from relevant systems, response handling and remaining exceptions.
Legal and reference sources
Detailed obligations, periods and exceptions apply according to law, contract and the actual service configuration.