Privacy Policy

§ 1

Who is responsible for the data

The GPS LocaL app is published by Alla Petrivna Mostova, sole proprietor (FOP), Ukraine. For any question about data — supportgpsresource@gmail.com. This is the same address shown on the app's store page, and the developer answers it personally.

The division of roles, and it is the main point here. Data about your vehicles, drivers, routes and addresses is the responsibility of the owner of the Wialon Local installation you connect to — usually your company or your monitoring service provider. They decide what data is collected and how long it is kept. The app merely shows it on your phone screen.

§ 2

What data the app processes

2.1. Provided by you

There is no password among these. It is entered on Wialon's own page and never reaches the app.

2.2. Collected technically

2.3. Vehicle data

Locations, routes, sensor readings, vehicle names — all of this is stored on your company's Wialon Local server. The app receives it for display and holds it in memory while it is open. The developer has no access to it.

§ 3

Where data leaves the device

There are three destinations, and none of them belongs to the developer.

It was not always so: until September 2026 the app registered itself with the developer's notification server, and there were four destinations. That registration has been removed — see § 5.

3.1. The Wialon Local server you specified

Everything to do with the work goes there: requests for the list of objects, history, reports, commands to the tracker, and notification rule triggers as well. You choose this server's address — the app never contacts a server you have not entered.

Connections are encrypted only (HTTPS). The app rejects unencrypted ones, and certificate validation is never switched off.

3.2. Google and Apple services

• Firebase Cloud Messaging — Google issues the installation a technical token; on iPhone, Apple's notification service takes part in this as well. The token is obtained but not currently used: the app reads rule triggers itself, from your own server (see § 5). It is kept in case delivery with the app closed is ever needed.
• Firebase Remote Config — the app asks Google for settings: the minimum supported version and the list of supported servers. Only technical details about the app installation are transmitted.
• Subscription payment — if you take one out. The payment is handled entirely by the store the app was installed from: App Store on iPhone, Google Play on Android. The developer sees neither your card details nor your billing address.

Google and Apple may process this data outside Ukraine, in particular in the EU and the USA, under their own data protection mechanisms.

3.3. Map server

Map imagery is loaded from a third-party map server. It learns your device's IP address and the map area you are viewing. No data about your vehicles is sent there — vehicle markers are drawn on the device, on top of the loaded imagery.

§ 4

The grounds we rely on

• Performance of a contract — everything the app cannot work without: connecting to your server, storing the access token, displaying data.
• Your consent — notifications: the system asks for permission separately, and you can withdraw it at any time in your phone settings.
• Legitimate interest — the diagnostic report for support, and only when you have decided to send it yourself.

§ 5

Notifications

The app reads rule triggers from the history of your objects on your own Wialon server — the server leaves ready-made text there if the rule has the action “Register event for unit”.

The banner on the screen is drawn by the app itself, on the device. No developer server takes part in this chain.

A consequence worth knowing: notifications arrive while the app is open or in the background. Once the system unloads it from memory, there is nobody left to read the history.

It used to be different. Until September 2026 the app registered itself with the developer's notification server, sending it the device token, your Wialon user id and login, your server address and the ids of your resources. That is gone. The app contacts that server once more — to delete the record if one is left over from earlier versions; after the deletion it does not contact it at all.

The notifications switch stops the reading and removes the banners.

§ 6

Sharing a vehicle's location (locator)

This feature creates a temporary link on your own Wialon server. Whoever opens it will see the selected vehicle on a map — with no sign-in and no password, for the period you choose (one hour, three hours, a day or a week).

What to understand before you share it:

• The link is a key. Forwarded on, it works for anyone who received it until the period ends.
• It cannot be revoked early — Wialon itself has no such option.
• The link gives view only of one vehicle's current location. Neither route history, nor geofences, nor tracker control are available through it.
• You create it, and you decide who to send it to. The developer neither sees nor stores these links.

§ 7

Diagnostic report

The settings contain a “Diagnostic report” — it is needed when you ask for help. The report is assembled on the device and contains the phone model, system version, user name, server address and the last lines of the app's log. Access tokens and session identifiers are stripped from it automatically.

The report is never sent anywhere by itself. You see its text on screen, and only you decide whether to copy it and to whom to send it.

§ 8

What is kept on the device, and for how long

App storage is not accessible to other apps on the device.

Backup is switched off. Both Android and iPhone copy app data to the phone owner's cloud by default — Google Drive or iCloud. We disabled that: the notification log and the settings contain your client's vehicle names and addresses, and they have no place in a dispatcher's personal account.

The developer stores none of your data at all — there is nowhere to store it.

§ 9

What the app does not do

§ 10

Your rights

Since the developer stores none of your personal data, most requests concerning data about vehicles and drivers should be addressed to the owner of your Wialon Local installation — they are the one who controls it.

Whatever concerns the app itself you can achieve yourself, immediately:

• “Switch user” — removes the access token, leaving the server address as a hint.
• “Sign out” — removes the record entirely and unsubscribes the device from notifications.
• Deleting the app removes everything from the device: the token, the notification log, the settings.

If you still have questions about how the app processes data — write to supportgpsresource@gmail.com. We reply within 30 days.

§ 11

Security

• The access token is kept in the system's hardware-backed storage (Keychain on iPhone, Keystore on Android) and never leaves the device.
• All connections are encrypted; the app rejects unencrypted ones.
• Server certificate validation is never switched off, under any circumstances.
• Backup of the app's data is disabled.
• If you wish, you can enable a biometric lock: the app will ask for a fingerprint, face or passcode when opened and after a minute in the background.

No system is absolutely secure. We take reasonable measures, but cannot guarantee protection against every possible threat — in particular those that arise outside the app: a lost phone, malicious software on it, third-party access to an unlocked device.

§ 12

Limitation of liability

The app is provided “as is”. To the extent permitted by the legislation of Ukraine, the developer is not liable for:

• incompatibility with particular phone models, system versions and manufacturers' shells. Manufacturers manage background processes, permissions and power saving differently; because of this, notifications may arrive with a delay or not arrive at all on certain devices;
• any actions of the user or of third parties that led to disclosure or leakage of data — in particular passing a locator link to outsiders, handing the device to other people, working with an unlocked phone, saving screenshots;
• indirect losses — lost profit, vehicle downtime, disrupted transport plans, damage to property — arising from use of the app, its unavailability, or incorrect or untimely data;
• the accuracy, completeness and timeliness of the data that comes from the Wialon Local server, the GPS hardware and the mobile network. The app only displays it, and can be responsible neither for how the trackers work, nor for the quality of the satellite signal, nor for the server's availability;
• interruptions caused by lack of internet, maintenance on the client's server, changes in the Wialon API or in Google or Apple services.

These limitations do not extend to cases of intent or gross negligence on the developer's part, nor to consumer rights that cannot be limited by law.

Decisions affecting people's safety or the protection of property must not be taken on the app's data alone. This is an observation tool, not a response system.

§ 13

Children

The app is intended for professional use and is not addressed to children. We knowingly collect no data of persons under the age of 18.

§ 14

Changes

If the policy changes, the updated revision will appear at this same address, and the revision date at the top will change. Significant changes will additionally be explained in the app's update notes.

§ 15

Questions

Write to supportgpsresource@gmail.com — the developer answers personally. The app is published by Alla Petrivna Mostova, sole proprietor (FOP), Ukraine.