Product/Product Details


In-depth information on all Safeture processes.

Process categories

Print Friendly, PDF & Email

Alert Publishing

Incidents are first detected through proprietary data gathering tools, scanning thousands of information sources. The system also has a built-in auto-translation capacity to manage sources in a variety of languages.

These are a few of the types of data sources used to gather information on incidents:

  • News (International and Regional)
  • Seismological institutes
  • Meteorological agencies
  • Departments of Foreign Affairs
  • Other Government Agencies
  • Social Networks and forums (Crowdsourcing)
  • Aid organizations and other NGO’s
  • Meta-data aggregation
  • Health and Disease Surveyors
  • Safeture Incident and Event Database (all events and incidents that Safeture process are tagged and labeled)
  • Strategic Partners
  • Social Media

After data gathering, the information first goes through automatic filtering by an Artificial Intelligence (AI) system (semantic relationships) plus a list of keywords to search for. A secondary manual filtering is done by analysts. They then verify the data, define the impact radius, severity level, and finally, publish the alert.

The impact radius is dynamic and varies depending on the incident. For instance, a shooting is seen as a very local incident while an earthquake might have countrywide effect. The radius of the incident is set based on the incident category and how widespread the effect is. They are set with an interval between 10 km and 1000 km. Event radius crosses borders and may be set as nationwide. Minor incidents, such as traffic disruptions, civil unrest, and events, start within a 10 km radius. Natural disasters span a large radius interval, with the most widespread tropical storms ranging upwards 1000 km.

If the incident is seen as critical, an initial message will be published and sent to clients in the affected location within 5-15 minutes from when a source initially reported about the incident. We are capable to do so due to the integrated information mining system, message publication system, and our highly automated process. Sometimes robot publication is used where the time between source input to message (SMS, push notification) publication and send-out is required to be short and where the source is highly credible, such as automated tsunami warnings. 

On publication of an alert, the Safeture Platform will automatically send out an alert about the incident to all end-users that are within the impact radius, or that are traveling into the region where there has been a published alert during the last three days.

By “Favoriting” a region, end-users will receive newly published alerts for that country even if they are not traveling to, or within, that country. The alert will show as a notification, and when pressing the link or notification, the end-user is presented with an alert overview. A map will show the incident location, the risk level, and the distance from their current position to the incident location.

The Safeture Platform will also notify relevant Administrators in the Safeture Web Portal (own/assistance providers) if any employees were impacted by the alert. To Administrators, alert notifications are sent via email and can be configured to send via SMS also.

Positioning methods

The Safeture Platform uses a variety of methods and functionality to locate employees. The locations of your employees are continuously uploaded to Safeture servers, all in compliance with GDPR.

Below you find all these methods listed and explained:

1. Mobile Application Positioning

The Mobile Application Positioning is used for active monitoring. If activated, the Safeture Mobile Application automatically sends location data without any manual input by the end-user. The location is based on GPS, WIFI network, VPN, and Mobile Network connections.

  • WIFI

Being connected to WIFI increases the likelihood that your position reporting will be inaccurate compared to your “true” location. In practice, the position of your internet base station or router, i.e., probably set by your internet provider, will be used as your actual position.

  • VPN

Similar to WIFI, being connected to VPN significantly increases the likelihood that your position reporting will be inaccurate compared to your “true” location. Depending on the VPN setup, it may report your position in a different state or country for privacy purposes. Using VPN can make your device believe that you are at a different location than your real location and thereby report a “false” location on the Safeture App.

  • Mobile Networks

This is the best option for getting an accurate position. In this case, with a strong cellular network connection, your position can be determined by triangulation and GPS (trilateration), theoretically depicted in the graphic. Hence, being in a basement usually decreases the accuracy, while being outdoors increases position accuracy significantly. Also, turning on Bluetooth improves location accuracy as Apple location service utilizes it in reporting positions.

2. Travel Booking Data

The platform will use the itinerary location of a trip as that person’s location, which requires integration with a Travel Management Company, parsing through email, or manual input of travel data.

3. Manual Check-In via the Safeture Mobile Application

The end-user can also manually check-in by pressing the check-in button in the app, which will send that person’s location to the Safeture Platform.

Book a demo


Ready to see the platform in action?

Sign up and get a free, personal demonstration of all Safeture features and functionalities by one of our team members.

Travel Data Integration

Travel booking information is a key component of the Safeture offering. We integrate with all Travel Management Companies (TMCs) and Global Distribution Systems (GDSs), so Safeture can automatically import all travel booking data. During the onboarding process, Safeture will contact your travel providers and arrange for the connection between the travel providers and Safeture. Safeture has connections to all GDS providers and TMCs.

An agreement between you and the TMC that allows the TMC to send copies of the Passenger Name Records (PNRs) to Safeture needs to be set up beforehand. When the agreement and identifiers are in place, the TMC can send copies of the PNRs to Safeture via the GDS.  

For bookings that are not connected to GDS, we can provide an SFTP that the TMC can upload bookings to.  

When the TMC makes a booking for the client, a copy should be sent to the Safeture queue in the GDS. Safeture regularly monitors the queue for new PNRs. PNRs will be parsed by Safeture, and, when detected, will be determined if they’re completely new bookings or contain updates and cancellations.

Traveler identification is done via phone number, email, frequent flyer ID, and name. If a trip contains several bookings, it will be pieced together for the end-user and displayed accordingly. We support PNRs that have more than one traveler.  

The PNR queue on Amadeus and Sabre is scanned every 15 minutes. The TMC needs to re-queue the PNR for the update to be visible. Each PNR is updated at a regular interval before each departure segment. For TravelPort, updates are done when new updates are received. 

For bookings made outside of default TMCs, users can use email parsing, where travel booking confirmations are emailed to a defined email address. A third option is to manually add a travel booking in the Travel module within the Web Portal.

Alerts sent through email

You can have traveling users receive alerts via email. The email is triggered for any users – both end-users with the Safeture Mobile Application installed and traveling users added to the platform via a PNR (Passenger Name Record).

The alert is sent when the user has a booking to, or from, the area where an alert has been published.

Traveling users will recieve the alert:

  • For departure locations (i.e. outbound airports)
    • 24 hours before, and 4 hours after, scheduled take-off.
    • If the published incident radius is within 5 km of the booking location (airport/hotel/rental car) or if the region of the booking location matches a region of the alert.

  • For arrival locations (i.e. inbound airports, hotels, etcetera.)
    • 72 hours before scheduled take-off.
    • If the published incident radius is within 50 km of the booking location (airport/hotel/rental car) or if the region of the booking location matches a region of the alert.

Image – Alerts sent through email