Location Privacy
A user's location data is not shared or recorded unless they turn on an active check-in session or initiate an alert. That is the whole rule.
With no session and no alert running, nothing is collected in the background and nothing is recorded for a supervisor to open later.
The worker starts a session and ends it themselves, and location stops the moment they check out. An admin cannot start one on their behalf, so it only ever happens when the user turns it on.
Alerts work the same way - the location is shared only when the alert is triggered, and stops being shared after it ends.
No session
Alert Feed
Every alert opens a shared feed with that person's emergency network: live location, the context they set out with, and every message and action in one place. Nobody has to be sitting at a desk for it to work.
The contacts at the top of the feed are the people this employee's alerts go to, not one generic company-wide call list. Networks can be configured on a user level, so a field tech three hours out of town and an office manager downtown each get the people who can actually help them. Contacts are unlimited at no extra cost, so you can add a supervisor, a spouse, a second site lead and the rest of the shift crew without a per-contact fee deciding who gets left out.
The feed says what kind of alert it is the moment it opens, so responders know what they are dealing with before reading a word of the thread. A missed check-in and a duress alert are not the same event, and they do not have to get the same response. You set who is notified first for each type, how long it waits before moving to the next person, and when it gets handed off for help, so a quiet reminder stays quiet and a real emergency moves fast.
The moment an alert fires, live location goes into the feed and keeps updating as the person moves. Nobody has to call around asking where they were last seen, and nobody has to recall an address under pressure. The team opens the feed already knowing where to go instead of starting with a name and a question mark.
On the way out, the employee records what they are heading into: job type, level of risk, and any notes they want on file. If an alert fires while that check-in is running, all of it opens with the alert, so the people responding already know it is a parolee home visit and that Mark has seemed jumpy the last couple of meetings. That context came from the person who set it, before anything went wrong, and nobody has to reconstruct it from a calendar entry.
Add 24/7 professional monitoring (optional) and the operator's actions post into the same feed your team is already watching. You can see the alert was received, see the operator reach out, and see whether they got an answer back. Managers get proof that something is being done as it happens, in writing, without calling anyone for a status update.
Everyone in that person's emergency network is notified at the same time, so the closest teammate can speak up instead of waiting to be assigned. At a remote site that coworker is often minutes away when emergency services are much further out. The team can pool what they know, agree on who is going, and respond directly when that is the fastest way to help, or escalate to emergency services from the same screen.
Every location, message and timestamp is logged to the alert's record in the Compliance Dashboard, ready when you need to show what happened.
Our guide will walk you through how to evaluate different types of technology to improve lone and at risk worker safety.
