Permissions and privacy
The permissions the SDK uses, what it keeps on the phone, and how it is protected.
Permissions
The SDK asks only for what a journey and a video call use, and only when they first need it.
| Permission | Used for |
|---|---|
| Camera | Photographing documents and selfies; the video call |
| Microphone | The video call |
| Notifications (Android 13+) | Video call notifications; requested by your app |
| Internet | Reaching your institution |
It never asks for location, contacts, storage or photo library access.
What stays on the phone
- Photos are sent to your institution and deleted from the phone straight away.
- Answers, documents and video go only to your institution. They never pass through your app.
- On iOS a journey keeps nothing on the phone at all once it closes. On Android, `terminate` removes what the journey kept; call it when the customer signs out.
- The push token is held in memory only, until you call `terminate`.
How it is protected
- The SDK shows pages only from your journey host, over https. Anything else opens in the phone's browser.
- On Android, screenshots and screen recording are blocked while a journey or call is on screen. On iOS, the screen is covered while it is being recorded.
- Each start is checked against your allowed apps, so a key copied into another app does not start journeys. Pin your Android signing certificate for the strongest check.
- Revoking a key, removing an app or turning on the kill switch takes effect at the customer's next start.