RevHostGPS Service Terms

These terms describe what RevHostGPS tracking does, what it does not do, and what you are agreeing to when you activate a device on one of your vehicles. Please read the Limitations section in particular — several of these limits are not obvious, and the worst time to learn them is during a dispute, a damage claim, or a theft.

1. What RevHostGPS is

RevHostGPS is a vehicle telematics and tracking service. A cellular tracking device installed in your vehicle reports its position and driving data to RevHost over a mobile network, and RevHost displays that data to you in your dashboard, alerts you to certain events, and — on supported hardware — relays commands you send to the vehicle.

The service consists of the device, the RevHost-managed SIM and cellular data plan inside it, and your access to the data in RevHost. It is billed per vehicle, monthly, as part of your RevHost subscription.

2. What RevHostGPS is not

RevHostGPS is a tracking and telematics tool. It is not a theft-prevention system, a vehicle-recovery service, a security system, or an emergency service. Specifically:

• It will not stop anyone from stealing your vehicle. A tracking device is passive. It does not immobilize a vehicle on its own, does not sound an alarm to bystanders, and does not physically prevent a theft in progress.
• It does not guarantee recovery of a stolen vehicle. A determined thief can unplug or remove the device, shield or jam its signal, disable its power, or move the vehicle on a flatbed tow truck — none of which the device can prevent.
• RevHost does not monitor your vehicles. There is no monitoring center, no staff watching your fleet, and no one who will notice an event and act on it for you. Alerts are delivered to you. Responding to them is yours.
• RevHost does not contact police, dispatch anyone, or coordinate recovery. In a theft, you contact law enforcement. We can help you retrieve the position data we hold; we cannot act on it for you.
• It is not an emergency service. Do not rely on RevHostGPS in a situation involving a risk to safety. Call emergency services.

RevHostGPS improves your visibility into where your vehicles are and how they are being driven. Any security benefit is indirect, and no outcome is guaranteed.

3. What the service can do

Depending on your device model and vehicle, the service may provide:

• Live position. The last position the device reported, shown alongside how old that reading is.
• Trip history, where trip assembly is active for your device: start and end time and place, route travelled, distance and speeds, for trips recorded while the device was installed on that vehicle. See §3.1 — this one is not available on every device, and your vehicle's page is the authority on whether it is.
• Driving events. Harsh braking, harsh acceleration, sharp cornering, speeding above a configured threshold, and possible-collision detection.
• Geofence and speed alerts based on rules you configure. A geofence alert is triggered by a crossing — the vehicle entering an area, or leaving it — and not by the vehicle being inside one. You choose the areas and whether each rule watches entries, exits, or both. A rule you create is active at all times by default, including while a guest has the vehicle — you can narrow any rule to run only between rentals, and §7 explains why that choice matters. Geofence alerts appear in your RevHost dashboard; we do not currently send them by push notification, SMS, or email. See §4.9 for what this cannot detect.
• Tamper and power alerts. Notification when the device loses external power, and detection of vehicle movement while the ignition is off.
• Vehicle data over the OBD/CAN connection — odometer, fault codes, fuel data, battery voltage — on models that read it, and only when the vehicle actually exposes it.
• Remote commands— door lock/unlock and starter disable (“kill switch”) — on hardwired models only, and only after professional installation and per-vehicle calibration.

3.1 Capability depends on the device, not on your plan

Two vehicles on the same RevHost plan can have different capabilities because they have different hardware. What your device can do is fixed by its model:

Trip history is marked “varies” deliberately.Whether a vehicle's movements are assembled into named trips depends on how its device reports into our platform, not on which model it is. Where trip assembly is not active for a device, your dashboard says so on that vehicle and you still get live location, driving events and alerts. Do not assume a trip list exists for a given vehicle without checking that vehicle's page.

The RH505uses the OBD-II port for power only. It does not read the vehicle's data bus, so it reports no odometer, no fuel data, and no fault codes — its mileage figures are estimated from movement, not read from the car.

Even on models that do read the data bus, availability depends on the individual vehicle. Some vehicles do not expose a usable odometer, fuel level, or fault-code channel, and some hardwired installations require the data connection to be wired and enabled before any of it appears. A device can be installed, online, reporting position correctly, and still show no odometer.

