Tool profile
N0RMA
Record nearby Android radio observations without treating them as a safety verdict
Claims and corrections are reviewed before public profile changes.
Trust / disclosure
How to read this profile
Editorial line
Editorial judgment and commercial context are kept separate on OSINT4ALL.
Review status
This profile has an editorial review date. Source checking does not mean the tool was hands-on tested.
Claims / submissions
Corrections and claim requests are reviewed before any public change is made.
Commercial context
No commercial relationship is disclosed on this profile.
Editorial verdict
Use case and fit
This is editorial guidance, not vendor copy.
Documenting nearby Bluetooth, Wi-Fi and Remote ID observations during an authorized protective survey, with explicit radio and location uncertainty.
Submitted for editorial consideration; independently desk-reviewed by OSINT4ALL. Official-source review on 2026-10-22, not hands-on testing or an independent implementation audit. The official Android repository carries an MIT license. Use current official release information and check build provenance before installing. The submitted F-Droid listing was pending and is not represented here as available.
Best for documenting nearby Bluetooth, Wi-Fi and Remote ID observations during an authorized protective survey, with explicit radio and location uncertainty.
Operational snapshot
Workflow, access, and coverage
Define a proportionate protective purpose; inspect release provenance and permissions; record the phone/build and survey limits; corroborate radio hints with lawful physical/contextual checks; redact exports; seek qualified help where safety is at risk.
English project documentation was reviewed. Network names and device identifiers can contain arbitrary text or be misleading; do not interpret a name as an authenticated identity.
Limits
Strengths, caveats, and risk
A local survey record can preserve what the phone observed alongside the checks that were not possible; exportable observations can support a carefully scoped follow-up.
Phone hardware, Android permissions and scan throttling limit observations. Names and radio strength are weak clues; a device classification or rough direction may be wrong.
Quiet results cannot establish a space is safe. Dormant, wired, cellular and non-broadcasting devices may be missed. Remote ID can be spoofed; a broadcast does not authenticate a drone, operator or position.
The privacy document describes local history and deletion controls, but optional OS address lookup and browser destinations use external services. Exported files can reveal location and device observations; deliberate sharing is not made private by local collection.
Survey only where authorized and minimize observations about bystanders. Do not interfere with radio systems or confront someone based on an alert. Preserve uncertainty in any report; checksums alone do not prove origin or evidential admissibility.
Provider documentation supports the described scope, not a guarantee of accuracy, safety or completeness. Pending Verification; no account, install, upload or sensitive lookup was used for this review.
Maintenance
Source status & suggest an update
Help keep this profile accurate. Update requests are reviewed and logged before publication.
Source checked: 2026-10-22
If something is outdated, please submit a correction or ownership update request. Claim requests are reviewed and do not grant editorial control.
Commercial or sponsorship requests use the separate partner workflow.