System Settings

System settings take effect globally throughout Analytics, for example, you can set time periods when you want Analytics to stop collecting data. Email and text settings are also configured in the System settings, as all the alarms in Analytics use the same email and SMS account to send notifications when an alarm has fired.

The System settings are grouped on the following tabs:

Privacy Regulations and Analytics

Analytics collects user data from some of the resources that it monitors in order to track how users interact with those resources. Tracking user information makes it possible to assess the usage of various applications and sites in order to facilitate decisions on how to improve the user experience. Whenever an organization or software collects user data, privacy and the protection of personal data becomes an issue.

Increasingly, regions like the European Union (EU) and California are enacting laws or regulations to govern how organizations protect users' privacy rights when they collect user data. Regulations vary between regions from non-existent to a strict set of precise instructions.

Currently, the strictest set of regulations is the EU General Data Protection Regulation that comes into effect on May 25, 2018. Only Analytics users in the EU have to follow these strict regulations. Most other regions are likely to have less exacting requirements.

To ensure that all Analytics customers are able to comply fully with privacy regulations, Analytics has built-in features that make it possible to comply with the strictest current regulations.

Because of the differences in regional regulations, Analytics customers need to ascertain what the regulations are in their particular region, and then ensure that they configure the Do-Not-Track option in Analytics to comply with those laws.

Privacy regulations usually specify that organizations protect personal privacy in the following ways: 

How do I comply with privacy regulations?

The following is a comprehensive, although not exhaustive, list of measures that you can implement in order to comply with the strictest privacy regulations. Unless you are operating in the European Union, you are unlikely to have to implement all of them.

To meet strict privacy regulations, you should: 

  1. Establish what privacy laws and regulations are applicable in your area.

  2. Establish what your organization's retention policy is for stored user data, in particular, how long user data will be kept. Some regulations require that you inform the user of the length of time their data will be stored.

  3. Based on what your region's regulations are, configure Analytics to comply with those regulations.

  4. If the region you serve has privacy tracking laws, then obtain users' unambiguous consent before tracking or using their data.

    A good practice is to add a pop-up that appears when the site or software opens. The pop-up contains text to inform the user how their data is used, how long it will be kept and how to opt out of tracking. The pop-up also contains a box for the user to confirm that they consent to being tracked. The language must be plain and easily understood.

    Example text for this pop-up could be:

    This [application/website] records user statistics, such as your user name and Internet Protocol (IP address) in order to improve your user experience and the overall quality of our services. User data is stored for analytical purposes for up to [X] years and is not shared with any third parties.

    Consent is determined by the Do-Not-Track setting in your browser. If you do not want your usage of this application/website to be tracked, you must enable your browser Do-Not-Track setting.

  5. Keep the stored User Data that Analytics collects secure: 

  6. If you are an Analytics customer servicing the EU and there is a data breach, you must inform the EU privacy body within the time period specified in the regulations.

Configure Global System Settings

Global System settings affect all the resources that Analytics monitors. You can set up time periods during which you want Analytics to stop collecting data, set whether or not to accept invalid SSL Certificates, or whether or not to enforce Do-Not-Track privacy settings.

To configure Global System Settings:

  1. Open Analytics, and then click Configuration.

  2. In the sidebar, click System.

  3. On the Global Settings tab, change any of the following settings:

  4. Click Save.

Configure Email Settings

If you wish to receive email notifications when one or more alarms fire in Analytics, you need to enter the information that Analytics needs in order to send emails automatically, including the wording in the email and which email addresses to send them to.

To configure Email Settings:

  1. Open Analytics, and then click Configuration.

  2. In the sidebar, click System.

  3. On the Email Settings tab, change any of the following settings:

  4. Click Save.

Configure SMS Settings

If you wish to receive a text message when an alarm fires in Analytics, then you need to create a Twilio account for Analytics to use to automatically sends SMS messages. You also need to enter the list of phone numbers to receive the text messages.

To configure SMS Settings:

  1. Open Analytics, and then click Configuration.

  2. In the sidebar, click System.

  3. On the SMS Settings tab, change any of the following settings:

  4. Click Save.

Purge Data

You can purge older data to free up space on your server.

You can only purge data that is older than two months. When you select a month, all the data prior to that month and during that month is purged.

Purging data is permanent. Once purged, the data cannot be retrieved.

To purge Data:

  1. Open Analytics, and then click Configuration.

  2. In the sidebar, click System.

  3. Select the Purge Data tab.

  4. From the Purge All Data Collected Prior To and During drop-down list, select a month.

    Beside each month, the brackets indicate the estimated space that you will free by purging that data.

  5. Click Purge.

Manage User Data and Privacy

Analytics tracks and collects information about how users interact with the resources that it monitors, for example, Geocortex and Esri applications. The objective of tracking user data is to establish usage patterns that can inform decisions about how to improve users' experience.

Privacy regulations in some regions indicate that if you collect user data, you must be able to retrieve and delete that data on request.

On the User Data tab in Configuration, you can search for a user's collected data by their full or partial user name or IP address. You can export the data if required, or purge the data to strip it of any identifying information. Analytics keeps the purged user data and uses the retained information for statistics about the user's activities in various applications but the data is anonymous.

To find and purge user data:

  1. Open Analytics, and then click Configuration.

  2. In the sidebar, click System.

  3. Select the User Data tab.

  4. In the Search by Name or IP Address box, type in a full or partial user name or IP address.

    If you type in a partial name or address, all matching users or addresses will be listed.

  5. Click Search.

    If the user was authenticated on sign-in to an application or resource that is monitored by Analytics, their user name and ID are listed in the results. If the user did not sign in, only their IP address is listed.

  6. To export a user's data because it has been requested, click Export.
  7. To strip a user's data of any identifying information, click Purge.

© 2018 Latitude Geographics Group Ltd. All Rights Reserved.

Documentation Version 1.4