How Droozi Decides That Two Plans Overlap
Droozi compares places and dates you have saved. A new future location can match a contact's location when the dates intersect and the places are within 10 kilometres or have the same address text.
Future Location Sharing
How Droozi checks new future locations for nearby contacts: distance or matching addresses, intersecting dates, audience controls, and the limits of editing an existing one.
The rule, stated plainly
For eligible contacts, the dates must intersect and the places must either be within 10 kilometres or have identical address text after spaces at the ends and letter case are ignored. A saved Home location can also qualify without a bounded trip date range.
The distance check uses the two saved coordinates. Two future locations more than 10 kilometres apart can still match if their address text is identical. If their addresses differ, being in the same metropolitan area alone does not produce a match.
The dates do not need to be identical. If you are in Chicago from the 4th to the 9th and a contact is there from the 8th to the 12th, the shared dates satisfy that part of the check.
When the check runs
Creating a new future location triggers the comparison. The create flow also checks when it replaces an existing Home location. Ordinary edits to an existing future location use a separate update flow that does not run the overlap check.
If two eligible friends create future locations in Denver for the same week, the second creation can find the first. Editing an existing future location into those dates does not trigger a fresh alert. There is no periodic sweep that guarantees a later notification for that edit.
The comparison uses saved plans, not a live GPS position. Notification delivery also depends on account settings and device permissions.
Who is actually in the candidate pool
The candidate pool contains your accepted friends and contacts you saved yourself. Someone saving you as a contact does not, by itself, add them to the candidates checked when you create a future location.
Your new future location's audience filters candidates using the categories you assigned them: All contacts, Personal, Work, or Personal + Work. For accepted friends, the check also respects the other person's audience and how they categorized you.
Droozi creates overlap notifications for the person who created it and matched people with Droozi accounts, subject to notification preferences. A saved contact without an app account cannot receive an app notification. An alert can open the relevant profile or people list on the map.
What the rule does not give you
There is no dedicated screen that recomputes and lists all current overlaps. You can revisit retained overlap alerts in Notifications after dismissing a device notification. That history records alerts; it does not recompute matches after a plan changes.
Precision is a convention rather than something the app enforces. Droozi is designed around city-level future locations, and that is what the field placeholder suggests, but if you select a specific venue the future location stores that venue. The one exception is your default home location, which is deliberately reduced to a postal-area approximation.
Expired future locations are kept for a limited grace period, currently 30 days, before being purged. Default locations stay until you change or remove them, or delete your account. The Privacy Policy is the authoritative version of both windows.
Sources: Droozi Privacy Policy, sections on location data and retention
How to get more useful matches out of it
Add plans when the dates are useful, so contacts can coordinate in advance. A newly created future location checks existing eligible plans too, so a late addition can still find a match. Editing one later does not guarantee a new alert; check the map or contact the person if timing matters.
Choose a place and audience you are comfortable sharing. More precise coordinates affect the distance check, while identical address text can also produce a match. You do not need to share a sensitive venue to use the feature.
Sort your contacts before you need them. The audience filter is only as good as the categories behind it, and the moment you want a Work-only future location is a bad moment to start filing two hundred people.
Methodology
- We read the location creation and update handlers and the matching helper in the production-branch backend. We recorded the distance and address alternatives, date comparison, candidate pool, and audience checks.
- We checked the mobile edit path and notification history against the production source branch. This was a code review, not a new test of every flow on an installed store build.
- We checked the retention and audience statements in this guide against Droozi's published Privacy Policy on September 10, 2026.
Primary sources
Create your first future location
Download Droozi, add where you will be later, choose who can see it, and turn future overlap into a real plan.
Use cases
Explore the matching planning workflow
Move from this guide into product pages for work travel, conference networking, local meetups, and remote coordination.
Pricing
See what is free today
Confirm that current core planning features are free before deciding whether to install the app.
Events
Browse live event pages
Give readers a direct path from planning advice into public events and RSVP-ready destination pages.
Quick FAQ
Does Droozi check my plans against everyone in the city?
No. The comparison is limited to accepted friends and contacts you saved, with audience checks applied before a match is returned.
Why did I not get an alert when a friend was clearly in the same city?
Check the saved addresses, distance, dates, audiences, and notification settings. Creating a future location runs the check; an ordinary edit does not. Being in the same city is insufficient when addresses differ and the two are more than 10 kilometres apart.
Can I see a list of all my overlaps?
There is no dedicated list of all current matches. Retained overlap alerts are available in Notifications, but that history does not recalculate matches after edits.