Location sharing without giving up privacy: a family safety plan
Choose who sees your location, for how long and at what precision. Build a practical family agreement, test its limits and know how to respond to unwanted tracking.
Security and resilience editorial team · Source-reviewed editorial guidance based on public-agency publications; no professional certification, product testing or laboratory validation is claimed.
Quick answer
Share location for a specific purpose with a small, agreed audience and a clear stopping point. Prefer an arrival message when continuous tracking adds little value. Review app permissions and account access separately, test how sharing ends, and agree on a backup contact plan. If monitoring may involve abuse, seek help from a safer device before changing settings.
Key takeaways
- Start with the safety task, then choose the least revealing way to complete it.
- Agree on recipients, duration, precision and what happens after a missed check-in.
- Review location permissions, sharing recipients and account access as separate controls.
- Treat a map position as supporting information rather than proof of someone’s safety.
- Plan carefully before removing access when stalking or coercive control is suspected.
Choose the smallest amount of sharing that solves the problem
The best starting point is a specific question: does your family need an arrival confirmation, a meeting point or temporary visibility during a journey? Choose the least detailed option that answers it. Routine reassurance does not automatically require a permanent location feed.
For example, agree that someone travelling home sends a message after reaching the station and another after arriving. If meeting in a crowded place is the problem, a single meeting-point pin may be sufficient. For an unfamiliar journey, consider temporary sharing with one person who has agreed to monitor it. These are suggested decision rules, not guarantees of safety.
Distinguish a one-time location from a live feed and from stored journey history. Before using a feature, check which of these it actually provides. Ask the recipient what they can see instead of relying on the sender’s interpretation of the interface. The eSafety Commissioner explains that location exposure can arise through multiple services and account settings [Location sharing](https://www.esafety.gov.au/key-topics/online-tools-and-features/location-sharing).
Use the table as a conversation starter. Move toward more detail only when you can explain what useful action that detail enables. If nobody will be available to respond, first solve the contact problem rather than adding another map.
- • Name the purpose in one sentence: meeting up, confirming arrival or supporting a particular journey.
- • Choose one responsible contact and an alternative if that person is unavailable.
- • Choose an end event, such as arrival, and an expiry time where supported.
- • Decide what information the recipient actually needs to act.
| Approach | Suggested use | Privacy boundary to check |
|---|---|---|
| Arrival message | Routine journeys where confirmation is enough | Message recipients and any location attached |
| One-time location pin | Meeting at a specific place | Whether the pin is static and who can forward it |
| Temporary live sharing | A defined journey with an available contact | Expiry, recipients and precision |
| Ongoing sharing | A continuing support need agreed together | Regular review, ability to stop and retained history |
Sources for this section: eSafety Commissioner: Location sharing
Write a family agreement people can actually follow
A useful location-sharing agreement states who participates, who receives updates, when sharing starts and ends, and how to respond when contact is missed. Make it understandable and reviewable. For adults, our editorial recommendation is voluntary participation with a practical way to withdraw.
For children, explain the arrangement in language they understand: who can see the map, why it is being used and whom to ask for help. Revisit the arrangement as independence and support needs change. For an older relative, discuss what help they want rather than assuming continuous observation is the only suitable arrangement. These are family decision criteria, not legal advice about parental authority or capacity.
Try this template: ‘For this journey, I will share with Alex until arrival. If I miss our agreed contact time, Alex will message, then call, then contact our backup person according to the plan.’ Choose intervals that fit the circumstances; there is no universal delay that proves an emergency.
Add a rule against forwarding links or posting screenshots. The FTC warns that recipients can save or redistribute shared content, so expiry cannot undo everything already seen [Heads Up](https://consumer.ftc.gov/articles/heads-up). Ask before including someone else’s location in a group conversation.
Practice stopping sharing during an ordinary, low-pressure moment. Invite each participant to explain the plan in their own words. If someone cannot identify the recipient or stopping point, simplify the arrangement before relying on it.
- • Record the purpose, named recipients and stopping point.
- • Agree on a missed-contact sequence and a backup contact.
- • Set a review date and revisit after travel, a new phone or a relationship change.
- • Keep group chats and public posts outside the sharing arrangement unless explicitly agreed.
Sources for this section: Federal Trade Commission: Heads Up: Stop. Think. Connect.
Audit permissions and account access separately
Check three separate boundaries: whether an app can obtain location, which people can receive it, and who can access the account. Reduce precision and background access where suitable, then test the intended task. A restricted permission does not by itself verify the recipient list or the provider’s retention policy.
Open the phone’s location-permission list and review each app individually. Look for approximate versus precise access and foreground versus background access where available. The Canadian Centre for Cyber Security notes that approximate location may affect functionality and should not be relied on alone for sensitive locations [Mobile-device security guidance](https://www.cyber.gc.ca/en/guidance/security-configurations-best-practices-protect-your-mobile-device-itsm80002).
Next, open the sharing feature itself. Record the people or links currently authorised and remove obsolete access when safe. Separately inspect account sessions, recovery details and linked devices where those controls exist. Use an individual account rather than treating a shared family password as the sharing mechanism.
For every candidate service, ask concrete questions before committing: can access expire automatically; can you identify every recipient; can you stop sharing clearly; what history is retained; and does the privacy notice describe onward sharing? Treat an unanswered question as a reason to investigate, not as proof of a protective feature.
NIST identifies abuse of granted location permissions as a mobile threat [APP-24](https://pages.nist.gov/mobile-threat-catalogue/application-threats/APP-24.html). Our practical rule is to grant access for an identified function and review it when that function is no longer needed.
- • Remove unnecessary location permissions.
- • Check recipient lists inside each sharing service.
- • Review account access and recovery routes separately.
- • Repeat the actual journey-sharing test after making changes.
Sources for this section: Canadian Centre for Cyber Security: Security configurations and best practices to protect your mobile device (ITSM.80.002), National Institute of Standards and Technology: APP-24: Covertly Track Device Location
Test the arrangement and prepare for missing updates
Before relying on location sharing, run a short rehearsal with the actual sender and recipient. Confirm that both understand the display, the stopping control and the backup contact plan. Our recommendation is to treat an unavailable or old position as missing information that requires context.
During the rehearsal, ask the recipient to describe what they see, including any update time or accuracy indicator the service provides. Walk a short, familiar route, send the planned check-in and stop sharing. Confirm what remains visible afterward. Do not assume every service exposes the same status information.
Write down a fallback that does not depend on opening the map: a contact number, a planned meeting point and the person to contact next. Test the plan with anyone who finds the interface difficult. A simpler message routine may be more usable than a feature-rich service that one participant cannot operate confidently.
Use the missed-contact plan to guide a proportionate response. Try the agreed contact methods and consider known circumstances. Where there is credible immediate danger, seek local emergency help; do not wait for a map to become conclusive. This is an editorial planning framework rather than an emergency-dispatch protocol.
A personal safety alarm can be considered separately when planning what to carry. It should not change your assumptions about the sharing service. No alarm capability, connectivity or rescue response is evaluated here. Keep equipment choices subordinate to a clear communication plan.
- • Rehearse starting, viewing and stopping sharing.
- • Check what happens when the planned sharing period ends.
- • Keep essential contact details available outside the location app.
- • Reassess the plan if reduced permissions prevent the intended function.
Sources for this section: Canadian Centre for Cyber Security: Security configurations and best practices to protect your mobile device (ITSM.80.002), eSafety Commissioner: Location sharing
Respond carefully to unwanted tracking
If unwanted tracking may involve an abusive person, prioritise a safety plan before changing access or resetting a phone. Seek support using a device the person cannot monitor. Preserve relevant evidence safely, then decide with appropriate support how to secure accounts and address the suspected device.
The FTC warns that removing stalkerware can alert an abuser and escalate abuse. Its guidance recommends seeking help through another device and considering evidence preservation before replacement or reset [Stalkerware: What To Know](https://consumer.ftc.gov/articles/stalkerware-what-know). Do not make a conspicuous cleanup checklist your first step when retaliation is a concern.
Prepare a factual record if it is safe: unexpected account-access notices, unfamiliar sharing recipients and incidents in which someone knew an undisclosed location. Keep observations separate from conclusions. A battery problem alone does not identify the cause, and an absence of obvious signs should not be treated as a completed investigation.
When it is safe to proceed, include passwords, additional sign-in protection, recovery access and physical control of the phone in the recovery plan. If resetting or replacing a device, the FTC cautions against reinstalling applications from the old backup because this could restore stalkerware. Rebuild deliberately rather than restoring everything automatically.
Finally, check indirect disclosures. Review public route posts, check-ins and photos, together with linked services relevant to your situation. Set a follow-up date after the initial changes. Recovery is complete only when the revised arrangement is understandable, usable and consistent with the affected person’s safety needs.
- • Use a safer device to seek support when monitoring is suspected.
- • Discuss possible retaliation before cutting off access.
- • Preserve evidence where safe before destructive changes.
- • Review both deliberate sharing and indirect location disclosures.
Sources for this section: Federal Trade Commission: Stalkerware: What To Know, eSafety Commissioner: Location sharing
FAQ
Should every family member share location continuously?
Our recommendation is to start with the purpose and consider an arrival message or temporary sharing first. Use ongoing sharing only after discussing the continuing need, recipients, stopping process and review date.
Does approximate location make sharing private?
It reduces detail in supported configurations, but it is not a complete privacy safeguard and may affect functionality. Test whether it meets the task; the Canadian guidance specifically cautions against relying on it alone for sensitive locations.
Does ending sharing delete everything already disclosed?
Do not assume so. Check the service’s history and deletion controls separately. Recipients may also have saved content; the FTC explains that screenshots and redistribution can outlast the original sharing.
What should I do if someone knows locations I did not share?
Consider account access, indirect posts and unwanted monitoring without assuming a single cause. If abuse is possible, use a safer device to seek support before making changes that might alert the person.
Methodology and sources
We searched for and opened primary guidance from the FTC, Australia’s eSafety Commissioner, the Canadian Centre for Cyber Security and NIST on 2026-11-02. The publication and update fields retain the requested editorial date, 2026-10-30; they are not the research-access date. The checklists, comparison and family agreement are editorial applications of these sources, not a tested protocol or an app ranking. We did not test devices, measure accuracy or verify provider retention practices. Interface names and available controls vary. Visual limitation: the supplied PNG is square and both supplied SVGs are portrait; all contain English text. No supplied asset meets both the landscape and text-free requirements. The existing files are used without inventing replacements, and captions identify their illustrative role.
- eSafety Commissioner: Location sharing · accessed 2026-11-02
- Federal Trade Commission: Heads Up: Stop. Think. Connect. · accessed 2026-11-02
- Canadian Centre for Cyber Security: Security configurations and best practices to protect your mobile device (ITSM.80.002) · accessed 2026-11-02
- National Institute of Standards and Technology: APP-24: Covertly Track Device Location · accessed 2026-11-02
- Federal Trade Commission: Stalkerware: What To Know · accessed 2026-11-02