4. Limitations you should expect

4.1 It depends on a cellular network. No signal, no reporting.

The device reports over a mobile network. Where there is no usable signal, it cannot report, and your dashboard will show the last position it managed to send. This is normal and expected in:

• underground and multi-storey parking garages
• enclosed metal or concrete structures, workshops, and shipping containers
• tunnels
• rural and remote areas with weak or no coverage
• areas where the local network has been congested, has failed, or where signal is being deliberately jammed

The device stores data locally while it is out of coverage and uploads it when the network returns, so trip history usually fills back in. Live tracking does not. A vehicle parked in a garage may be invisible for as long as it stays there.

4.2 It depends on satellite positioning

Position comes from satellite navigation signals (GPS and other GNSS constellations), which need a view of the sky. Indoors, underground, or under heavy obstruction the device may hold no fix at all, or report a degraded one. Position accuracy is approximate in all conditions and is not survey-grade.

4.3 “Live” is not real time

The map shows the last position the device reported, not the vehicle's current position. While a vehicle is moving and in coverage, updates typically arrive every few seconds. Outside those conditions a pin can be minutes or hours old. RevHost always shows the age of the reading next to it — read the age before acting on the pin, and never present a stale position as the vehicle's current location.

The same applies to alerts, including geofence alerts. An alert can only be as timely as the report that triggered it, so it may arrive well after the event and, where the device never reported, not at all. The absence of an alert is not evidence that nothing happened, or that a vehicle stayed where you left it. Do not treat silence as confirmation.

4.4 A parked vehicle produces no position history

Position is recorded as trips. To conserve the vehicle's battery and the device's data allowance, the device suppresses reporting while the vehicle is stationary. A car parked from Friday to Monday leaves no position records for that period — only the end of the previous trip and the start of the next.

There is no continuous, second-by-second location log of your vehicles. If you need to establish where a vehicle was at a specific moment while it was parked, the answer is “where its last trip ended”, not a recorded position for that time.

4.5 History fidelity degrades after 180 days

Trip detail is kept at full fidelity — position, time, and speed for each point — for approximately 180 days. After that, trips move to long-term archival storage and RevHost displays a simplified route shape instead: the path the vehicle took, without the per-point timestamps or speeds.

This means a question like “where exactly was this car at 2:32 pm?” can be answered for a recent trip and cannot be answered from the displayed data for an old one. Late-arriving disputes are exactly the ones that land past this line. If you may need full-fidelity detail for a specific trip, export or save it before it ages out. RevHost may be able to restore archived detail on request; restoration is not instant and is not guaranteed.

4.6 The device can be removed, and a removed device stops reporting

Plug-in models are removed by hand in seconds. Hardwired models require tools, but can still be cut out. When a device loses external power it sends a power-loss alert within seconds and then continues to report from its small internal backup battery for a short period — on the order of minutes, not hours — before going silent entirely.

A device with no power reports nothing. RevHost cannot locate a vehicle whose device has been removed, destroyed, or run out of backup power, and cannot recover the positions it did not send.

4.7 Cross-border travel is supported, but not guaranteed

The devices ship with a RevHost-managed SIM that roams internationally, and vehicles driven between the United States, Canada and Mexico will generally keep reporting. Coverage nonetheless depends on our carrier having a roaming agreement in that country and on the local networks supporting the radio technology your device model uses. Coverage outside the United States is not uniform, and the plug-in and hardwired models do not use the same cellular technology, so they may behave differently in the same place.

RevHost does not warrant coverage, service quality, or continuity of reporting in any particular country, region, or location. Do not remove, replace, or reconfigure the SIM to try to improve it — see section 6.

4.8 The service depends on systems outside our control

RevHostGPS relies on satellite positioning systems, mobile network operators, the device manufacturer's platform, cloud infrastructure providers, and the device hardware itself. Any of these can fail, be interrupted, be taken down for maintenance, or change. The service is provided on an as-available basis with no uptime guarantee, no guaranteed reporting interval, and no guarantee that any specific alert will be generated or delivered.

Data may be delayed, incomplete, out of order, or missing. Do not use RevHostGPS as the sole basis for a decision with legal, financial, or safety consequences without corroborating it.

4.9 What geofence alerts cannot detect

