Alert Publishing


Alerts are notifications about security incidents to help people stay safe by avoiding risk. Safeture covers incidents of different kinds, such as kidnap and ransom, political developments, terrorism, etcetera. See all alert risk categories here: alert risk assessment methodology.

After an incident is detected, the information is verified, and the risk is assessed by experienced analysts. Alerts can be distributed in a few different ways; through the Safeture mobile app, via email, or inside the web portal in an alert feed.

Read more details about the alert publishing process below.


Risk Assessment

Define the impact radius

After an incident is detected, the analysts assign it an impact radius, i.e., the geographical area impacted by the incident. This is based on the character of the incident. For instance, a shooting is seen as a very local incident while an earthquake might have a countrywide effect. The radius of the incident is set based on the incident category and how widespread the effect is.

Assign a risk level and risk category

The analysts also assign the incident a risk level before publishing it as an alert. The alert can have any of the three risk levels; low, medium, or high.

To describe the type of incident that has occurred, the alert will have one or more risk categories assigned. Read more about the risk levels and risk categories here: alert risk assessment methodology.

Alerts triggers

On publication of an alert, the Safeture Platform will automatically send out an alert about the incident to all end-users that:

App locations:

  • Are currently located within the incident’s impact radius. Note that the location of the end-users reflects their privacy settings set in the Safeture mobile application. To get more relevant alerts, we recommend having the exact location enabled.

Manual selection:

  • Have marked a country as a favorite in the app. By doing so, end-users will receive newly published alerts for that country even if they are not traveling to, or are located 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. See a guide on how to mark a country as a favorite here.

Travel booking locations:

End-users will also get alerts based on their travel destinations. The timeframe and radius is depending if it is the departure or arrival location. Hotels, which have only one location, will use the values specified for an arrival location. See details below for both arrival and departure locations as triggers for alerts:

  • Arrival locations: people traveling will get alerts about incidents happening at the arrival location 72 hours before arrival. These locations are valid in the system until 4 hours after departure from that location. This enables proactive risk management where you can cancel trips where there has just been a large incident. The radius for these locations is the size of 50km, meaning that the incident needs to be within 50km from the airport (for flights), or hotel (for hotel bookings), for the end-user to get an alert about it.

  • Departure locations: people traveling will get alerts about incidents happening at the departure location, ie., the location they are traveling from, from 24 hours before the time of the departure and 4 hours after departure from that location. The radius for these locations is the size of 5km.

Assets near an incident – alerts to admins

  • For administrators managing the safety of end-users, you will also be notified of alerts near your assets (people or facilities). To administrators, alert notifications are sent via email and can be configured to send via SMS also. The email is called “Personnel in incident region,” and you can read more about its exact of it content here.