NearLens Questions

Smart glasses nearby:
Frequently Asked Questions

How to check for smart glasses nearby, interpret compatible signals, and understand the app's limits.

NearLens smart-glasses presence illustration

What NearLens does, and what it does not

Product transparency

Coverage and reliability

NearLens recognises only Bluetooth identifiers and observable signal patterns that its current recognition data can evaluate. It is not a universal detector, and no result is proof that smart glasses are absent.

Recognition coverage
Recognition depends on a supported combination of observable identifiers and signal characteristics evaluated by the installed rules. New or undocumented devices may not produce a match. A match is not authentication of a model or camera capability.
Known sources of false positives
Headsets, earbuds, speakers, and other products from the same manufacturers may expose related Bluetooth information. NearLens reports signal compatibility, not visual proof of a specific device.
Known reasons for missed detections
A device cannot be detected when it is not broadcasting, Bluetooth is off, it is asleep, its advertisement is suppressed, or its identifiers and signal pattern are not yet recognised.
Distance and testing
Distance is estimated from signal strength and can change with walls, crowds, interference, and device behaviour. Field observations are not a controlled accuracy benchmark, so NearLens does not publish an unsupported accuracy rate.

What confidence means

Confidence describes the strength of a match between the received Bluetooth information and NearLens's recognition rules. It is not a measured probability, an authentication result or a recording score. Even a high-confidence result can be wrong.

High confidence
The signal matches a stronger recognition rule for a supported device profile.
Medium confidence
The available information supports a match but leaves more uncertainty.
Low confidence
The match is partial or ambiguous and should be treated cautiously.

The basics

NearLens can help you check for smart glasses nearby by recognising compatible Bluetooth broadcasts associated with supported devices. Nearby glasses that do not expose a recognised signal may not appear.

A match does not identify the wearer, locate the device precisely or independently confirm recording; no result does not establish that camera-equipped glasses are absent.

NearLens scans for nearby Bluetooth Low Energy signals that match its installed smart-glasses recognition rules. It can show compatible device observations, rough distance estimates and the confidence behind a match.

It can also display supported privacy signals voluntarily broadcast by cooperating devices. These observations provide awareness, not proof of a particular model, a person's identity or recording activity.

No. NearLens is not about the people who wear smart glasses, and most of them are not doing anything wrong. Many use them for music, calls, navigation, translation, or accessibility.

NearLens observes Bluetooth signals, not verified identities. It does not capture photos or audio, and it does not tell anyone what to do. The Terms of Use prohibit using NearLens to approach, confront, or target anyone.

Some products share Bluetooth identifiers, names or service patterns with camera-equipped devices. NearLens excludes certain known camera-free models, but its rules cannot distinguish every product or firmware version.

A result, including a high-confidence match, is not independent proof that the device has a camera. If a camera-free model appears, contact hello@marcosrezende.com with the model and app version. Do not include personal information about its owner.

NearLens recognises compatible Bluetooth identifiers and signal patterns using the recognition data installed with the app. An exact model listing is not always required: shared recognised information may produce a general classification rather than a model-specific identification. It is not a universal detector.

Some devices do not expose a detectable BLE advertisement in the conditions where you are scanning. Others broadcast information the installed rules do not recognise. Those devices may be nearby without producing a result.

Usually, NearLens can recognise only a compatible device signal, not its recording state.

Some cooperating devices voluntarily broadcast camera or microphone status through PMSG, a Bluetooth privacy-signal convention. NearLens can display these reports, but cannot independently verify them. Indicators inferred from a Bluetooth name are weaker evidence than an explicit protocol message.

No recording signal does not mean that a device is not recording.

NearLens does not identify or authenticate a device's owner. It does not use faces, accounts, location maps or a shared detection feed to identify people.

Bluetooth devices may advertise names or identifiers, which are not verified identities and can be changed or copied. A device name is not proof of who owns or carries it.

