Auto Secure LoginPlatform
LiveWebAndroidSecurity & RF intelligence

Know what's transmitting on a site you're responsible for.

See what is actually transmitting around you — a receive-only radio survey run from a phone and a low-cost USB receiver.

Built for: Security consultants and field assessors who get asked "is anything transmitting here that shouldn't be?" and need a defensible answer · Managed service providers adding a radio walkthrough to a site assessment without buying bench equipment · Facilities and physical-security managers doing a periodic sweep of a building they are responsible for · Locksmiths, automotive technicians and fleet shops who need to know whether a fob, remote or tyre sensor is transmitting at all

55radio allocations in the built-in band reference, each carrying a caution level
16one-tap band presets in the Android app, from broadcast FM to satellite navigation
14survey presets in the browser app
8capability rows the browser app's device check reports on

The problem

BandSight exists because of this.

Someone points at a room, or a fence line, or a shipping bay, and asks whether anything is transmitting that shouldn't be. Most of the time you cannot answer honestly. The app-store tools that promise to find hidden devices show a green checkmark that means nothing — a phone's own radio hardware cannot look at the spectrum, it can only report the handful of interfaces the operating system chooses to expose.

So you tell the client "looks clear" and you have no idea whether that is true. Real radio equipment exists, but it was built for a bench. Desktop software, a driver to wrestle with, a scrolling waterfall that shows you energy without telling you what it is or whether you are allowed to listen to it.

And when you are done there is nothing to hand over — no site name, no scope, no comparison against last time, no file the client can keep. On a walkthrough you do not have a bench. You have a phone, ten minutes, and someone watching you.

There is a legal edge to this too. Plenty of frequencies are perfectly fine to receive. Plenty of others carry private correspondence, and some are outright unlawful to intercept. Most tools show you a number in megahertz and leave the rest to your judgement. Getting that wrong is not a technical mistake, it is a liability you carry personally.

And the answer that should worry you most is "found nothing." A loose antenna, a band that is simply out of the receiver's reach, a receiver the computer never really opened — every one of those produces a calm, empty screen that looks exactly like a clean site.

What changes

  • Receive-only is verified automatically, not merely promised — an automated check fails if any path that could push data to the receiver ever appears in the driver code, or if a signal generator is added to the audio code.
  • The Android app declares no network permission whatsoever. That is enforced by the operating system, not by a privacy policy, and anyone can confirm it in the handset's own settings.
  • It names restricted bands so you can recognise and avoid them. The reference lists protected allocations to keep you off them, not to point you at them.
  • When a band is out of the receiver's reach it says so and names the hardware that would reach it, instead of showing an empty display you could easily mistake for a clean result.
  • The receiver was proven against real hardware before it was called finished. Three genuine faults were found on the bench and fixed, and each now has a regression check that stops it returning.
  • Baseline comparison matches by frequency, not by record number, so a repeat survey does not report every transmitter as brand new.
  • Hardware recommendations carry no affiliate tracking, and an automated check enforces it — the kit is named because it works, not because it pays.

What it does

How BandSight works, start to finish.

BandSight is two things that stay honestly separate, delivered on two surfaces that are also honestly separate. The first is a straight check of the device in your hand: which radio interfaces this device and this browser actually expose, and which they do not. Eight rows cover the running environment, secure connection, short-range wireless, tag reading, attachable receivers, connection state, location and offline capability, and each is reported as available, limited, or simply not exposed rather than inventing a result.

That alone settles the "can my phone find hidden cameras" question in about ten seconds, and it settles it in the direction most tools will not — a normal phone is not a spectrum analyzer, and BandSight says exactly that on the page. The second is the receiver.

Plug an inexpensive USB radio receiver into your phone or laptop through a USB-C adapter and BandSight becomes a working radio. It tunes, draws a live spectrum and a rolling waterfall, demodulates wideband FM, narrowband FM and AM, and plays the audio. That receiver was proven against real hardware before it was ever called finished — three genuine faults in the way it talked to the receiver were found and fixed on the bench, and each one now has an automated check so it cannot quietly come back.

Fourteen survey presets put the common bands one tap away. The browser app is where a survey becomes a document. Observations group under a named site and a stated authorization scope instead of piling into one flat list. Declare the transmitters that are supposed to be radiating, and anything else is flagged — which is the actual question a site assessment is paid to answer.

Load an earlier survey and see what has appeared since, matched by frequency rather than by record number, because a repeat survey creates new record numbers for the same physical transmitter and a naive comparison would report everything as new every time. Export the whole thing as a spreadsheet or a structured file, or merge two operators' files without double-counting.

