wiki:Privacy Policy
Last modified 8 years ago Last modified on 08/11/09 16:08:24

Privacy Policy

We respect your privacy and want to protect it as much as possible. If you are concerned about privacy, please review these details.

mget-help mailing list

The goal of this list is enable a public dialogue between MGET users and the developers. When you email this list, your message will be sent to the developers as well as anyone who has subscribed to the list. Your message will also be added to the list's archive.

The archive is visible to all Internet users and is indexed by search engines. By making the archive visible in this manner, we allow users to quickly reach solutions to problems that were previously encountered by others. But the mailing list service provided by our university does not allow us to remove email addresses from archived messages. If you email this list, the copy of your message in the archive will include your email address. Therefore, if you are concerned about exposing your email address to others, please do not email mget-help. Instead, email jason.roberts@duke.edu for a completely private conversation. In the event that you accidentally email mget-help and would like your message to be removed from the archive, please email jason.roberts@duke.edu as well.

mget-help is a moderated list. To protect subscribers from spam, we review all messages for appropriate content before approving them for distribution to subscribers. Because of this, there will always be a delay before your message is distributed.

Anyone is allowed to subscribe. Subscribers may unsubscribe at any time from the list's home page. If you subscribe, we will only retain your email address for the duration of your subscription, and it will only be used for this list.

mget-announce mailing list

The goal of this list is to allow the MGET developers to notify interested users of new MGET releases and upcoming presentations related to MGET. Only MGET developers can send messages to this list. Anyone is allowed to subscribe. Subscribers may unsubscribe at any time from the list's home page. If you subscribe, we will only retain your email address for the duration of your subscription, and it will only be used for this list.

Installation reports submitted to the MGET development team by the installation program

In MGET 0.7 Beta 1 and later releases, the installation program reports the result of the installation to the MGET development team at the conclusion of the installation process. The report sent to the MGET dev team includes the following information:

  • The version of MGET that was installed.
  • A Boolean (true/false) indication of whether the different steps of the installation procedure succeeded, and error messages for certain types of failures.
  • The versions of Python, ArcGIS, and R that were installed on the machine.
  • The MGET-specific ID of the machine. This is a random, globally-unique 128-bit number (a GUID) assigned to the machine by the installation program the first time MGET 0.7 Beta 1 or later is installed. This number is kept in the ClientID value of the registry key HKEY_LOCAL_MACHINE\Sofware\GeoEco. This number allows the MGET team to differentiate between reports submitted by different machines.

The installation program initiates the reporting procedure at the conclusion of installation by starting the program ReportInstallation.py as a background process. After gathering the information above, that program submits the report by placing an XML-RPC call over the HTTP protocol to a secure server at Duke Unversity, and then exits. This typically takes 5-10 seconds. The server stores the report in a database, along with the IP address of the machine that submitted it and the date and time it was submitted.

At Duke, the database is maintained in a secure environment. The database is only accessible to the MGET development team and is not shared with anyone. We use the data to:

  • Measure the software quality of the installation program.
  • Determine which versions of Python, ArcGIS, and R are used by our user community, so we can plan what will be supported by future MGET releases.
  • Count the number of MGET installations and summarize this by MGET version, geographic region, and so on, to help us justify requests for additional funding.

Summaries of these data may appear on the MGET website, so that the user community can see how MGET is used. The unique identifiers (e.g. the IP address and MGET-specific ID) never appear on the MGET website.

We hope you appreciate how this information allows us to continue to improve MGET and offer it as free software. We believe that most people will be comfortable with us collecting this information. But you'd prefer that we not collect this information, you can disable the collection by performing the following procedure prior to running the MGET installation program:

  1. Start the Windows Registry Editor.
  1. Navigate to HKEY_LOCAL_MACHINE\Software.
  1. Create a subkey called GeoEco (if it does not exist already).
  1. Create a String Value called DisableInstallationReporting. You do not need to enter any data.
  1. Close the Registry Editor.