Mobile Application Privacy Policy
Apple requires all apps to declare their data practices in the App Store. The table below summarises NeuralKey's data collection in the format required by Apple's App Privacy guidelines (App Store Connect Privacy Questions).
| Privacy Category | Details |
|---|---|
| Data Used to Track You | None. NeuralKey does not track users across third-party apps or websites and does not use advertising identifiers. |
| Data Linked to You | Username; government-issued document image (transmitted to our servers during identity verification only); identity-match facial photograph (a still image captured solely for server-side document-face matching, transmitted once during identity verification over an end-to-end encrypted connection and deleted upon completion of the verification review). |
| Data Not Linked to You | Motion sensor data (on-device, Security Guard feature); battery state (on-device); microphone (briefly activated at the iOS camera framework level during video-based liveness detection; audio capture is explicitly disabled -- no audio is recorded, processed, or transmitted); network connectivity status (on-device); security event logs (encrypted, local). |
| Data Not Collected | Advertising identifiers (IDFA/GAID); location data; audio recordings; browsing history; search history; purchase history; financial information; contacts; messages; health and fitness data; sensitive information beyond what is required for identity verification. |
NeuralKey ('we,' 'our,' or 'us') is a mobile identity-management application published by PRESTIGE ALLIANCE CO., LTD. This Privacy Policy explains what personal data we collect, why we collect it, how we store and protect it, and the rights you have over it.
By downloading or using the App, you confirm that you have read and agree to this Privacy Policy. If you do not agree with any part of this policy, please discontinue use of the App and uninstall it from your device.
The following data is collected and processed exclusively on your device. None of this data is transmitted to our servers or shared with third parties.
We do not collect, and have no technical access to, any of the following:
| Data Category | Legal Basis | Applicable Law |
|---|---|---|
| Username / Handle | Performance of contract | GDPR Art. 6(1)(b); LGPD Art. 7(V) |
| Government-issued document image | Explicit consent; legal obligation | GDPR Art. 9(2)(a) & (b); LGPD Art. 11(I) |
| Identity-match facial photograph | Explicit consent | GDPR Art. 9(2)(a); LGPD Art. 11(I) |
| Liveness selfie (on-device only) | Performance of contract | GDPR Art. 6(1)(b) |
| Security keys | Performance of contract; legitimate interest | GDPR Art. 6(1)(b) & (f) |
| Recovery phrase | Performance of contract | GDPR Art. 6(1)(b) |
| Motion sensor data | Legitimate interest (Security Guard feature, on-device) | GDPR Art. 6(1)(f) |
| Microphone activation (framework only) | Legitimate interest (mandatory iOS camera framework requirement) | GDPR Art. 6(1)(f) |
| Security event logs | Legitimate interest (security monitoring) | GDPR Art. 6(1)(f) |
| Digital identity credentials | Performance of contract | GDPR Art. 6(1)(b) |
Where processing is based on your consent, you may withdraw it at any time via Settings - Delete Account, or by contacting us at privacy@neuralkey.com. Withdrawal of consent does not affect the lawfulness of processing carried out before withdrawal.
| Purpose | Data Used |
|---|---|
| Creating and managing your digital identity | Username and security keys |
| Identity verification | Government-issued document image; identity-match facial photograph (transmitted to server); liveness selfie (on-device liveness check only -- never transmitted) |
| Authenticating you within the App | Fingerprint, Face ID, or device PIN -- processed by the device operating system only (LocalAuthentication framework on iOS; BiometricPrompt on Android); never transmitted |
| Securing your communications | Security keys that protect data during transmission |
| Issuing and verifying digital identity credentials | Digital credentials and verified identity information |
| Security Guard -- detecting unauthorised device movement | Motion sensor data (accelerometer, gyroscope) -- on-device processing only; security event logs |
| Device Integrity Check | Battery state (on-device) |
| Liveness detection and document scanning | Camera (video frames, still photographs); microphone activation is a mandatory iOS camera framework requirement -- audio capture is explicitly disabled (enableAudio: false) |
| Background credential refresh | Security keys and digital identity credentials (on-device only); no personal data is transmitted during background refresh unless a network operation was already authorised by the user |
| Backup and account restoration | Encrypted recovery phrase and security keys (on-device only) |
| Authenticating with third-party services via QR code | Only the specific identity information you explicitly approve for each interaction |
During the identity verification process, we use automated systems -- including on-device liveness detection and automated document-reading technology -- to assess whether your identity document is genuine and whether the identity-match facial photograph corresponds to the document photograph.
This process may produce an automated decision regarding whether your identity is successfully verified. Such a decision may affect your access to features within NeuralKey that require a verified identity.
| Safeguard | Description |
|---|---|
| On-device encrypted storage | All sensitive data -- including security keys, recovery phrase, and credentials -- is stored locally on your device using strong encryption, protected by your device's built-in secure hardware chip (Secure Enclave on iOS). |
| Encrypted local logs | Security event logs are retained exclusively on your device in a securely encrypted format. These logs are never transmitted to our servers. |
| Transmission security | All data exchanged over the internet uses TLS-encrypted connections. Identity verification data is additionally end-to-end encrypted. |
| Liveness selfie (on-device only) | Liveness images used for the on-device liveness check are processed entirely by Google ML Kit on your device. They are never transmitted to NeuralKey servers or to Google. No facial biometric template or faceprint is stored. Liveness images are automatically deleted upon session completion or within 24 hours, whichever is sooner. |
| Identity-match facial photograph | The still facial photograph transmitted during the identity verification submission is sent over an end-to-end encrypted connection. It is permanently deleted from our servers upon completion of the back-office review, and in any event within 30 days. |
| Government-issued document image | Transmitted only once during identity verification over an end-to-end encrypted connection. Permanently deleted upon completion of the verification review, within 30 days. |
| Microphone | Audio capture is explicitly disabled on all camera controllers (enableAudio: false). The microphone is activated at the iOS AVFoundation framework level only. No audio stream is created, stored, or transmitted by the App at any point. |
Apple requires each system permission to have a clear, specific purpose description. Each permission below maps directly to a required App function. You may revoke any permission at any time through your device system settings; revoking a permission will disable the corresponding App feature.
| Permission (iOS key) | Apple's Sensitive Data Category | Specific Purpose |
|---|---|---|
| Camera (NSCameraUsageDescription) | Camera | Capture a liveness selfie for on-device liveness verification; capture an identity-match facial photograph for server-side document-face matching; scan QR codes for third-party authentication via MobileScanner; photograph a government-issued identity document for OCR verification. |
| Face ID (NSFaceIDUsageDescription) | Biometric Data (device OS-managed) | Authenticate the user when opening the App and when confirming sensitive actions via Face ID. Processed entirely by the device operating system via the LocalAuthentication framework. No biometric data is transmitted to our servers. This key is required by Apple even when Touch ID or device PIN fallback is available. |
| Microphone (NSMicrophoneUsageDescription) | Microphone | Required by the iOS camera framework (AVFoundation) when initialising an AVCaptureSession for liveness detection and document scanning. Audio capture is explicitly disabled in the App (enableAudio: false on all CameraController instances). No audio is recorded, processed, stored, or transmitted. This key is a mandatory Apple framework requirement; removing it may cause a runtime crash even when audio capture is disabled. |
| Motion Sensors (NSMotionUsageDescription) | Motion & Fitness | Used by the Security Guard feature to detect unauthorised movement or rotation of your device while it is armed (accelerometer and gyroscope via sensors_plus package) and display an on-screen security alert to the user. |
| Photo Library (NSPhotoLibraryUsageDescription) | Photos | Required by the file_picker package when browsing and selecting files or folders on your device to save or load encrypted credential backup data and export audit logs. No photos are accessed, read, or transmitted without explicit user selection. |
| Internet Access | n/a (network permission) | Required for identity verification submissions and for the issuance of digital identity credentials. |
| Network Status | n/a (network permission) | Determine whether an internet connection is available before initiating network-dependent operations (connectivity_plus package). |
| Background Processing (BGTaskSchedulerPermittedIdentifiers; UIBackgroundModes: processing) | n/a | Enables the flutter_foreground_task package to schedule a BGProcessingTask (identifier: com.prestigealliance.neuralkey.refresh) that keeps the Security Guard foreground service alive when the device is idle. No personal data is transmitted during background processing. No new data collection occurs in the background. |
We do not sell, rent, or trade your personal information to any third party. We may share data only in the following strictly limited circumstances:
When you complete identity verification, your government-issued document image and identity-match facial photograph are transmitted to NeuralKey's verification servers. Where such transfers cross international borders, we rely on the following legally recognised safeguards:
| Jurisdiction | Transfer Mechanism |
|---|---|
| European Economic Area / United Kingdom | Standard Contractual Clauses (SCCs) approved by the European Commission (Decision 2021/914), incorporated into our data processing agreement. A copy is available upon request to privacy@neuralkey.com. |
| Brazil (LGPD) | Contractual clauses that provide an equivalent level of protection as required under LGPD Article 33(II). |
| Japan (APPI) | Transfer made pursuant to the data subject's consent, or subject to equivalent protection measures under APPI Chapter IV-2. |
If you do not wish your identity verification data to be transferred internationally, do not initiate the identity verification process.
| Jurisdiction | Notification Obligation |
|---|---|
| EU / UK (GDPR) | The relevant supervisory authority will be notified without undue delay and, where feasible, within 72 hours of our becoming aware of the breach (GDPR Art. 33). Affected individuals will be notified without undue delay where the breach is likely to result in a high risk to their rights and freedoms (GDPR Art. 34). |
| Brazil (LGPD) | The Brazilian national data protection authority (ANPD) and affected individuals will be notified within 3 business days of our becoming aware of the breach (LGPD Art. 48; ANPD Resolution No. 15/2024). |
| Canada (PIPEDA) | The Office of the Privacy Commissioner and affected individuals will be notified as required under the PIPEDA Breach of Security Safeguards Regulations. |
Because the majority of personal data in NeuralKey is stored locally on your device and protected by strong encryption, the risk of a server-side breach affecting your security keys, recovery phrase, or biometric data is substantially mitigated. Nonetheless, any identity verification data submitted to our servers is fully covered by the commitments above.
Apple requires apps to clearly disclose their minimum age requirement and the mechanism by which under-age use is prevented. NeuralKey is rated 17+ on the App Store. The identity verification process, which requires a valid government-issued identity document, serves as an effective age gate.
NeuralKey is not directed to individuals under the age of 18. We do not knowingly collect personal information from minors. The identity verification process -- which requires a valid, government-issued identity document -- serves as an effective mechanism to prevent under-age access to the App's core features.
If you believe that a minor has provided us with personal information, please contact privacy@neuralkey.com and we will take prompt steps to delete that information from our records.
| Applicable Law | Age Threshold |
|---|---|
| COPPA (United States) | Children under the age of 13 |
| GDPR Article 8 (EU / EEA) | Children under the age of 16, or a lower threshold as set by the applicable member state (minimum 13) |
| LGPD Article 14 (Brazil) | Children under the age of 12; adolescents under the age of 18 (with additional protections) |
| PDPA (Singapore) | Minors as defined under the applicable national law of the user's jurisdiction |
Depending on your jurisdiction, you have the following rights regarding your personal data. To exercise any right, please contact us at privacy@neuralkey.com with the subject line 'Privacy Rights Request -- [Right Type].' We will verify your identity before processing any request.
| Jurisdiction / Applicable Law | Response Timeline |
|---|---|
| GDPR / UK GDPR | 30 calendar days; extendable by a further 60 days for complex or numerous requests (with prior written notice to you) |
| CCPA / CPRA (California) | 45 calendar days; extendable to 90 days total with prior notice |
| LGPD (Brazil) | 15 calendar days |
| PIPEDA (Canada) | 30 calendar days |
| PDPA (Singapore) | 30 calendar days |
| APPI (Japan) | Without undue delay; within a reasonable period as required by applicable guidance |
Apple requires disclosure of all third-party SDKs integrated into an app and their respective data-collection practices. The table below provides a complete listing of SDKs used in NeuralKey, the data each SDK processes, and whether any data leaves the device.
| SDK / Service | Purpose | Data Processed | Data Leaves Device? | SDK Privacy Policy |
|---|---|---|---|---|
| Google ML Kit -- Face Detection | On-device liveness verification during identity checks | Liveness selfie video frames; liveness probability score | No -- processed on-device only | policies.google.com/privacy |
| Google ML Kit -- Text Recognition | Automated on-device reading of identity documents | Document image text content | No -- processed on-device only | policies.google.com/privacy |
| Google Fonts | Rendering application typography within the user interface | Font display metadata only | No -- fonts are bundled in-app | policies.google.com/privacy |
NeuralKey has entered into data processing agreements with all relevant third-party service providers to ensure compliance with applicable data protection laws.
We reserve the right to update this Privacy Policy from time to time to reflect changes in our practices, applicable technology, legal requirements, or other factors. We will handle changes as follows:
© 2026 NeuralKey / PRESTIGE ALLIANCE CO., LTD. Decentralized Identity (DID) Platform
Last Updated: June 3, 2026