In a small space, a nearby signal may still allow someone to make assumptions about others. Do not use NearLens to identify, follow, confront or target people.

An observation is only useful if it helps you make a decision. NearLens cannot determine someone's intentions or confirm that they are recording you. If an uncertain signal would not change what you do, the app may not be useful in that situation.

NearLens does not prevent recording or replace consent. It provides context, not a guarantee of privacy or safety.

Most people wearing smart glasses are not recording anyone. But when a camera is on a face, people nearby have no easy way to know it is there.

NearLens offers compatible Bluetooth observations to help inform a decision. Those observations do not independently establish that a camera is present or recording.

Knowing that a compatible device may be nearby lets you decide what feels right for you, like staying, moving, or asking venue staff about their policy.

The app provides compatible device observations and supported device-reported privacy states, not verified identities or proof of recording.

The honest position is that NearLens is useful and insufficient. The structural fix is consent design at the platform level, not a detection app. NearLens treats a symptom, and it does not pretend otherwise.

Recording indicators vary by model. Some smart glasses use an external light or other cue, but a bystander may not notice it because of distance, lighting, viewing angle or how the device is worn.

NearLens does not inspect recording lights or verify whether they are working. A Bluetooth observation cannot establish whether a recording indicator is visible or whether recording is taking place.

Check the manufacturer's documentation for the specific model. Do not assume that all smart glasses use the same indicator or recording behaviour.

NearLens recognition data includes observable identifiers or verified signal signatures associated with Ray-Ban Meta, Oakley Meta, Snap Spectacles, and compatible EssilorLuxottica smart eyewear.

Coverage changes as manufacturers release new products or update Bluetooth behaviour. Recognition-data revisions are included in app updates. A model not individually listed may still produce a general classification if it shares identifiers or signal patterns that the installed version recognises.

Yes, nearby-device awareness has privacy implications. Even without identifying an owner, a Bluetooth observation can lead to assumptions about people in a small space.

NearLens does not automatically upload detection history or provide a shared detection feed. Observations remain local unless you choose to copy, export or share information. Destination apps or recipients may then store or disclose that content.

The app does not authenticate owners or independently verify device-reported activity. Use observations cautiously and never to follow, confront or target another person.

Your data

No. In the current implementation, the conversation is held in memory for the app session rather than saved as a persistent chat archive. Switching tabs does not by itself clear it.

Settings includes an option to clear the conversation. Copies or content you share may remain in the destination app or with the recipient.

Detection history has separate storage and deletion controls. Clearing the conversation does not by itself delete the detection log.

The NearLens app does not use analytics, telemetry, advertising, or account data. Bluetooth observations and detection history are stored locally and are not automatically uploaded to NearLens. If you choose to copy, export or share information, the selected content may leave the app.

The website is separate and uses optional Umami Cloud analytics only after consent. It also uses one necessary cookie to remember that choice.

NearLens requests Bluetooth access to scan for nearby BLE signals. iOS does not require location authorisation for Core Bluetooth scanning.

NearLens does not need GPS coordinates for detection.

The available local history is limited to 500 entries. Observations older than 90 days are excluded when history is loaded or updated.

These limits describe application-level history handling, not a guaranteed background deletion schedule.

You can clear saved history from within the app. Removing the app deletes its local app data, but does not remove copies you previously exported or shared. Device backups are governed by your iOS backup settings.

Local detection history is enabled by default in the current version. It is stored on your device and is not automatically uploaded to NearLens.

You can clear your history or turn off history saving in Settings. Turning off history saving also clears the saved history after confirmation.

“Ask about your local history” is a separate setting, also enabled by default in the current version. It controls whether that history can be used for on-device questions. Previously saved choices are preserved for both settings.

If you choose to copy, export or share information, the selected content may become available to the destination app, service or recipient. Review the information before sharing it.

No. NearLens detects nearby signals using Bluetooth Low Energy (BLE), so scanning needs Bluetooth turned on and the required permissions, not Wi-Fi or mobile data. Keep the app active to scan.

