Privacy Policy for GPSDome and GPSDome Fleets

This policy describes two mobile applications: GPSDome on Android and GPSDome Fleets on iOS. One policy covers both. Useful Systems IT (US IT) is the data controller responsible for personal information processed through these applications.

Effective date: 1 September 2026 · Privacy contact: support@gpsdome.net

USIT creates and administers the customer accounts and issues the username and password. A customer does not register or create an account in either application. Both applications sign in to track.gpsdome.net.

1. Information collected

1.1 Sign-in details

The username or email entered on the sign-in screen, and the password, are sent to track.gpsdome.net. After sign-in, the application stores a session value on the phone. If the user chooses to be remembered, that session value remains on the phone. The password is not stored in that local record.

1.2 Vehicle information

The applications receive the signed-in account's vehicle and fleet records from track.gpsdome.net, including vehicle identity, status, position, history, events, and geofences returned for that account.

1.3 Phone location

When the user taps My Location, the applications read the phone's position while the application is in use and show it on the map. The phone position is not sent to track.gpsdome.net.

1.4 Push token

If the user allows notifications, the applications use Firebase Cloud Messaging to obtain a push token and send that token to track.gpsdome.net for the signed-in account.

1.5 Information kept on the phone

The applications store the session value, the notification token, and the user's language, appearance, and map settings on the device.

2. Location and GPS tracking

Vehicle positions, history, and events shown in GPSDome and GPSDome Fleets come from track.gpsdome.net.

The phone's own location is read when the user taps My Location. The read is used to show that position on the map while the application is in use. Android requests approximate and precise location for that use. iOS requests location in order to show My Location. The iOS background modes included in the application are background fetch and remote notifications. The phone position is not sent to track.gpsdome.net.

3. Maps and address lookup

The user can view the fleet on Google Maps or on OpenStreetMap. When OpenStreetMap is selected, the applications request map tiles from the OpenStreetMap tile service. To show an address for a vehicle, the applications send that vehicle's latitude and longitude to nominatim.openstreetmap.org. The user may share a vehicle name and a Google Maps link through the phone's share sheet. The user chooses the destination.

4. Firebase Cloud Messaging and push notifications

If the user allows notifications, GPSDome and GPSDome Fleets use Firebase Cloud Messaging to obtain a push token. The applications send that token to track.gpsdome.net for the signed-in account. Android also requests permission to show notifications. Signing out deletes the push token stored on that phone. The applications do not send a removal request for a token stored on the server.

The reviewed application dependencies do not include an advertising SDK, a crash-reporting SDK, or an analytics SDK. In the iOS Firebase configuration file, the advertising and analytics flags are turned off.

5. Third-party services and data processing

track.gpsdome.net receives the sign-in details, fleet requests, and push token. It is the tracking service these applications are built to use.

When the related feature is used, the applications also contact:

• Firebase Cloud Messaging, to obtain the push token.
• Google Maps, when that map is selected and for the map link offered through the share sheet.
• OpenStreetMap tile servers, when that map is selected.
• nominatim.openstreetmap.org, to turn a vehicle coordinate into an address.
• Google Play on Android, to check for an application update.

A share-sheet destination receives a vehicle name and map link only when the user chooses that destination.

6. Data retention and security

While the user remains signed in, the applications keep the session value, notification token, and selected settings on the phone. Signing out removes the session value and the push token stored on that phone. Removing the application from the phone removes the information stored by the application on that phone.

The applications connect to track.gpsdome.net over HTTPS.

7. Account deletion and data removal requests

GPSDome and GPSDome Fleets do not contain an account-deletion control.

A customer, or a person authorized to act for the customer, may email support@gpsdome.net to ask USIT to review an account. The message should include:

• GPSDome or GPSDome Fleets
• the username
• whether the request concerns one login or the company account
• the name of the requester and the company represented

USIT receives the request, verifies the requester's identity and authority, and reviews the request. A request about one login and a request about a company account are reviewed separately. USIT confirms the outcome of that review to the requester.

Signing out ends the session on that phone and deletes the push token stored on that phone. The account remains on track.gpsdome.net. Removing the application from the phone also leaves the account on that server. The applications display vehicle records and GPS history from that server and do not delete them.

8. Contact

Useful Systems IT (US IT)
support@gpsdome.net