Key takeaways
- Prefer share-on-demand (the worker sends a location) over continuous tracking.
- Explain in writing when location is requested, why and who sees it.
- Never request or collect location outside working hours.
- Location sent in a group is visible to that group; use direct messages for one-to-one.
- C Chat lets people share a location in a message; it does not track staff.
Location is one of the most useful pieces of information in field work and one of the most sensitive. A guard sending where they are during an incident can save time; a manager watching a dot move on a map all evening damages trust and may break the law. The rules below help you get the benefit without the surveillance, whether your team uses a messenger, a dedicated app or both.
Why employee location sharing privacy matters
Location reveals more than people expect. A week of location points can show where someone lives, which doctor they visit or where they pray. That is why most data protection frameworks treat location tied to a person as personal data, and some treat it as especially sensitive.
For employers, the risk is twofold: legal exposure if collection is not justified and disclosed, and lost trust when staff feel watched. Rules vary widely; Latin American readers can start with data protection in Latin America, and everyone should confirm their obligations with counsel.
Share-on-demand vs tracking
There are two very different models:
| Share-on-demand | Continuous tracking | |
|---|---|---|
| Who acts | The worker sends it | The system collects it |
| When | At a moment that matters | All the time, often in background |
| Data created | A few points | Thousands of points |
| Worker control | High | Low |
| Typical use | “I’m at the gate”, incident location, meeting point | Fleet routing, dispatch systems |
For most messaging use cases, share-on-demand is enough: a worker arriving at a site, a lone worker checking in, an incident report that needs a precise spot. It also creates much less metadata to protect.
Consent and transparency
Whatever model you use, tell people clearly. A good disclosure answers five questions:
- When will we ask for your location? (Example: on arrival at a client site, during incidents.)
- Why do we need it? (Safety, proof of service, coordination.)
- Who will see it? (The site group, your supervisor.)
- How long will it be kept? (As long as the related records.)
- What if you don’t share it? (Who to call instead.)
Put this in your BYOD policy if staff use personal phones, because location on a personal device is the most sensitive case of all.
Off-duty boundaries
The clearest rule: no location requests or collection outside working time. That includes “just checking where you are” messages to someone on a day off. If a role is on call, define the on-call hours in writing and limit requests to those hours.
Also think about who receives the location. A location sent in a group is visible to everyone in it, and in a business messenger the group is part of the company record. A location sent in a direct message goes only to that person.
Policy wording
Adapt this text and have your counsel review it:
Location sharing. During working hours, you may be asked to share your location in [approved app] when arriving at a site, during an incident or for safety check-ins. You send it yourself; the company does not track your phone. Locations shared in work groups are visible to members of that group and form part of work records. We will not request your location outside your working or on-call hours.
How C Chat helps
C Chat supports share-on-demand by design. Any person can share their location in a message to a group or a direct message; there is no background tracking or GPS tracking feature. Locations in a group are visible to that group’s members and, like other group content, can be audited and exported by team owners and admins. Locations in a direct message stay private between the two people; see why direct messages stay private and who can read your messages.
The same privacy-first approach applies elsewhere: phone contacts are matched using numbers hashed with SHA-256 on the device, and the server does not store those hashes (how contact matching protects phone numbers). If you are moving away from personal apps, the guide to personal WhatsApp risks explains why location in personal groups is harder to control.
Getting started
Write your location rule first, then set up groups that match it. Try C Chat in the browser at getcchat.com/c; it is free for now within the limits on the pricing page.
Frequently asked questions
Can my employer track my phone's location?
It depends on the country, the device, the app and what you agreed to. Tracking a personal phone continuously is restricted or requires clear notice and a legitimate reason in many places. Ask for the written policy, and employers should confirm their obligations with counsel.
What is the difference between sharing location and tracking?
Sharing is a single action by the worker: they send where they are, when they choose or when asked. Tracking is continuous collection, often in the background. Sharing gives the worker control and creates far less data, which makes it easier to justify.
Is location data personal data?
Yes, in most data protection laws location linked to a person is personal data, and it can reveal sensitive details such as home address, health visits or religious practice. Collect as little as you need and keep it only as long as needed.
Does C Chat track employee location?
No. C Chat lets a person share their location in a message to a group or a direct message when they choose to. There is no background tracking or GPS tracking feature.