Every limitation above applies to geofencing, and two of them combine into a gap worth stating on its own. A geofence crossing is detected by comparing reported positions, so the device has to be reporting for a crossing to be seen at all.

• A vehicle moved without its ignition on may not generate a crossing. The device suppresses reporting while stationary (§4.4), and while it also raises an alert on unexpected movement, a vehicle that is towed, winched, or carried out of an area may leave it without producing a geofence alert.
• A vehicle out of coverage produces no crossing while it is out of coverage. A car driven out of an area from an underground garage, or through a long gap in network coverage, may be reported only once it resurfaces — somewhere else, later.
• Positions are approximate (§4.2), so boundaries are approximate. To stop a parked vehicle near a boundary from raising endless alerts as its reported position drifts, a crossing must clear the boundary by a margin and hold before it is reported. Movement of a few metres across a line will not, and should not, alert.

Geofencing is a monitoring convenience, not a containment or recovery system. Read it together with §2: this is not a security system, and it is not theft prevention.

5. Remote commands and the kill switch (RH863 only)

Hardwired devices can relay door lock/unlock and a starter-disable command. These carry obligations that ordinary tracking does not.

• Never disable a vehicle that is moving or occupied. The starter-disable function is intended to prevent a stationary, unoccupied vehicle from being started. Using it in any other circumstance can create a serious safety hazard and may expose you to criminal and civil liability.
• Commands are not guaranteed to arrive or to succeed.They travel over the same cellular network as everything else. A command may be delayed, may fail silently, or may not reach a device that is out of coverage or unpowered. Never rely on a command having taken effect without confirming the vehicle's state.
• Correct behavior depends on correct installation. Lock/unlock and starter disable are wired into each individual vehicle and must be calibrated per vehicle by your installer. An uncalibrated or miswired installation can produce the wrong result.
• You are responsible for how you use these commands, including compliance with the laws of your jurisdiction, with your rental or car-sharing platform's rules, and with the agreement between you and your guest. Many jurisdictions restrict remotely disabling a vehicle. RevHost provides the capability; the decision to use it and the consequences of using it are yours.

6. The device, the SIM, and installation

• The SIM and data plan are managed by RevHostand are part of the service. Do not remove, replace, or transfer the SIM, and do not change the device's network, APN, or server settings, or send it configuration commands. Doing so breaks connectivity, is not covered by warranty, and is not something support can always undo remotely.
• Plug-in devicesconnect to the vehicle's OBD-II port and can be installed by you. Hardwired devicesmust be installed by a qualified professional; incorrect wiring can damage the vehicle's electrical system and is not covered.
• You are responsible for the device being installed and functioning. A device that has been unplugged, damaged, disconnected during service work, or installed in a vehicle with a faulty OBD-II port will not report, and RevHost will not necessarily know.
• Hardware warranty is 12 months from delivery against manufacturing defect. It does not cover physical damage, water damage, unauthorized modification, incorrect voltage, tampering, or removal of identifying marks. Hardware terms are separate from this service agreement, as are the terms of any promotional or prepaid offer you purchased under.
• Trip history belongs to the vehicle, not the device. Moving a device to a different vehicle does not move the history it already recorded. A vehicle showing no recent trips may mean its tracker was moved, not that the vehicle did not move.

7. Privacy, guests, and your legal obligations

A vehicle on rental has a person in it. Tracking that vehicle is tracking that person. This is the part of the service most likely to create legal exposure for you, and it is your responsibility, not RevHost's.

