What the session sends to the NeuroVision server
To verify the person's identity and prevent fraud, a session sends the NeuroVision KYC server:
- the document photos;
- the liveness check photos and video;
- the device's facts: model, OS, language, time zone, screen, and the emulator / simulator and tampering signals.
Product analytics
The SDK can send product analytics — the same events as the Web SDK — to PostHog: the screens shown, errors, entry and consent, the camera (permission, switching, torch), the document steps, the liveness check with its timings, request retries, and the session's outcome. Liveness check telemetry carries durations, counts and sizes only.
Never sent to analytics: camera frames, faces or face positions, the liveness check challenge's parameters, the document's recognised data.
The events of one session are tied together by the session's clientKey (or taskId), as the Web SDK does, so that one person's events from the site and from the app join.
The PostHog project is named by the app, not built into the SDK: NeuroVisionKycPostHogKey and NeuroVisionKycPostHogHost in the app's AndroidManifest.xml meta-data or Info.plist — see section "Analytics (optional)" in the guide for your platform: Android, iOS, Flutter, React Native. Without a key nothing is sent at all. Analytics is best effort: the session does not wait for it, and a batch of events that fails to send is dropped.
The SDK's logs
In normal operation the SDK writes nothing to the device's system log or to files. It never logs the client key, document images or recognised personal data.
What to declare in the app stores
- Google Play, Data safety: photos and videos (the document, the face), device and other identifiers, app info (device facts) — collected for fraud prevention and security, shared with NeuroVision; with analytics on — app interactions and diagnostics as well, for analytics.
- App Store: the framework carries its own privacy manifest (
PrivacyInfo.xcprivacy); Xcode merges it into your app's privacy report (Product → Archive → Generate Privacy Report), from which you fill in the privacy label. - Camera: iOS needs
NSCameraUsageDescriptioninInfo.plist; on Android the SDK asks for the permission itself.