Connectors
Device connector
Tie bans to devices without fingerprinting, with Play Integrity Device Recall on Android and Apple DeviceCheck on iOS.
Ties a ban to the device without fingerprinting: Android Play Integrity with Device Recall, iOS Apple DeviceCheck. Google and Apple keep a few bits per device and developer account that survive reinstall and factory reset. Limenia sets them for banned/suspended users at their next device check and reads them on every check (Device checks).
The API call, its fields and its answers are described in Device checks. The connector needs a plan that includes it.
In the app
Get the token with the Flutter plugin limenia_device (LimeniaDevice.requestToken(requestHash: …, cloudProjectNumber: …)), send it to your backend, never to Limenia. Android needs the project number of the Cloud project linked to Play Integrity; minSdk 24, iOS 15.
In the backend
Issue the request hash (Device checks), take the user from the login, forward once, fail open.
Setup
Android: link Play Integrity to a Cloud project, request Device Recall from Google, create a service account in that project and give the Limenia connector service account shown in the dashboard roles/iam.serviceAccountTokenCreator on it, prove ownership with the project label, then Test connection. iOS: create a DeviceCheck key (.p8), enter team ID, key ID and key, Test connection. Do not enable a platform if your developer account already uses these bits for something else.
Test mode
Test mode is switched on per app in the dashboard. It accepts platform: "test" with tokens test:<device> (add :risk for a device without integrity) on emulators and simulators. Turn it off in the production app.
Signals, webhooks and quota
- Limenia creates system signals
device_flaggedanddevice_riskfor rules. Webhooks contain nothing about devices. - Quota: Google allows 10 000 decodes per day per project (shared with Firebase App Check). Check only at registration, login and optionally reports.
Duties of the tenant
The tenant must cover the device check in its privacy policy and store privacy labels, decide on consent for reading device information, and offer users a way to ask for a reset (Apple requires it); a moderator then requests the reset in the user file.
See Data protection.