• You must disclose the tracking to your renters. Many jurisdictions require that a driver be told a vehicle is equipped with a tracking device, and some require explicit consent or restrict how the data may be used. Your rental agreement and listing must reflect what this service actually does, including any use of a starter-disable function.
• You are the controller of your fleet's data. You decide who in your organization sees it. If you grant access to staff, co-hosts, or a virtual assistant, you are responsible for their use of it. Position lookups performed by delegated back-office users are recorded.
• Geofencing during a rental is automated monitoring of your guest, and it is on by default. A geofence rule that stays active while a vehicle is rented does not merely record where the car went — it watches for your guest crossing a boundary you drew and notifies you when they do. That is a step beyond looking up a position, and in some places it is treated differently in law. Because a rule runs at all times unless you narrow it, creating any geofence is enough to begin monitoring your guests— you do not have to switch anything on. Your rental agreement and listing must disclose it, and your disclosure must cover being alerted on the guest's movements, not merely that the vehicle has a tracker.
• The default is ours; the obligation is still yours. We arm rules at all times by default because the events hosts most need to know about — a vehicle that does not come back, one crossing a border or leaving the state — happen during a rental, and a rule that stands down for the duration of the trip would not report them. That is a deliberate choice on our part, and it does not transfer the duty: you remain responsible for disclosing the monitoring and for complying with the law where the vehicle is rented and driven. Each rule can be set to run only between rentals, only during them, or always, and a rule limited to periods when no guest has the vehicle monitors nobody. If the law that applies to you does not permit monitoring a renter, or you would rather not, narrow the rule — the control is on the same screen where you create it.
• Use the data for legitimate fleet purposes. Do not use RevHostGPS to monitor a person for reasons unrelated to operating your vehicles, to harass or stalk anyone, or in any manner prohibited by law. RevHost may suspend service for misuse.
• RevHost may access your telematics data to operate, support, secure, and improve the service, to respond to your support requests, and where required by law or valid legal process. Our general handling of your data is covered by the RevHost Privacy Policy.

8. Data retention and deletion

• Full-fidelity trip detail — position, timestamp, and speed per point — is available for approximately 180 days.
• After 180 days, trips remain available as a simplified route shape without per-point timestamps or speeds, as described in section 4.5.
• Telematics data is retained indefinitely unless you ask us to delete it. RevHost does not automatically purge historical trip data today.
• Deletion on request. You may ask RevHost to delete the telematics history for a vehicle or for your account by contacting support. Deletion is permanent and irreversible: once deleted, the data cannot be produced for a later dispute, insurance claim, or law-enforcement request. We may retain data we are legally required to keep, and may decline or defer a deletion while it is subject to a legal hold.
• Removing a device or a vehicle does not delete history. Deactivating a device or removing a vehicle from your fleet stops new data being recorded; it does not erase what was already recorded.

9. Billing

• GPS service is billed per vehicle, per month, added to your RevHost subscription. The per-vehicle rate depends on how many vehicles you have on the service — the more vehicles, the lower the per-vehicle rate.
• Activation charges immediately and is prorated. When you activate a device mid-cycle you are charged for the remainder of the current billing period, and the full rate applies from your next renewal. The exact amount is shown to you before you confirm.
• Removing a device does not produce a refund or credit. Service continues to the end of the current billing period and simply does not renew for that vehicle. You pay for any billing period in which a device was attached to a vehicle at any point.
• Moving a device between your own vehicles is free. It does not create a new charge.
• Unpaid accounts lose GPS access. If a payment fails, GPS features are paused until the payment method is updated. Devices may continue to record during that period, but you will not be able to see the data.
• Prepaid and promotional plans are governed by their own terms, which override this section for the vehicles they cover.

10. Disclaimer and limitation of liability

RevHostGPS is provided “as is” and “as available”. To the fullest extent permitted by law, RevHost disclaims all warranties, express or implied, including any warranty of merchantability, fitness for a particular purpose, accuracy, continuity of service, or that the service will prevent, detect, or assist in resolving any theft, damage, loss, or dispute.

RevHost is not liable for loss of or damage to a vehicle, loss of revenue, loss of data, or any indirect, incidental, special, or consequential damages arising from the service, from its unavailability, from inaccurate or missing data, from a device failing to report, or from an alert or command not being generated, delivered, or acted upon. Nothing in these terms excludes liability that cannot lawfully be excluded.

RevHost's total liability arising out of the GPS service is limited to the GPS service fees you paid for the affected vehicle in the twelve months before the event giving rise to the claim.

These terms supplement, and do not replace, the RevHost Terms of Use and Privacy Policy. If they conflict on a point specific to GPS service, these terms govern.

11. Changes to these terms

RevHost may update these terms. The version in force is always published at /gps-terms and is dated. Activating an additional device means accepting the version in force at that moment. Material changes affecting existing service will be communicated to you; continuing to use the service after a change means you accept it.

12. Contact

Questions about the service, requests to delete telematics data, and device support all go through RevHost support.