Authorized-use guardrail
DarkDar is intended for owned, managed, consent-based, or otherwise authorized environments. Unmatched devices remain redacted, privacy-protected, and limited.
Privacy and limits
Powerful BLE awareness
without privacy theater.
DarkDar is designed for authorized environments. It does not identify people, does not bypass Bluetooth privacy protections, and does not claim exact positioning from RSSI alone.
Operating principles
Local-first, consent-based, confidence-driven.
No de-anonymization promise
The product uses authorized probabilistic identity correlation. It does not claim to defeat randomized addresses or operating-system privacy controls.
Local data containment
Sessions, point clouds, registry data, and exports are local by default. Remote sync or telemetry should require explicit opt-in, and exports should be intentional operator actions.
Uncertainty is visible
RSSI-only estimates are shown as range bands, confidence, and uncertainty, not exact indoor coordinates from a single collector.
Identity handling
Use “registered,” “likely,” “possible,” “unknown,” and “privacy-protected.”
DarkDar may classify or correlate devices using user-registered labels, paired or authorized records where available, service UUIDs, manufacturer data, appearance values, local names when present, service data, advertising behavior, and session-local similarity. Those signals are evidence, not proof of a person or owner.
Public copy rule: say “authorized probabilistic identity correlation,” not “de-anonymization,” “privacy bypass,” or “stalker identified.”
Technical limits
Honest constraints make DarkDar more credible.
- Web Bluetooth is not a replacement for native BLE collectors.
- iOS and iPadOS background scanning is bounded by platform behavior and app state.
- RSSI is affected by distance, walls, reflections, body blocking, antenna orientation, chipset behavior, transmit power, and scan scheduling.
- Single-collector RSSI mode provides proximity and range uncertainty, not precise x/y coordinates.
- AoA, AoD, Channel Sounding, and multi-anchor workflows require compatible hardware and calibration.