Processing of locations in Twitter

SNH 1.27.0

If a target profile has made location information (geolocations) publicly accessible, this can be collected by the SNH.

The SNH Facebook module collects geolocations from three different sources:

1. Geolocations in postings
2. Geolocations in user details
3. Geolocations from „checked in” or “visits” page

Geolocations in Postings

If a target profile has tagged location information in one of its public posts, the location will be saved during the timeline backup. The time of publishing is stored as the time of the location information. 

The location information of a posting may overlap with visit location information. It is notpossible to assign the location information to either source.  It may also be the case that location information in postings cannot be found in the location information  in  visits of the same target profile. The opposite  is also possible. This is due to the different privacy settings of the profiles and the posting habits of the profile owners.

Geolocations in user details

If a profile owner publishes information about their place of residence, place of work, education, etc., in their user details, and if a Facebook page is stored within the location information, the SNH will also store these locations while collecting user details.

Since  dates are usually not given for these locations, the respective collection times are stored as associated dates for the locations. 

Geolocations from "checked in" or "visits" page

If a profile owner publishes locations where they have stayed, these visits will be recorded while collecting user details. The dates are only given accurate to the day on the Facebook website. An exact timestamp cannot be collected.