The phrase “location-based dating” usually creates an immediate concern.
Can someone see where I am?
Can they see where I go?
Can they figure out my schedule?
Those concerns are valid because many location products are designed around real-time proximity.
Usual is not.
The product does not need to show who is nearby right now.
It does not need to reveal whether two people visited a place on the same day.
It does not need to display a map of users around a venue.
Usual is built around recurring place overlap.
That means identifying that two people have independently approved the same place or type of place as part of their lives.
For example, two people may regularly visit the same climbing gym.
One goes before work. The other goes on weekends.
They may never have been there simultaneously.
The useful signal is not that their coordinates once overlapped.
The useful signal is that climbing is a meaningful part of both lives and that they participate in the same local community.
That context can be used without exposing a schedule.
Before a match, Usual can say:
You both regularly visit a climbing gym.
It does not need to say:
This person goes to Central Rock on Tuesdays at 6:30 p.m.
The first statement creates context.
The second creates risk.
A privacy-first system should also prevent venue searching.
A user should never be able to select a restaurant, apartment building, workplace, school, gym, or neighborhood and browse a list of people associated with it.
Matching should happen privately inside the system.
Users should also control which places participate.
A detected place should remain private until the user approves it.
Home, work, medical facilities, schools, treatment centers, shelters, places of worship, and other sensitive destinations should never become match signals.
Location matching can be useful.
Location exposure is not required.
The distinction should not be a marketing claim added after the product is built.
It should determine how the product is designed from the beginning.