Privacy Intelligence also runs locally. With saved detection history to analyse, you can ask questions in natural language and receive on-device answers without an internet connection.

Questions require iOS 26 or later, a compatible iPhone, Apple Intelligence enabled and available on the device, and “Ask about your local history” enabled in Settings. There is no hosted-model fallback.

This website, unlike the app's scanning and local analysis, needs an internet connection.

No. NearLens observes Bluetooth Low Energy advertisements that nearby devices make available. It does not pair with detected devices, connect to read their services, or access their photos, audio or messages.

Not every Bluetooth device advertises continuously, and some stop or change their advertisements when connected to another device. NearLens cannot observe information that is not available in the signals it receives.

Detection and accuracy

NearLens checks for Bluetooth advertisements in scan windows, not through uninterrupted observation. The current default interval is two seconds, but a short camera or microphone signal can still begin and end between windows.

Radio interference, iOS advertisement delivery and the other device's behaviour can also affect reception. A shorter scan interval does not guarantee that every photo or recording event will be detected.

No. An alert may indicate that NearLens first observed an active state or observed a change from an inactive to an active state.

Repeated photos may share one continuous active flag, and brief changes can be missed. NearLens does not provide a reliable per-photo count. The time shown is when the app observed the signal, not a verified capture time.

Encounters describe nearby-device observations grouped by the app. Privacy Signals describe supported camera or microphone states observed through PMSG.

One device can generate several encounters or state observations. Neither view is a verified count of distinct devices, people, photos or recordings.

A privacy signal may also come from something other than glasses, so its presence does not establish the device type.

No. The list includes reference information as well as entries supported by executable recognition rules. A manufacturer or product appearing in the catalogue does not mean that every model or firmware version can be detected.

Recognition depends on the information actually broadcast by the device and the rules installed with your app version. A company identifier or product name alone does not establish camera capability.

It expands the scan list to include other Bluetooth Low Energy devices observed during the scan, not just matches for smart-glasses or supported privacy signals.

An entry in this list is not evidence that the device has a camera, is recording or belongs to a particular person. Some devices may not appear because they are not advertising a detectable signal.

Yes. Advertised names, identifiers and PMSG status data are not proof of authenticity. Another device can copy them, and an advertiser can report an inaccurate or outdated state.

NearLens distinguishes supported protocol data from weaker name-based inference, but neither authenticates the sender or proves that recording is taking place.

NearLens recognition data is reviewed periodically, and revisions are included in app updates. It does not synchronise continuously with an online device registry. Keeping the app updated gives you the recognition data included in that release.

New models or changes to existing devices may not be recognised immediately. Scanning continues to work offline using the recognition data already installed.

Sometimes. A model that is not individually listed may still broadcast identifiers or signal patterns that NearLens recognises. The app may return a general classification rather than identify the exact model.

Bluetooth company identifiers come from a public registry maintained by the Bluetooth SIG. They identify registered organisations, not specific models or camera capabilities. A general match does not confirm that a device is camera-equipped or recording.

If the available signal does not match NearLens recognition rules, it may not produce a result. No result is not proof that smart glasses are absent.

NearLens listens for Bluetooth Low Energy advertising packets that a device makes visible nearby. This provides Bluetooth presence awareness, not person tracking, a map or proof of recording. A missing result only means that no compatible signal was observed.

It compares observable identifiers and signal fields against its installed recognition data. A match may support a specific profile or only a general classification, depending on the available evidence. Receiving a signal does not by itself identify the exact model or confirm camera capability. A device that is not advertising a detectable signal cannot be detected this way.

Bluetooth devices can rotate the address they use in advertising packets. The same pair of glasses can therefore appear as several advertising identities over time, while two entries cannot safely be assumed to be two separate devices.

NearLens reports recognised signals for awareness, not a count of distinct glasses or people.

No. NearLens does not see where another device sends captured images or audio.

