NearSight Privacy Policy

Effective date: 30 June 2026. Last updated: 20 October 2026.

NearSight listens for the Bluetooth Low Energy (BLE) advertisements that nearby devices broadcast and decodes what those devices are. This policy explains what NearSight does and does not collect, and your choices.

Local-first by default. Scanning runs entirely on your device. NearSight collects nothing off-device unless you turn on AI insights and/or telemetry — both are opt-in and off until you choose them, and the app is fully functional with both left off.

NearSight doesn’t detect every nearby device — see the Disclaimer & Coverage Notice for what it can and can’t see.

1. Who we are

NearSight (“we”) is the data controller for any data described below. For privacy requests, contact privacy@nearsight.one.

2. What we collect (only when you opt in)

When you enable AI insights and/or telemetry, NearSight may send:

Data	What it is	Linked to you?	Used for tracking?
Anonymous install ID	A random UUID generated on first opt-in to group your uploads. Not your account, name, or device serial.	No	No
BLE advertisement data	The advertisement payloads NearSight is analyzing, which can include identifiers broadcast by nearby third-party devices, and the product names those devices broadcast (see section 6).	No	No
App/device diagnostics	App version/build, device model, iOS version.	No	No

These rows mirror the app’s Apple privacy manifest and App Store privacy “nutrition labels.”

3. What we do NOT collect

No account, no name or email, no precise location, no contacts, and no cross-app or cross-site tracking. We do not sell data. NearSight never reads your phone’s location for telemetry. A few nearby devices, such as some dash cams, broadcast their own GPS position; NearSight rounds any such position down to whole degrees (roughly 100 km) before upload.

4. Why we process it (purposes & legal bases)

Provide AI insights you request — performance of the feature you turned on (GDPR Art. 6(1)(b)).
Improve device recognition / parsers — our legitimate interest, exercised only under your opt-in consent (Art. 6(1)(a)/(f)).

5. Who receives it

Cloudflare — hosts the telemetry endpoint and this page.
Your chosen AI provider (Anthropic or OpenAI) — only when AI is on and using a cloud provider, and using your own API key. On-device AI sends nothing to a provider. See their policies: Anthropic, OpenAI.

6. Bystander (third-party) data

BLE advertisements from bystander devices around you may be captured incidentally. We minimize this:

Device identifiers are replaced with digests keyed to your install, so the same device can’t be matched across different phones or a reinstall.
Names that devices broadcast are uploaded only when they match a known product name (for example “JBL Flip 5”), with any per-unit serial number masked. Other names, including names people give their own devices, are not uploaded. Device names are included by default; turn off “Include device names” in Settings → Telemetry to leave them out.
Nothing is linked to a person’s identity.

We use this data only to recognize device types, never to identify or track an individual.

7. Retention & deletion

You are always in control of telemetry you’ve contributed.

Delete in the app (recommended): Settings → Telemetry → “Delete my telemetry data” clears the app’s local data, issues a fresh anonymous install ID — severing future uploads from anything you sent before — and requests deletion of the telemetry you previously uploaded. Server-side data marked for deletion is removed without undue delay.
Request deletion by email: contact privacy@nearsight.one with your install ID (shown in Settings → Telemetry) — a fallback if the in-app request can’t reach the server. We then mark your uploaded data for deletion as above.

Diagnostic data is retained only as long as needed to operate and improve the service.

8. Your rights

Subject to applicable law (incl. GDPR/UK GDPR and CCPA), you may request access to, correction of, deletion of, or object to our processing of your data. Exercise these via privacy@nearsight.one.

9. Children

NearSight is not directed to children under 13 (or the equivalent age in your region) and we do not knowingly collect their data.

10. Changes

We’ll update this page and its effective date when this policy changes.

See also the NearSight Disclaimer & Coverage Notice — what NearSight can and can’t detect, and why it is not a safety or security device.