Last updated: 9 August 2026 · Developer: Bhaskar Mehra · Contact: lucent.app.support@gmail.com

Lucent is a privacy-first, on-device toolkit. It has no backend server of its own, no user accounts, no advertising, no analytics, and no third-party tracking libraries. We (the developer) do not collect, store, or receive any of your personal data. This policy explains what stays on your device, what happens when you use a tool that makes an online lookup, and why each permission is requested.

Information stored on your device

Everything Lucent saves is kept locally on your device and is never uploaded to us or synced to any cloud:

• Identifiers you choose to add to your Vault (e.g. an email, username, domain, or phone number you attest is your own).

• Findings, your Exposure Score, hardening-checklist progress, and achievements derived from your own activity.

• App settings (theme, sound/haptics, app-lock preference).

You can permanently erase all of this at any time from Settings → Wipe all local data. Uninstalling the app also removes it.

Information sent over the network

Lucent performs its lookups directly against public, keyless third-party services over encrypted (HTTPS) connections — there is no Lucent server in between. When you actively run a tool, the specific value you enter is sent to the relevant public service solely to answer your query. For example:

• An IP address, domain, or URL you look up is sent to the corresponding public intelligence/DNS/WHOIS service.

• A username you check is tested against public profile pages to see whether it exists.

• An email you scan for breaches is sent to a public breach-lookup service.

• When checking a password against known breaches, only a partial, irreversible hash prefix leaves your device (k-anonymity) — never the password itself.

These lookups are ephemeral: Lucent does not log them, does not retain them, and does not combine them into a profile of you. Once a service returns its answer, Lucent keeps nothing about the request except any result you explicitly save to your Vault. Each third-party service you query is subject to its own privacy policy. The complete, per-tool list of every service Lucent may contact is shown inside the app under Settings → Data Sources. Nothing is ever sent to a non-encrypted destination. Personal data is kept out of URL query strings, with one unavoidable exception: the public breach-lookup service accepts an email address only as a URL parameter, so checking an address for breaches necessarily sends it that way. That request is encrypted in transit like every other one, and the address is still never sent to us.

Three behaviours deserve to be spelled out:

• The Geotag Camera and your coordinates. Every other tool sends a value you typed. This one can send a value your phone measured, which is a different thing and is treated as such. Each stamp field is off until you switch it on, and a field is the only reason anything is sent: the weather fields send the coordinate to Open-Meteo, an address field sends it to your device's own geocoder (on a phone with Google Play services, that call reaches Google) and falls back to OpenStreetMap's Nominatim, and a map thumbnail fetches a tile from OpenStreetMap or Esri, which reveals the coordinate rounded to that tile's area. With no field switched on there is no panel to draw and nothing is requested. Nothing is sent to us, the coordinate is never stored anywhere but inside the file you captured, and each service is subject to its own privacy policy.

• Active network tools. Tools such as Ping, Traceroute, the Port Scanner and the Network Scanner make direct connections to a host or address range you specify (or to your own local network) in order to map it. Before sweeping any network that is not your own private Wi-Fi, the app asks you to confirm you own it or are authorised to test it — this is standard for a network-diagnostic tool and remains your responsibility. Site Status may also retry the same host over your mobile data while you are on Wi-Fi (or vice versa) to tell a real outage from a network-specific block; this can use a small amount of your mobile-data allowance.

• Optional breach monitoring. If — and only if — you switch on monitoring for one of your own emails, Lucent runs a periodic background job (about every 12 hours, and only while you are online and your battery is not low) that re-submits that email's address to the same public breach-lookup service, so it can notify you of a newly reported breach. You can turn this off at any time, and it never runs for an identifier you have not added and enabled yourself.

Device permissions and why they are used

Permissions are requested only when you open the tool that needs them, and are used strictly for that tool's on-device function:

• Camera — scanning a QR code you point at, and taking the photographs and recordings you capture in the Geotag Camera.

• Location (approximate/precise) — reading Wi-Fi, GNSS/satellite, and cellular signal properties and your own device's fix for the signal-analysis tools, and stamping a photograph or recording with where it was taken in the Geotag Camera. Lucent never uses this to locate any other person, and Wi-Fi/Bluetooth scanning is flagged neverForLocation.

• Microphone — measuring ambient loudness for the live sound-level meter, which measures in real time and records nothing. The Geotag Camera also uses it in two ways you control: it records sound into a video while the sound switch is on, and, if you have switched on the ambient-noise field, it takes a reading lasting a fraction of a second at the moment the shutter fires. Outside a video you have chosen to record with sound, no audio is kept.

• Phone state / phone numbers — showing your cellular network and serving-cell details, and (for you only) your own SIM/line information.

• Nearby Wi-Fi devices / Wi-Fi state / Bluetooth — reading the Wi-Fi network you are on and listing nearby radios in the scanner tools. Wi-Fi and Bluetooth scanning are flagged neverForLocation.

• Network state / change network state — checking whether you are online, and (for Site Status' second-opinion check) asking to try a host over a specific transport such as mobile data while you are on Wi-Fi.

• NFC — reading a tag or card you physically tap to the phone. This reads what the tag broadcasts on contact: its chip model and identifiers, any stored NDEF records (links, text, Wi-Fi/Bluetooth pairing tags), and — only after you turn on an in-tool authorisation switch — a contactless payment card's number and expiry, or a MIFARE access card's unprotected sectors. It is entirely on-device and read-only: nothing is written to the tag and nothing is uploaded. A contactless read never exposes the printed security code (CVV) or a usable payment cryptogram, so it cannot be used to pay or clone a card. Read only tags and cards you own or are authorised to.

• Photos/media — reading a photo you select to display or strip its metadata (embedded GPS is shown only if you explicitly ask to reveal it), and saving what the Geotag Camera captures to your gallery; nothing is uploaded.

• Notifications — sending you a breach alert, only if you switch on breach-monitoring for one of your own emails.

• Biometric — the optional app-lock (fingerprint/face/PIN) that gates the app; authentication is handled by the operating system.

Checking whether specific apps are installed

The Device Integrity tool checks your device for signs of rooting or tampering. As part of this, it asks the operating system whether a fixed, built-in list of known root-management, hooking and root-hiding apps is present (for example Magisk, KernelSU, Xposed/LSposed). It can only ask about the specific packages on that list — it cannot and does not enumerate your other installed apps. The result is computed on your device, shown to you, and never transmitted. This is disclosed here because checking for named packages is a form of reading your app inventory.

Data sharing and selling

We do not sell your data, and we do not share it with anyone — because we never receive it in the first place. The only data that leaves your device is the query you personally submit to a public service while using a tool, as described above.

Children

Lucent is a security and privacy utility intended for users aged 16 and over. It is not directed at children under 16, and it does not knowingly collect any information from them.

Security

Network requests are HTTPS-only. The optional File Encryptor performs AES-256 encryption entirely on your device with a passphrase you choose; the passphrase and files never leave the device, and there is no recovery mechanism. The optional biometric app-lock adds a device-level gate. Because no data is transmitted to or held by us, there is no server-side store to be breached.

Changes to this policy

If this policy changes, the updated version will be posted at this URL with a new "Last updated" date.

Contact

Questions about this policy or Lucent's privacy practices can be sent to lucent.app.support@gmail.com.