A Bluetooth advertising signal does not reveal the cloud provider, processing location, or retention policy chosen by the wearer. Those details require the manufacturer's documentation or independent testing, not a nearby-device scan.

Confidence describes the strength of a match between the received Bluetooth information and NearLens's recognition rules. It is not a measured probability, an authentication result or a recording score.

High: the signal matches a stronger recognition rule for a supported device profile.

Medium: the available information supports a match but leaves more uncertainty.

Low: the match is partial or ambiguous and should be treated cautiously.

Even a high-confidence result can be wrong. Advertised names, company identifiers and service UUIDs can be shared by different products or copied by another device.

NearLens needs two things: a detectable Bluetooth signal and an identifier or verified signal signature that the app recognises.

Some devices do not expose a detectable BLE advertisement in the conditions where you are scanning. Others use identifiers or payloads the app does not recognise. No result means that no compatible signal was observed. It is not proof that no camera-equipped glasses are nearby.

No. A device that is not broadcasting cannot be detected by any Bluetooth scanner. NearLens sees no more than the glasses choose to announce.

The same applies to walls and direction. Signal strength gives a rough distance, not a location.

NearLens has been used in field observations, but those observations are not a controlled accuracy benchmark.

Detection depends on a compatible Bluetooth broadcast, recognition data, distance, interference, and device behaviour. No result is proof that no smart glasses are present, and a result is not proof of recording.

There is no guaranteed detection range. Reception depends on the device's advertising behaviour, signal power, your iPhone, obstacles, interference and the surrounding environment.

NearLens converts received signal strength into rough distance bands. These are estimates, not measured positions. A weaker signal does not reliably mean that a device is farther away, and a stronger signal does not prove it is in the same room.

Distance estimates should not be used to locate a device or identify its wearer.

Sometimes. The device must broadcast a detectable Bluetooth signal that matches NearLens recognition rules. An exact model listing is not always required, but a general classification does not confirm the model or whether it has a camera.

Some devices do not expose a detectable BLE advertisement in the conditions where you are scanning. Others broadcast information the app does not recognise. In those cases, the device may not be detected even if it is nearby.

Using the app

A visible observation does not always produce a new alert. The app may already have alerted you about that recognised device or state, or alerts may be snoozed.

Check the vibration and notification preferences in NearLens Settings and the notification permissions and delivery settings in iOS.

NearLens does not detect new devices while it is in the background. Receiving an alert also does not prove that every nearby signal was observed.

The local report uses calculations over saved observations and does not require a language model.

Natural-language questions are a separate feature. They require a compatible iPhone, iOS 26 or later, Apple Intelligence enabled and available, saved detection history and the “Ask about your local history” setting enabled.

If the local model is unavailable, NearLens does not send the question or history to a hosted model instead.

The demo uses sample data to show supported privacy-signal states and how the interface presents them. Changing a demo state updates the sample device card and may show a simulated recording alert.

The demo does not scan for a real device, transmit a privacy preference, send a notification, trigger vibration or save a detection event.

PMSG is short for “P.M. Smart Glasses”, a project by Paul Stefaan Mooij. In NearLens, “PMSG privacy signals” refers to the project's documented Bluetooth Low Energy (BLE) convention for sharing privacy-related states.

Compatible devices can voluntarily announce camera or microphone activity, or supported privacy preferences. NearLens interprets supported announcements without pairing with the device. A preference-only beacon is not treated as a camera or microphone activity event.

These are device claims, not independently verified evidence. A signal does not prove recording, its absence does not prove that no camera is nearby, and NearLens does not block recording or broadcast do-not-record requests.

Read the PMSG project documentation and its Bluetooth privacy-signal convention.

A privacy signal and a recognised smart-glasses profile are different findings.

NearLens may receive a PMSG announcement from a device whose manufacturer or model it cannot identify. The protocol can also be used by devices other than glasses.

A PMSG signal alone is not proof that camera-equipped glasses are nearby.

