Running a GPS tracking operation requires more than viewing points on a map. Teams must also protect access, deliver information to the right people, keep trackers connected, and turn device data into decisions. This Secure GPS update brought together improvements in account security, REST API integration, statistics downloads, and GPS tracker compatibility to make that work easier to control.
The new capabilities help fleet managers, security companies, integrators, and individual users review account activity, obtain operational information, and expand their hardware choices without unnecessary manual processes.
Alternate email for stronger account administration
Secure GPS added an option in My Account to register an alternate email address. The feature keeps a second contact detail associated with the user and includes a verification step before the address is saved.
In a real operation, a company may want to keep the login email separate from an administrative contact or maintain an additional contact without replacing the primary user name. Verification helps prevent an incorrectly entered address from being attached to the account.
Security records for logins and sensitive changes
The account area began displaying security records for activity such as logins and password changes. This traceability provides context for determining when an important action occurred and whether it matches authorized activity.
An administrator can review the record after credentials are changed or when a login is not recognized. This reduces uncertainty during a security review and supports timely action, such as changing the password and confirming who has access.
For organizations with several operators, the value goes beyond keeping history. It provides visible evidence that supports internal controls and responsible access practices.
Manage and renew tracker phone lines from Secure GPS
Customers who manage lines associated with their trackers received an option to review, administer, and renew those lines from the corresponding area. Device monitoring and connectivity continuity can therefore be handled through a more integrated experience.
This capability helps prevent interruptions caused by an expired line. A business can review its tracker lines, identify those that require attention, and renew them in advance instead of finding the issue only after a vehicle stops reporting.
Line management availability depends on the service associated with each account and tracker.
Redeem points and use available benefits
The release added SDG points redemption. Eligible users can open the option and apply their points to the benefits available through the corresponding process.
In daily use, this turns an accumulated balance into a useful action without a separate management request. The workflow uses the correct user and alternate contact information to support the redemption process. Available options and conditions depend on the balance and current service rules.
Download all statistics for a GPS device
Secure GPS expanded its data output so users can download all available statistics for a device. Instead of relying only on the on-screen view, customers can retain the complete available set and use it in their own analysis and control processes.
This is useful for operational reports, usage reviews, period comparisons, and sharing results with other departments. A fleet manager, for example, can download a vehicle's statistics and use them in a performance meeting, route review, or driving-behavior analysis.
The available values depend on the information transmitted by the tracker and the functions enabled for the account.
REST API for devices, locations, and alerts
For teams that need to connect Secure GPS with another application, this version introduced a REST API protected with a Bearer access token. The integration authenticates authorized users, including subusers, and lets them query the devices assigned to them.
The subuser's scope is preserved in the integration. An application does not receive unrestricted access to the entire account: queries are limited to devices authorized for that user, apply to enabled trackers, and remain subject to the applicable usage limits.
The first public version supported use cases such as:
- Last location: obtain the latest available position for an authorized device.
- Locations by period: retrieve coordinates and movement data within a requested interval.
- Alerts by period: query device events and optionally filter them by alert name.
Location responses may include date and time, latitude, longitude, speed, course, battery, fuel, temperature, sensor times, inactive time, engine revolutions, mileage, and additional attributes when the tracker transmits them. Alert responses may include date and time, coordinates, event text, alert types, and notification indicators.
In a real application, an integrator can display the last position in a customer-service system, populate an operations dashboard with recent movement, or connect GPS alerts to an authorized workflow. The advantage is being able to use tracking information where the business needs it while retaining the permissions configured in Secure GPS.
To protect the service, historical location and alert queries in this release used a maximum 60-minute interval. Integrations should validate success and error responses, respect query limits, and never expose the token in public applications or logs.
Support for iStartek GPS trackers
Secure GPS added support for the iStartek protocol, expanding the tracker models that can send data to the platform. The implementation interprets position and operating details such as date, coordinates, speed, course, altitude, mileage, signal quality, inputs, outputs, and voltages when reported by the device.
It also recognizes compatible events such as panic button, input activation or deactivation, power disconnection, low battery, harsh acceleration or braking, and vibration. Customers using iStartek hardware can therefore centralize monitoring in Secure GPS and use maps, history, and alerts according to the tracker's actual capabilities.
Protocol support does not mean that every model provides every field. Before installation, customers should confirm the exact model, configuration, and data transmitted by the tracker.
Correct speed handling for H02 trackers that report km/h
The H02 family gained the H02.Km variant for devices that send speed directly in kilometers per hour instead of knots, as defined by the original H02 protocol. This distinction prevents a conversion from being applied when it does not match the tracker's actual format.
For customers, the benefit is more consistent speed information across maps, route history, statistics, and related alerts. When an H02 model produced disproportionate values because it used a different unit, selecting the compatible variant allows Secure GPS to interpret that value correctly.
New Intellitrac event and smoother mobile purchases
Secure GPS also expanded Intellitrac processing with support for a new event. Operations using these trackers can make better use of the information their devices send to the platform.
The purchasing experience gained a field for entering an advisor code, color controls became easier to use from mobile devices, and annual subscription activation was corrected. These refinements reduce errors when completing a purchase or configuring visual elements from a touchscreen.
One release for access, data, and connectivity control
Together, these features help customers protect accounts, review sensitive activity, administer related services, download operational data, and connect locations and alerts with other authorized processes. Wider protocol support also creates more hardware choices while keeping GPS monitoring centralized.
Current availability may depend on the plan, user permissions, contracted service, and tracker compatibility. Explore Secure GPS plans and features to review the capabilities offered today.