App privacy — Lumaria Link
Last updated: 2026-08-26. Lumaria Link connects devices on a local network. Recovered 5.0.1 technical documentation describes NSD/mDNS discovery, in-person pairing and screen sharing only after visible MediaProjection consent; final physical-build and Data Safety verification are still pending.
- Application
- Lumaria Link
- Operator
- Lumaria Lab
- Legal entity
- Lucky Blox S.L.U.
- Verification status
- Conservative public policy; Play Data Safety will be finalized against the audited final APK/AAB.
- Privacy contact
- hola@lumarialab.es
Privacy summary
- It is not designed as Internet remote access or a Lumaria cloud surveillance platform.
- Local discovery is not authorization: commands require pairing.
- Screen sharing requires visible Android MediaProjection consent for each new session in the documented architecture.
Permissions and access
- INTERNET for TCP sockets and LAN NSD/mDNS; this permission alone does not imply an external backend.
- ACCESS_NETWORK_STATE and CHANGE_WIFI_MULTICAST_STATE for local connectivity/discovery where needed.
- WAKE_LOCK and VIBRATE for local operations/alerts; CAMERA is documented for flashlight use, not photography.
- MediaProjection uses the system consent flow; final behavior must be confirmed in the release build.
External services and communications
The documented 5.0.1 architecture uses the same Wi‑Fi, NSD/mDNS and local transport. It does not document a Lumaria cloud server, continuous GPS, remote camera or remote microphone. Authorized screen frames are designed to be encrypted before crossing the LAN.
Retention and deletion
Role, preferences, paired devices and history are documented as local data. Persistent secrets are designed to be protected with AndroidKeyStore. Exact retention will be confirmed against the production build.
Rights and contact
For privacy questions or applicable rights requests, write to hola@lumarialab.es.