A built-in reference covers 55 allocations across the receiver's range and tells you, for each one, whether it is open to log freely, may carry private correspondence, is a safety-of-life service, or is unlawful to intercept — the restricted ones are listed precisely so you can recognise them and stay off them.

The separate Android app is where fieldwork happens, and it is worth being clear that the band sweep, saved stations, the signal finder and device capture live there and only there — the browser app does not have them. Sweep a range and it lists every carrier it found, with strength.

Save the ones that matter, search them later, tap one to tune straight back. A signal finder gives you a strength meter, a peak hold, and beeps that get louder, higher and faster as the signal grows, so you can walk a building and home in on a source; on a handset with a compass it also records the heading where the signal was strongest, which is how you actually use a directional antenna.

Sixteen one-tap band presets cover broadcast FM, the aircraft band, weather, marine, the 2 metre and 70 centimetre ham bands, walkie-talkie channels, the unlicensed device bands, ADS-B, satellite navigation and a low-cellular coverage sweep. When you pick something the receiver genuinely cannot reach — Wi-Fi, Bluetooth, shortwave — it tells you why and what hardware would reach it, instead of showing an empty graph you might read as "clear." Capture mode, also Android-only, handles the short bursts that fobs and sensors emit.

Tune to one of the four unlicensed sub-GHz bands, press capture, and press a car fob, gate remote, tyre sensor or weather sensor nearby. BandSight times each on-off burst and slices it into bits, giving you a fingerprint: frequency, timing, pulse count, and the raw pattern in binary and hex.

That is enough to tell one device from another and to confirm whether a remote is transmitting at all. You can name a device, name its buttons, and learn a button by pressing it a few times. It reads only. It never unlocks anything, never transmits, and never replays a code.

Nothing leaves the device unless you export it. The browser app keeps records on the machine you used it on. The Android app carries no network permission at all, so it cannot open a connection even in principle — anything it hears stays on the handset.

Both run in English and Spanish, and the browser app keeps working once loaded even with no signal.

Features

Everything in the current release.

Each of these is built and working today. Nothing on this list is a roadmap item.

01

A straight answer about your device (browser app)

BandSight checks eight things this specific device and browser actually expose — the running environment, a secure connection, short-range wireless, tag reading, whether a receiver can be attached at all, connection state, location and offline capability — and reports each as available, limited, or not exposed. Where a capability is limited, it says how rather than glossing over it. You can save that check into the field report as a dated record of what the device could and could not do that day.

02

A working receiver, in the browser or on a handset

With a small USB radio receiver attached, BandSight tunes, shows a live spectrum and a rolling waterfall, and plays demodulated audio in wideband FM, narrowband FM or AM. It is a real receiver, not a visualisation — it was validated against actual hardware, receiving broadcast FM across the band and playing it aloud. Retune while it is running and it hands the radio over cleanly instead of stalling.

03

Fourteen survey presets (browser app)

Broadcast FM, the civil aviation band, weather satellite downlinks, marine VHF and the calling channel, vessel position telemetry, weather radio, radiosondes, the four unlicensed device bands, licence-free personal radio, and both aviation beacon frequencies — each one a tap, each carrying a short note on what lives there and how to treat it. No typing frequencies while a client watches.

04

Sweep a band, get a list (Android app)

Give it a start and end frequency, or tap a preset, and BandSight sweeps the range and lists every carrier it finds with its strength. Progress and a running count are shown while it works, and you can pause and resume without losing what you have found. If the range you asked for falls below the receiver's reach, it tells you that up front rather than sweeping an empty band.

05

Saved stations (Android app)

Anything worth coming back to gets saved with one tap — from a scan result, or from whatever you are tuned to right now. The list is searchable, supports favourites, and tapping an entry tunes straight back to it. Scan results show a tick when they are already saved, so a repeat sweep of the same site does not fill the list with duplicates.

06

Signal finder — walk toward the source (Android app)

A strength meter with peak hold sits on the centre of the tuned frequency, and an optional beep gets louder, higher and faster as the signal grows. That turns a number on a screen into something you can follow through a building. On a handset with a compass it also records the heading where the signal was strongest, which is how you get a bearing with a directional antenna — and it tells you plainly when no compass is present, and that a plain whip gives the same strength in every direction, so you home in by moving.

07

Capture what fobs and sensors send (Android app)

