Skip to content
All guides

GPS tracking

Connect your GPS platform read-only or have your trackers send straight to Rentoth, link each tracker to its car, then use the map, kilometres and alerts.

8 min read ·

1. First, your CNDP authorisation

Tracking cars driven by your customers is your agency's own processing of personal data. It needs your agency's prior authorisation from the CNDP (law 09-08), and each renter must be told in the contract before any data is collected. Until the account owner has switched on the geolocation clause in Settings and entered the authorisation number, Rentoth collects nothing and shows no position. Managers can prepare the connections meanwhile.

2. Connect your GPS platform

Rentoth reads, read-only, the platform your trackers already send to: Wialon, Traccar, Navixy, GPSWox or flespi. You keep your installer and your subscription. Ask your installer for a read-only access: a token or a sub-user that cannot send commands. No platform? Compatible trackers can send directly to Rentoth instead: see section 8.

  • Open Tracking, then Connections, and choose your platform.
  • Enter your platform's address when it is asked for (https only) and the access your installer gave you. For Wialon, the "Get a token" link opens Wialon's own sign-in page.
  • Press Test: Rentoth shows how many trackers it finds. Then save.
  • The access is stored encrypted and never shown again. Replace it when your installer changes it; pause or delete the connection at any time.

3. Link each tracker to its car

In the connection's list of trackers, Rentoth suggests a car for each one, with the reason and how sure it is: same plate, same chassis number, same identifier, same plate digits, or the name. Accept the suggestions you agree with, or choose the car yourself: nothing is linked until a manager confirms it. A linked car is marked as having a tracker, so its next contracts carry the geolocation clause.

4. The map and each car's panel

Tracking shows your linked cars on a map, refreshed every 30 seconds while the page is open, with a list you can search and filter: rented, available, silent, alerts. A car's panel gives its last position with a link to Google Maps, its speed, ignition, odometer, the time of its last signal and its route over the last hours. Counter staff see the map; managers also handle the connections and the settings. Views are noted in the access log: who opened the map, a car's panel or its route, at most one line per person every 10 minutes.

During a rental recorded in Rentoth whose contract does not carry the geolocation clause, Rentoth records no position for that car, only the time of its last signal and its kilometres; a tracker that sends to Rentoth's own server is paused until the rental ends, so that car has no silent-tracker alert and no GPS kilometres at return. Record every rental in Rentoth before the car leaves: a car out on a rental Rentoth does not know is treated as parked, so its positions are recorded and a "Moved while not rented" alert goes off.

5. Kilometres at pickup and return

When you create a contract or record a return, the kilometres read from the tracker appear beside the mileage field. Check them against the car's dashboard: nothing is saved until you save the form. A tracker that counts kilometres by GPS drifts a little; when your staff correct the value, Rentoth adjusts its next suggestions for that car.

6. Alerts

Rentoth warns you in the dashboard when a car moves about 500 m or more with no rental in progress, and when a rented car's tracker has sent nothing for the number of hours you choose (2, 6, 12 or 24). Moving a car yourself? Mute its alerts for 2, 6 or 24 hours from its panel. When a connection stops working, managers see why and fix it in Connections.

7. How long data is kept, and who sees it

You choose how long positions are kept: 7, 30 or 90 days (30 by default); lowering it deletes the older positions the next night. Tracking alerts are kept 90 days and the access log 12 months. Rentoth uses this data only for your agency: its own team does not see positions, and it never cuts an engine or sends any command to a car. It is monitoring help, not a security or recovery service.

8. Trackers that send directly to Rentoth

Compatible trackers can send their data straight to Rentoth's own tracking server instead of a platform. Once the geolocation clause is on, a manager opens the Hub tab of Tracking, enables the hub for the agency, then adds each tracker with its identifier (usually its IMEI), its brand and its car. Add it before your installer sets it up: the server ignores identifiers it does not know. The dashboard then shows your installer the address, the port and the set-up steps for its brand, with the SMS to send when it is set by SMS. Let your installer do it: a wrong message can cut a tracker off its server. A tracker that sends only to Rentoth no longer reports to your installer's app, nor to its engine cut-off, unless it can send to two servers. The server keeps the raw positions it receives for 7 days. Keep your trackers' identifiers private. Each tracker on Rentoth's server has a monthly fee, added to your subscription: the Hub tab shows it before you enable the hub, and the pricing page lists it. Connecting your own platform (section 2) stays included.

  • Teltonika (FMB920, FMB120, FMB140, FMC003…): port 5027, set in Teltonika Configurator or by SMS.
  • Concox / Jimi (GT06, GT06N, GT800, Wetrack): port 5023, set by SMS.
  • Queclink (GL300, GV55, GV300…): port 5004, set with the Queclink Manage Tool.
  • Coban (GPS103, TK103A/B, TK102): port 5001, set by SMS with the server's IP address.
  • Ruptela (FM-Eco4, FM-Pro4, Trace5): port 5046, set with Ruptela's configurator.
  • Sinotrack and other H02 trackers (ST-901, ST-906): port 5013, set by SMS. Register the 10-digit ID the tracker reports, not its IMEI.
  • TK103 clones: port 5002, set as the tracker's manual says.
  • Every tracker: a model approved by the ANRT, a SIM with mobile data and its operator's APN, and one tracker tested before the whole fleet.