Find My in iOS 27 can hide your location from one person, and tell them nothingFind My in iOS 27 can hide your location from one person, and tell them nothing

The Find My app in iOS 27 has a Hide Location option that pauses location sharing with one chosen person without notifying them, a change covered again on 29 September as the feature reached general users.

Selecting it against a named contact stops that person seeing where you are. MacRumors puts the duration at twelve hours; 9to5Mac describes it as lasting until the end of the day. While it is active the menu entry changes to Unhide Location, so sharing can be restored by hand at any point before it expires. The person on the other side receives no alert, no banner and no entry in their own app to say anything changed. If they open Find My and look for you during that window, the app reports No Location Found, which is the same thing it shows when a phone is off, out of signal or has never shared at all.

Apple's stated reason for building it, as reported, is the surprise party: a case where revealing where you are spoils something harmless. The same release reworks how sharing starts. A location share can now run for a custom period between fifteen minutes and thirty days, set as days, hours and minutes or as a fixed end date and time, alongside the existing For One Hour, For Today and Always options. Sharing can also be paused with individual people rather than all at once.

Two further changes ship with it. The app adopts the Liquid Glass interface with a new tab bar, and shows more location detail on its main screen without a tap. On a cellular Apple Watch, location sharing now continues from the watch when it is away from its paired iPhone or iPad, and the watch app merges people, items and devices into one view.

None of the coverage states a minimum iOS version for the other party, or what somebody on an older release sees when a contact hides from them.

Our take

The surprise party explanation is true and it is not the reason this feature is important. The important property is the absence of a notification, and that property is only worth engineering for one situation: when the person watching your location would react badly to being told you had stopped sharing it.

Location sharing between adults is often not a neutral convenience. It gets switched on early in a relationship, in a family, or between a parent and an adult child, and then it stays on, and the cost of switching it off is a conversation about why. Anything that fires an alert makes that conversation unavoidable at the moment of switching off, which is precisely when someone in a controlling relationship is least able to have it. A silent pause that expires on its own, and that looks identical to a flat battery, is the design that helps in that case. Apple has not said this, and we would not put words in its mouth, but the shape of the feature says it clearly enough.

APPDOOK's reservation is the symmetry. A feature that hides a person from surveillance is the same feature that hides a person from someone with a legitimate reason to be worried, and the twelve hour window cuts both ways. There is no version of this that only helps the party you want it to help, because the system cannot know which of the two people at either end is the one at risk. Apple has picked the side that errs towards the person being watched, which we think is the right call, and it is a call rather than an obvious default.

The No Location Found detail is the cleverest part and the part most likely to be misread. It is not an error state Apple reused out of laziness; it is the only string that carries no information. A dedicated message such as Location hidden would have defeated the entire design, and a stale last-known position would have been a lie. Showing the same thing a dead phone shows is the honest way to show nothing, and it works because that state is already common enough to be unremarkable.

For anyone building on Apple's platforms, the transferable lesson is in the sharing durations. Fifteen minutes to thirty days, with a real end time, replaces a binary that was really a ratchet: on was easy, off was awkward, so on is where things stayed. If your product asks someone to share something continuous, an expiry is not a feature you add later for tidiness. It is the thing that makes the first yes reversible, and it is much easier to design in at the start than to retrofit once a million relationships depend on the old behaviour.