On the four unlicensed sub-GHz bands — 315 MHz for most North American car fobs, 433.92 MHz for European cars, gate remotes and weather sensors, and 868 and 915 MHz for tyre and other sensors — BandSight captures each short burst and slices it into bits. You get the frequency, the on-off timing, the pulse count and the raw pattern in binary and hex. An all-bands sweep locks onto whichever band a signal appears on and holds it until the burst ends, so nothing is cut off mid-air.

08

Device library (Android app)

Name a device, name its buttons, then learn a button by pressing the fob at it a few times — every press is captured under that button. It builds a personal reference of the transmitters you care about, so next time you can compare a live capture against what that device looked like before. Captures and saved stations both export and import as a spreadsheet, so the library travels with you.

09

Band reference with cautions (both apps)

Fifty-five allocations across the receiver's range, from low-frequency beacons to the top of the tuner, each carrying a plain caution: open to log freely, may carry private correspondence, safety-of-life, or restricted. Where allocations overlap the strictest caution wins, and the app names the band the caution came from — so a weather channel is not left carrying a warning that really belongs to the land-mobile band it sits inside. The same reference appears as a lookup right under the frequency field while you log.

10

Expected versus found (browser app)

Declare the transmitters that are supposed to be radiating — the client's fobs, meters and access points — and anything else that turns up is flagged. That is the difference between a logbook and a survey that answers a question. Entries with no frequency, such as a device capability check, are excluded from the count rather than inflating the one number that matters most.

11

Baseline comparison (browser app)

Load a survey from last month or last quarter and BandSight shows you what has appeared since. Matching is by frequency within a tolerance, never by record number, because a repeat survey mints new record numbers for the same physical transmitter — a comparison by record would report every emitter as new, every single time, and quietly ruin the feature.

12

Sessions, export, import and merge (browser app)

Observations group under a named site and a stated authorization scope — your own equipment, a client-authorized site, or public broadcast — instead of piling into one flat list. Ending a session leaves later observations unassigned rather than back-dating them into a closed survey. Export as a spreadsheet or a structured file, and merge two operators' files into one record with duplicates removed by record ID.

Imported rows are re-checked and re-cleaned on the way in rather than trusted, because a file can be hand-edited between export and import. A local report holds 250 observations before the oldest roll off.

13

Audio recording you can see happening (browser app)

Recording the demodulated audio is a deliberate button press, marked by a pulsing indicator and a running timer the whole time it is on — never silent capture. The file downloads as a standard audio file you keep separately; it never enters the field report or the stored record. Any single recording stops itself after ten minutes so a forgotten session cannot grow without bound, and compliance with local law stays yours.

14

Offline, bilingual, and nothing phones home

The browser app keeps working once it has loaded, so a basement or a rural site does not end the survey. Every screen, message and band entry runs in English and Spanish with a toggle in the header, and the choice sticks between visits. The Android app declares no network permission at all — the operating system itself will not let it open a connection, so anything it hears is physically unable to leave the handset.

15

Help that works offline, in both languages

Twenty guides in English and twenty in Spanish cover the receiver and its power and permissions, tuning and audio, scans, the finder, device and button libraries, recordings, spreadsheet files, deletion and recovery, and follow the language you chose.

16

The policies travel with the app

The full privacy notice and terms are bundled in the Android app and open from About with no connection, and the same documents are published on the website.

17

Spanish search that forgives accents

Typing a Spanish search term without its accents still finds the article, and the keyboard no longer rewrites what you typed (Android candidate 1.0.4/code5).

Proof

Numbers we can stand behind.

Every figure below comes from the product's own release record or test suite, not from a marketing estimate.

55radio allocations in the built-in band reference, each carrying a caution level
16one-tap band presets in the Android app, from broadcast FM to satellite navigation
14survey presets in the browser app
8capability rows the browser app's device check reports on
36automated checks the browser app must pass, including the receive-only rule
5regression tests locking the three receiver faults found on the bench so they cannot return
9unit tests over the Android signal-processing core
428phrases the browser app carries in both English and Spanish, enforced so neither can go missing
  • Both apps ship complete in English and Spanish, enforced so a phrase cannot ship in one language and go missing in the other.
  • It runs on an inexpensive USB receiver you can buy from any electronics retailer rather than a bench instrument, and the setup guide names the exact adapter cable most people get wrong the first time.

Where it runs

Surfaces and status.

