Skip to content
Back to BlogGuide5 min read

How Droozi Decides That Two Plans Overlap

Droozi compares saved travel dates and places with your accepted connections. In the US, nearby includes the same metropolitan area and a 20-mile buffer around its boundary. Places within 20 miles can match anywhere.

By the Droozi TeamLast updated

Future Location Sharing

How Droozi checks saved plans for nearby accepted connections using metro areas, a 20-mile radius, overlapping dates and sharing controls, then handles reminders and edits.

The rule, stated plainly

Your saved dates must overlap for a positive amount of time. At least one person must have a dated visit. A home area can match a visitor, but it stops counting while its owner has a saved trip elsewhere, including a private trip.

In the US, both places can be inside the same Census metropolitan area or within 20 miles of that area’s boundary. Each metro is checked separately; neighboring metros are not joined into a larger region. A direct distance of 20 miles or less also qualifies, including outside the US. Matching does not rely on identical address text.

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

Saving or editing a future location, changing home, and syncing a trip schedule a fresh check. Changes to connections, blocks, and location-privacy settings also update eligibility. Background checks recover missed work.

A new match gets a heads-up and a reminder about 24 hours before the shared dates. A recent alert or a trip starting soon combines those alerts. Meaningful date or city changes and cancellations can update previously notified contacts after a short delay. Making a trip private silently removes any alert that no longer qualifies.

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

Notifications match active Droozi accounts with an accepted connection. Pending requests and people you have blocked do not qualify. A contact saved without a registered account remains your own contact record and cannot receive an app notification.

New and already-saved future locations are visible to all contacts. Matching checks accepted connections, blocks, and any privacy settings that apply to other location types, such as home.

Eligible people receive an inbox item; push delivery also depends on their preferences, device registration, and system permissions. A traveler’s simultaneous matches can appear together. An alert opens the existing profile or map flow. The system does not send extra alerts between two of your contacts.

What the rule does not give you

Notifications is a history of alerts, not a live arrival tracker or a complete list of every overlap. It rechecks whether you may still see a travel alert. Deleting an inbox item prevents a delivery retry from recreating it.

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. A default location is manually declared, has its own privacy settings and does not update from your device GPS.

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 while there is still time to coordinate, and update them when your city or dates change. A continuous visit is kept together so repeated saves and duplicate imports do not create a fresh heads-up each time.

Choose a city you are comfortable sharing with all contacts. The matching check uses the saved coordinates and geographic boundaries; you do not need to share a sensitive venue.

Connect before you travel. Overlap notifications require an accepted connection with an active Droozi account; manually saved contacts without accounts cannot receive app alerts.

Methodology

  • We reviewed the shared matching policy, US Census metropolitan boundaries, relationship permissions, home and travel precedence, and destination timezone handling.
  • Automated tests cover concurrent jobs, edits, cancellations, blocked users, deleted notifications, and retries after a device fails. Firebase accepting a push is recorded separately from whether a user reads the inbox item.
  • The sharing and retention guidance follows Droozi's Privacy Policy: future locations are visible to all contacts, with relationship, blocking and account-access rules still applying.

Create your first future location

Download Droozi, share where you will be later with your contacts, 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. Notification matching is limited to accepted connections with registered Droozi accounts, with location-privacy settings and blocks checked. Saved future locations are visible to all contacts.

Why did I not get an alert when a friend was clearly in the same city?

Check that your connection is accepted, your saved dates overlap, applicable location-privacy settings allow sharing, and neither person has another trip taking precedence. Check the inbox separately from phone notifications: an inbox item can exist even when a device is unavailable or push alerts are disabled.

Can I see a list of all my overlaps?

There is no dedicated list of every current match. Notifications contains retained, still-authorized alerts, and meaningful changes may produce an update.

Related reading