On this page
Privacy by configuration
Collect less, understand more
A device signal is useful only when its purpose, semantics, retention, and limitations are understood before collection.
What the SDK does and does not do
The package reads local observations and returns them to the calling application. It does not upload data, create a persistent cross-reinstall identifier, prompt for permissions, or contact a vendor service.
This boundary reduces hidden processing, but it does not make every use privacy-safe. The host application remains responsible for disclosure, lawful basis, consent where required, transport, storage, access, retention, and deletion.
Data minimization workflow
Define the event
Collect around a documented security or fraud-prevention action, not continuously because the SDK is available.
Select probe groups
Enable only the categories needed to answer the stated question. Prefer coarse observations over high-entropy fields.
Project fields
Remove unused values before the event reaches your backend. Avoid storing raw location or local addresses when a coarser derived feature is sufficient.
Expire data
Set a retention period tied to investigation, model training, legal, and audit needs. Delete raw values earlier than derived aggregates when possible.
Production governance checklist
- Document purpose and data owner for each enabled probe.
- Map platform and regional disclosure or consent requirements.
- Restrict access to raw observations and record administrative access.
- Encrypt events in transit and at rest using the host system controls.
- Version backend feature logic and monitor schema drift.
- Support deletion, retention enforcement, and incident response.
- Review false-positive impact across device age, region, platform, and accessibility use.
High-sensitivity areas
| Area | Why it needs review | Safer pattern |
|---|---|---|
| Location | Can reveal precise movement or home and work patterns. | Use existing permission state or coarse server-derived consistency where adequate. |
| Telephony | Carrier, SIM, and country can expose personal context. | Store only the comparison result when raw values are unnecessary. |
| Accessibility | May relate to disability and legitimate assistive technology. | Never treat accessibility use itself as fraud. |
| Screen and touch observation | Screenshot detection is user-visible and overlay flags can have legitimate causes. | Keep transaction safety off by default and observe only protected flows. Declare android.permission.DETECT_SCREEN_CAPTURE or android.permission.DETECT_SCREEN_RECORDING in the host app only when the corresponding field is required. |
| Local addresses | High entropy and network-sensitive. | Prefer a boolean or coarse network class if it serves the purpose. |
| Known apps | App visibility can expose behavior or affiliations. | Use the finite audited list, document each entry, and never request broad package visibility. |
Standalone Android transaction sessions are inactive until the host explicitly attaches them. Hosts must detach/close them with their Activity lifecycle. The SDK observes touch flags and capture events, not touch coordinates, text, screenshot images or recorded video. React Native detaches on pause/destroy and reattaches only on a subsequent enabled collection. Historical observations can span gaps and do not establish continuous monitoring; unavailable current capture coverage is omitted. These migration changes remain subject to release notes and physical-device QA.
Responsible decision use
Root, jailbreak, emulator, VPN, accessibility, screen capture, and remote-access observations all have legitimate explanations. Combine calibrated mobile evidence with authenticated account, transaction, behavioral, and server-side context. Monitor false positives and distribution shifts after every rule or model change.
This documentation is engineering guidance, not legal advice. Involve privacy, legal, security, and risk owners for your product and jurisdictions.