WEB
Web · Current release, last updated 2026-09-07Live, with a bilingual help center, privacy notice and terms added on 2026-09-07.bandsight.autosecurelogin.com
AND
Android · 1.0.4/code5Signed candidate dated 2026-09-08; not in Google Play and no public rollout is claimed, with store listing creation and a physical receiver check of this exact build still pending.

Status as of 2026-09-08. The browser app answers at https://bandsight.autosecurelogin.com/ — verified returning 200 on 2026-09-02, with the main app, the band reference and the hardware guide all responding and each page served byte-for-byte identical to the current source, last updated 2026-08-20.

The receiver was validated against real hardware on 2026-08-18 and confirmed tuning, streaming and playing live broadcast FM audio in a browser on 2026-08-19. The native Android app is version 1.0.0, built and signed on 2026-08-19, hardware-verified on a real handset on 2026-08-20, and its capture features validated against a real 315 MHz car fob on 2026-08-21.

What is new

Recent progress.

This product ships often. The most recent verified changes, newest first.

  • Signed Android candidate 1.0.4/code5 superseded 1.0.3 on 2026-09-08: Spanish help searches now match with accents omitted and the keyboard no longer rewrites search terms. All 35 unit tests and all 40 help articles passed on the signed build on two Android versions.

  • The website's help center, privacy notice and terms went live on 2026-09-07 with the same twenty guides in each language, and a broken install icon was regenerated and verified live the same day.

  • On 2026-09-06 a browser app release and signed Android candidate 1.0.2/code 3 followed an audit that repaired storage preservation, repeatable imports, recording export, deletion confirmation, bilingual layout and privacy disclosures. The candidate also fixed receiver status messages that stayed in English after choosing Spanish.

  • Signed Android candidate 1.0.3 / code 4 added twenty searchable offline help guides in each of English and Spanish, with the full privacy notice and terms bundled and opened from About; the app still declares no network permission and remains receive-only.

  • /19 — the receiver stopped being theory. It was driven against a real USB receiver, three genuine faults in how it talked to the hardware were found and fixed, and it was confirmed tuning, streaming and playing live broadcast FM audio in a browser. Opt-in audio recording landed the same week, validated against live FM, along with several receiver interface fixes: controls now grey out when the receiver is stopped instead of erroring, a normal stop no longer raises a false alarm, and pressing Start before a receiver is selected now opens the hardware picker instead of dead-ending.

  • a fully native Android app shipped at version 1.0.0, built and signed. It drives the same receiver directly and processes everything on the handset, with no network permission at all.

  • a large Android release, verified on a real handset: unit selection, a mode-aware band sweep with sixteen one-tap presets, saved stations with favourites and search, the signal finder with strength meter, peak hold, warmer-colder beeps and compass bearing, a reorganised Manual and Scan layout, and clear referrals when a band is out of the receiver's reach. The browser app was redeployed the same day and that is the release serving now.

  • device capture shipped: burst capture on the four unlicensed sub-GHz bands with an all-bands sweep that locks onto whichever band goes active, a device library where you name a device, name its buttons and learn each button by pressing the fob, saved signals, and spreadsheet import and export. Validated against a real 315 MHz rolling-code car fob.

Pricing

Pricing for BandSight is quoted after a short conversation about your situation, because the right scope differs from one team to the next. There is no charge for that conversation.

Ask about pricing
Honest by default. We publish the standard each product meets and the limits of each safeguard next to the feature, not in a footnote. If you cannot find an answer on this page, the assistant in the corner reads only these pages and will say so rather than guess.

Questions buyers ask

Straight answers.

What does it cost?

Pricing is not published yet. The browser app is reachable at bandsight.autosecurelogin.com today. The USB receiver and adapter cable are a separate purchase from a normal electronics retailer — we name a specific starter kit and cable in the setup guide, and the links carry no affiliate tracking, so we make nothing on what you buy.

What hardware do I actually need?

A USB radio receiver of the common RTL-SDR type, and a short USB-C to USB-A adapter cable so the receiver's weight is not hanging off your phone port. Some handsets also need a powered hub to supply steady power. The setup guide names a specific receiver bundle and a specific cable in the right connection order, because a rigid plug adapter is the usual reason a first attempt fails.

What is in the browser app versus the Android app?

The browser app is live now and has the device capability check, the receiver with spectrum, waterfall and audio, fourteen survey presets, survey sessions with a stated scope, expected-versus-found, baseline comparison, export, import and merge, and the 55-entry band reference. The Android app adds the field tools: band sweep with sixteen presets, saved stations, the signal finder with compass bearing, and fob and sensor capture with a device library. The Android app is installed directly on request rather than from the Play Store.

