How Radar finds relevant people
Radar uses recent server-side location to determine who is sufficiently close for the selected radius. The interface does not become a public map: another person receives only softened distance context that is enough to decide whether contact might be relevant.
Results depend on both sides. A profile must be available, online, within mutual radius and compatible with basic settings, with no hiding or blocking between the accounts. The list can therefore change as people move, refresh status and adjust their choices.
Location permission is needed to calculate proximity, but it is not consent to meet or share an address. Radar answers only “who may currently be nearby and open to contact”; a separate Knock is required to begin.
What Radar protects and simplifies
Approximate distance
The interface communicates proximity without publishing exact metres, coordinates or a home address.
Mutual radius
Discovery considers both people’s settings, not only one person’s wish to see another.
Current availability
Radar includes people who have refreshed location and are currently open to connecting.
How to use Radar
-
Step 1
Allow location access
Give the browser or app location access only while using the service.
-
Step 2
Choose a radius
Set a distance available on your plan and avoid expanding it without a reason.
-
Step 3
Refresh availability
Turn visibility on when open to contact, then go offline when leaving or becoming busy.
-
Step 4
Review the profile
Read intents, interests, language and bio before a Knock instead of relying only on proximity.
Questions about Radar
Does Radar include an exact map of people?
No. It does not show a public user point or precise coordinates; it uses approximate proximity context.
Why can Radar be empty?
There may be no simultaneously available profiles within mutual radius, or current location may not have refreshed yet.