No. NearLens does not disable nearby cameras or microphones, and it does not currently broadcast a do-not-record preference.

Its PMSG interpretation can recognise supported do-not-record declarations and claims that a device honours them. A preference-only beacon is not treated as evidence of a recording device or added as a camera or microphone activity event.

A device saying that it honours such requests does not confirm that it received any particular request or stopped recording. NearLens cannot independently verify compliance.

No. It is a record of the privacy states NearLens observed while scanning, not a complete history of another device’s activity.

Brief events, interruptions, missing broadcasts, and time spent outside the app can leave gaps. NearLens cannot reliably determine how many photos were taken or the exact duration of a recording from those observations.

A missing event is not evidence that no recording occurred.

No. NearLens scans while the app is open and active. Scanning pauses when you switch to another app or lock your iPhone, and resumes when you return unless you paused it manually.

Switching between Scan, Intelligence, Logs, and Settings within NearLens does not stop scanning.

This keeps scanning visible and under your control. Background monitoring is not currently supported, so NearLens cannot alert you to new detections while the app is in the background.

Privacy Intelligence summarises your local detection history, including observed brands, activity periods, and repeat encounters.

On compatible iPhones, you can also ask questions about that history using Apple Intelligence. Questions and answers are processed on your device, without uploading your detection history to NearLens. Answers may be inaccurate and should be checked against the underlying observations.

Questions require saved detection history, an available Apple Intelligence model, and “Ask about your local history” enabled in Settings.

NearLens does not substitute a hosted model when local generation is unavailable. Questions use a limited local context that excludes device names and Bluetooth addresses. Manufacturer reference entries are not all executable detection rules, and observed encounters are not a verified count of distinct people.

The Privacy Intelligence report summarises local detection history, including frequently observed brands, active time periods, repeat encounters, and cluster events.

The report can be exported. On compatible iPhones, you can also ask on-device questions about saved history using Apple Intelligence, with “Ask about your local history” enabled in Settings.

NearLens requires iOS 17 or later.

Natural-language questions in Privacy Intelligence require iOS 26 or later, an Apple Intelligence-compatible iPhone, and Apple Intelligence enabled and available on that device.

Bluetooth scanning does not require Apple Intelligence.

Yes. You can snooze alerts for a detected device for 15 minutes, one hour or the rest of the scan session.

Snoozing suppresses alerts for that recognised device identity; it does not stop scanning or erase its observations. Bluetooth identity changes can limit how reliably the app recognises it as the same device.

To pause scanning itself, use Pause on the Scan screen. Vibration and notification preferences are managed separately in Settings.

A detection is not an accusation. It means a compatible signal is nearby, not that anyone is recording or doing anything wrong.

Treat it as context, not evidence about a person. In a sensitive setting, you can ask about recording practices or check the venue's policy. Do not use a detection alone to accuse someone of recording.

An alert is not an instruction to run or confront anyone. NearLens observed a compatible Bluetooth signal nearby.

Pause and choose what makes sense: move to another seat or room, avoid a sensitive conversation, ask venue staff about their recording policy, or carry on. If someone is making you feel unsafe, prioritise your safety and seek help from staff or local emergency services.

NearLens does not identify the owner or independently verify recording. A PMSG message may report camera or microphone activity, but it remains an unverified device claim. Treat any alert as information for your decision, not proof that someone did something wrong.

NearLens is free, with no subscription, advertising or paid feature tier. The app does not require an account or automatically upload your local detection history to NearLens.

Android is not currently supported. The current experience is designed for iPhone.

NearLens focuses on recognising Bluetooth signals associated with camera-capable smart glasses. General-purpose Bluetooth scanners list every device in range without smart-glasses classification or confidence labels.

Other smart-glasses detector apps also exist. NearLens should be compared by its documented capabilities and limits, not by an exclusivity claim.

No. There is no paid tier and no features held back. Every user gets the same app.

Being free does not change what the app can and cannot detect.