GMaps Plugin requires internet connectivity to communicate with the Google Maps API. To ensure maximum security of your organization's data, GMaps Plugin does not send or persist any business data to Google servers. GMaps Plugin does not require additional ports or tunneling to successfully communicate with the Google APIs and does support HTTPS for added security (see HTTPS Support below).

Xcelsius Component Security
GMaps Plugin connects directly to the Google Maps API, and does not require any middleware layer in between. During SWF runtime all customer data rendered inside of the map on the local PC, and behaves like all other dashboard components. The SWF file and embedded map is stateless and will only communicate with Google Maps APIs upon user interaction. When the SWF file is closed all data is cleared from the local system memory and any data transacted to the Google Service during the session is also not persisted by Google, GMaps Plugin, or Xcelsius.

Data Transacted to Google Maps Service
The only information that GMaps Plugin transacts to the Google Maps API during SWF runtime is the API key, CentigonID, or ClientID, zoom level, pan-to location, map style (satellite, etc) and region/address data points that need to be geocoded during runtime. In return Google Maps API will return the necessary image tiles to draw mapping imagery.

GMaps Plugin contains all of the code required to render latitude/longitude data, data icons, tool tips, info windows, labels, polygons, lines, routes, heatmaps, and other metadata that is displayed to the end user. Like any other component within a SWF, the content is rendered locally on the end user's computer, secured behind your firewall and other security measures. GMaps Plugin will support HTTPS sites for organizations that build content that is accessible outside of the corporate firewall.

At no time will GMaps Plugin transact any data bound to the following Map Properties.

• Series Name
• Labels
• Values
• Data Insertion
• Shapefile definitions
• Icon Style or color definitions

Geocoding Exception
While GMaps Plugin is configured to interpret and render latitude,longitude data to render data, it is not capable of converting addresses locally. If your organization desires to use the Google Maps geo-code APIs, address data is transacted to the Google service and returned as converted Lat,Long data. Google Maps premier will not persist or use any data other than to convert and return the geocode conversions for the single user session.

GMaps Plugin Properties that are transacted to the Google service
The following are the only properties where linked data is transacted to the Google Maps API

• API Key (Trial and GMaps Plugin Standard)- For GMaps Plugin Trial and Standard, the API key is used to identify your dashboard deployment
• License Key (GMaps Plugin Bundle Only)- The license and Centigon Solutions generated authentication key is passed to Google Maps API to flag your page views. These keys identify your organization anonymously.
• Address Data- Address data property will only transact data when it is NOT latitude,longitude data. (See geocoding exception above)
• Pan-to Property- When using the pan to property, GMaps Plugin will send this single property to the Google Maps server so the map can obtain the correct map tile imagery.
• Zoom Level Property- When using the zoom property, GMaps Plugin will send this single numeric value to the Google Maps server so the map can obtain the correct map tile imagery based on the zoom level.
• Standard Map Controls- Google Maps includes standard controls for zooming, panning, and changing the map type.

HTTPS Support
GMaps Plugin will automatically connect to Google Maps Premier via HTTPS when GMaps Plugin is embedded in a secured web site and the SWF is accessed via HTTPS upon requesting HTTPS approved domains from Centigon Solutions support. HTTPS is NOT supported for GMaps Plugin Standard or GMaps Plugin Trial software.