We already use desktop SDR software. Why would we switch?

You probably should not switch — you should use both. Desktop software is excellent at showing you a waterfall. BandSight is built for what happens after: a named site, a stated authorization scope, a declared list of what should be radiating so anything else is flagged, a comparison against an earlier survey, and an export. If your work ends at "I saw a signal," what you have is fine. If someone later asks you to prove what you checked and when, it is not.

Where does my data go?

Nowhere. Nothing is uploaded. Browser records stay on the machine you used, and the Android app declares no network permission at all, so it cannot open a connection even in principle. Audio recording is an explicit button press with a visible indicator, saved as a separate file that never enters the report. Location tagging is currently switched off by the site's own privacy headers, so observations are logged without coordinates.

What happens to my surveys if we stop paying, or you disappear?

Nothing is held hostage. Your records are already on your own device, not held by us, and export is a button. Exports are a plain spreadsheet or a structured data file you can open in anything — no proprietary format, nothing to unlock. Losing access to the app does not cost you a single observation you have already exported.

Is it ready to use on a real job?

Yes. The browser app is live and serving now, and the receiver was proven against real hardware rather than written and hoped for. The native Android app is a signed 1.0.0 release, hardware-verified on a real handset. Read the limits first, though — the tuning ceiling, the Android-only feature split and the rolling-code caveat are the three that most often decide whether BandSight fits the job in front of you.

Is any of this legal?

BandSight measures the presence and strength of radio energy, which is lawful RF measurement in the United States, and that is all this receiver does. It never transmits, never jams, and never decodes the content of private communications. The band reference marks restricted allocations so you can recognise and avoid them. Rules vary by country and change, so check locally, and work only on your own equipment, on public broadcasts, or with written authorization. This is guidance, not legal advice.

Do we have to migrate anything to get started?

No. There is nothing to import and no account to set up before your first survey — open it, run the device check, and you have a record. If you already have earlier BandSight surveys you can load one as a baseline to see what has changed, and two people can merge their files into one record with duplicates removed automatically.

What should I know before I rely on it?

We would rather you hear this from us than discover it later. As of 2026-09-08:

  • You need hardware. A phone on its own cannot survey the spectrum. You need an inexpensive USB radio receiver of the common RTL-SDR type and a USB-C adapter cable, and neither is included — the setup guide names a specific starter kit and cable.
  • The band sweep, saved stations, the signal finder and fob capture are in the Android app only. The browser app has the device check, the receiver, survey sessions with a stated scope, expected-versus-found, baseline comparison, export and merge, and the 55-entry band reference — it does not sweep a band or capture fobs.
  • The Android app is a signed 1.0.0 release installed directly on request. It is available direct from us while its store listing is prepared.
  • The supported receiver tunes roughly 24 MHz to 1766 MHz. Wi-Fi, Bluetooth and the higher cellular bands sit above that ceiling and this receiver cannot sense them at all. Shortwave, AM medium wave and longwave sit below it and need an upconverter or a different receiver. BandSight tells you this rather than showing a blank display.
  • The browser receiver needs a current Chrome-family browser over a secure connection. On Windows there is a one-time step to hand the receiver over to the browser before it will open.
  • Only one app or browser tab can hold the receiver at a time. If a second one tries, BandSight reports the device as in use rather than blaming the hardware or the antenna.
  • Location tagging is switched off on the live site. The browser app can attach an approximate, rounded position to an observation, but the site's own privacy headers currently block the browser location call, so in practice observations are logged without coordinates. The device check still lists location as present, which overstates it. Use the site name and authorization scope you enter when you open the session, which is what a client report needs anyway.
  • Device capture fingerprints a transmitter by its signal timing. It does not decrypt rolling codes, and on real captures the fixed portion of a rolling-code car fob does not yet resolve to the same identifier across sessions — good enough to confirm a remote is transmitting and to compare captures, not yet good enough to be a reliable device ID. A protocol-exact decoder is the next piece of work.
  • Sensors that shift frequency rather than switching on and off show up as a strong carrier but may not slice into clean bits in this version.
  • Records live on the device. Clear the browser data or lose the handset and they are gone — export anything you need to keep. A local report holds 250 observations before the oldest roll off.

Know what's transmitting on a site you're responsible for.

See what is actually transmitting around you — a receive-only radio survey run from a phone and a low-cost USB receiver.

Prefer email? contact@autosecurelogin.com

Help / Ayuda