Skip to content

Bluetooth tire monitoring for travel trailers

Know every tire.
Every mile.

Spartan RV TPMS gives you a clear view of tire pressure, temperature, leak, battery, and missing-sensor conditions on Android and iOS. Keep essential tire status close at hand on your phone and compatible vehicle display.

Android and iOSAndroid Auto & Apple CarPlayBluetooth Low Energysingle, dual, or triple-axle layouts
Spartan RV TPMS app icon
Spartan RV TPMS monitoring screen with simulated sample readings
Actual app screen · simulated sample readings.

Built for the road ahead

Important tire information,
without the clutter.

See each paired sensor in its tire position, so the tire that needs attention is easy to identify.

PSI

Live pressure and temperature

View readings in PSI or kPa and Fahrenheit or Celsius.

!

Clear safety alerts

Recognize fast leaks, pressure warnings, high temperature, low batteries and missing sensors.

RV

Your trailer layout

Choose a single-, dual-, or triple-axle layout and include an optional spare.

BLE

Background monitoring

Continue receiving compatible sensors with the screen off, subject to phone permissions and power settings.

LOG

Trips History

Review saved readings and offline charts on Android, and export a trip as CSV.

QR

QR scanning & sharing

On Android, share or scan a setup QR, then review sensor assignments before applying it.

More from your TPMS app

Review the trip.
Share the setup. Stay informed.

Trips History

On Android, review saved trips and offline pressure and temperature charts. Export a trip as CSV when you want to keep or share its records.

Settings → Trips History

Spartan RV TPMS Android Trips History pressure and temperature charts using synthetic sample records
Android app capture · sample records.
Explore Trips History →

QR scanning & sharing

On Android, share your trailer setup as a QR image, or use Scan asset QR with your camera. Review the layout, baselines and sensor assignments before applying a scanned setup.

Settings → QR Asset Sharing

Spartan RV TPMS Android QR Asset Sharing screen with a fictitious example setup
Android app capture · example setup.
See QR scanning & sharing →

Android Auto & Apple CarPlay

Use Android Auto with the Android version or Apple CarPlay with the Apple version to view tire status on a compatible vehicle display. Complete setup on your phone while parked.

Compatible phone & vehicle display

Spartan RV TPMS Android Auto display with simulated tire readings
Android Auto capture · sample readings.
Check display compatibility →

Guided setup

Ready in four clear steps.

Configure your trailer while safely parked.

01

Choose your trailer

Select the axle layout and optional spare.

02

Pair each sensor

Start a fresh scan for one tire position and follow the compatible sensor's learn procedure.

03

Set baseline & units

Use your vehicle's placard pressure and choose your display units.

04

Finish and monitor

Confirm the setup and check fresh readings from every paired tire.

During Android setup, readings continue while audible alerts remain quiet. A one-minute quiet period follows Finish Setup.

Help inside the app

Guidance is a tap away.

Tap the question-mark button on the monitoring screen to open Help & Support.

App Behavior
Understand tire colors, alerts, mute and background monitoring.
Support & Help
Find pairing guidance and direct support contact details.
About
Check the app name, publisher and installed version.
Read the complete user manual →
Spartan RV TPMS Android Settings screen
Android Settings · app capture.

Compatibility

Use the phone and display
that suit your RV.

Core monitoring communicates directly with compatible Bluetooth Low Energy tire sensors. No account or cloud connection is required for tire monitoring.

Mobile devices
Android 9 or newer phones and tablets, plus compatible Apple devices.
RV profiles
Single-, dual-, or triple-axle trailers, with an optional spare.
Vehicle display
Android Auto is supported by the Android version, and Apple CarPlay is supported by the Apple version. Availability depends on the phone and compatible vehicle display.
Connection
Compatible powered TPMS sensors via Bluetooth Low Energy.

Spartan RV TPMS Privacy Policy

Effective and last updated: 2026-10-29
Publisher and privacy contact: SpartanLync Technologies, support@spartanlync.com
Android application: com.spartanlync.rvtpms · Current app version: 0.1.9

This policy explains how Spartan RV TPMS, published by SpartanLync Technologies, accesses, uses, stores and shares information. It covers the Android app and information you choose to send to its support contact.

At a glance: RV settings, paired sensor assignments and Trips History are stored on your phone. No app account or cloud trip-history service is required. The app does not obtain GPS coordinates or record travel routes. QR scanning uses Google ML Kit, which processes camera images on the device and separately sends technical diagnostics and usage metrics to Google as described below.

1. Information the app accesses and why

Information used by the Android app
InformationPurpose and handling
RV configuration and preferencesVehicle model, axle and spare layout, an asset or monitor name you enter, cold-pressure baselines, units, paired sensor identifiers, setup progress, consent choices and alert preferences are saved locally to configure monitoring and restore your setup.
Bluetooth sensor dataNearby sensor identifiers, received pressure and temperature, battery or voltage information, alert and availability states, reception times and signal strength when available are used to discover and pair compatible sensors, display tire status and generate alerts.
Trips HistoryMonitor names, trip/session start and end times, tire positions, sensor identifiers, received readings, battery information, alerts and signal information are recorded locally for history, offline charts and optional CSV export. Trip times describe monitoring sessions; they are not GPS routes. Illustrative sample records use separate storage from real monitoring history.
Camera images and scanned QR contentWhen you choose Scan asset QR and grant camera permission, camera frames are processed on the device to read a setup code. The scanning flow does not save photographs or record video. A decoded setup is shown for review before you confirm replacement of your configuration.
Technical SDK informationGoogle ML Kit processes technical device, app, identifier, usage and performance information for diagnostics and operation of its scanning technology. These SDK communications are separate from locally stored tire records; see section 3.
Information you send to supportIf you email us, we receive your email address, any name in your message, its contents and attachments, and information you choose to provide such as app version, phone model, sensor identifiers, screenshots, logs or exported records. This is used to answer your request, investigate the issue you report and maintain necessary support records. You do not need to send unrelated personal information.

The app does not require a personal profile, login, payment information, contacts, SMS messages or a GPS travel history. We do not sell app user data or use tire history for advertising. The app does not contain an advertising network or use an advertising identifier for personalized advertising.

2. Permissions and background operation

The app presents its data notice before requesting the permissions needed for live monitoring. Android also lets you control permissions in system settings.

  • Bluetooth / Nearby Devices: on Android 12 and newer, discovery and connection permissions allow the app to find compatible tire sensors and receive their broadcasts.
  • Location on older Android versions: Android 9–11 associate Bluetooth discovery with Location permission and the system Location setting. Android 10–11 may also require Background Location permission for continued discovery when the app is not in use. Spartan RV TPMS uses these permissions for Bluetooth tire-sensor reception, including background monitoring, rather than obtaining coordinates or building a location or route history.
  • Camera: optional, requested for QR scanning. Denying camera access prevents camera scanning but does not prevent normal tire monitoring or creating a sharing QR. Closing scanning or moving the app to the background releases the camera preview. Microphone permission is not requested.
  • Notifications, sound and vibration: used for monitoring status and tire alerts, subject to your choices and Android settings. Notification permission is optional on Android versions that request it.
  • Foreground service and battery operation: a foreground service, ongoing notification and wake lock support sensor monitoring with the screen off or the app in the background. The app offers a battery-settings choice because Android battery restrictions can interrupt reception. These functions do not give the app access to GPS routes.
  • Network access: supports SDK communications and user-selected support or website links. There is no app-operated server to which tire history is automatically uploaded.

Revoking permissions, stopping the app or restricting background activity can interrupt live readings and alerts. Camera permission controls camera access; it is not a separate opt-out from Google ML Kit's technical diagnostic processing.

3. Google ML Kit and technical diagnostics

QR camera scanning uses Google ML Kit barcode scanning. According to Google, camera images and the decoded input/output are processed on the device and are not sent to Google's servers by ML Kit. This is distinct from SDK technical information.

Google's ML Kit disclosure describes collection of device manufacturer/model, operating-system version/build and supported processing hardware; app package and version; per-installation identifiers and, for Google Play services-backed features, diagnostic device identifiers; feature/version/configuration information, input/output size, initialization and other usage events, errors and performance measurements such as processing latency. The library can initialize independently of a successful scan. SDKs may contact Google to obtain models, fixes or compatibility information. These communications also involve the connection information needed to contact Google's servers.

Google uses the metrics to operate, diagnose, protect, maintain and improve ML Kit. Google states that the documented diagnostic data is encrypted in transit using HTTPS and is not transferred by ML Kit to third parties. Google's processing and retention are described in its Privacy Policy and data-retention information. See also ML Kit privacy information and ML Kit's Android data disclosure. The app does not use these metrics to build an advertising profile.

4. When information leaves your phone

  • CSV export: records are shared only when you choose an export and a destination through Android. A CSV can contain monitor names, trip times, sensor identifiers, tire positions, readings, battery information, alerts and reception details. The selected app, service and recipients handle the copies they receive.
  • QR setup sharing: a setup code contains the asset name you enter, vehicle model/layout, cold-pressure baselines, units and sensor identifiers. It excludes Trips History, live readings, consent and permission choices. Anyone who receives or photographs the code can read that setup. A CRC-32 checksum checks for corruption; it does not encrypt the content or authenticate the sender. Share codes only with intended recipients.
  • Android Auto: tire status, configured tire positions, units, readings and alerts are passed to a connected Android Auto host through Android's automotive interfaces so they can be displayed. The connected host and Google platform services operate under their own privacy practices, including Google's Privacy Policy.
  • Google SDK diagnostics: ML Kit's technical information is sent to Google as described in section 3, separately from user-initiated file sharing.
  • Email and external links: your chosen email provider and our email-delivery/storage providers process messages you send to support. A browser and the website's hosting/network providers receive normal connection information when you open a website. External services have their own privacy practices. Information you provide to support may also be disclosed where necessary to comply with a lawful obligation.

Permission to access Bluetooth or the camera is not permission to upload your tire records. Normal monitoring, saved history and charts work locally without an app account or a cloud-history subscription.

5. Storage and security

Settings, assignments and history are kept in the app's private Android storage, protected by Android's application sandbox and your device's security controls. Android cloud backup and device-transfer backup for app data are disabled in this build. Use a device screen lock and keep Android and the app updated. The app does not provide an additional password-protected or separately encrypted history vault.

Google's documented SDK diagnostic transmissions use HTTPS. The security of an exported CSV, shared QR image, email or recipient's copy depends on the destination and service you choose. Avoid sharing personal names or sensitive records with unintended recipients. No storage or transmission method can guarantee absolute security.

6. Retention

  • Settings and assignments remain until you change or reset them, clear the app's storage or uninstall it.
  • Trips History normally retains up to 100 trips per monitor, removing older eligible trips when the limit is exceeded. Trips with unresolved critical events are protected from automatic pruning, so records can exceed that limit and remain until you delete them. History is not automatically removed after a fixed number of days.
  • Temporary sharing files: CSV export and QR-image caches older than 24 hours are pruned when the next corresponding export/share operation runs. This is not a guaranteed deletion exactly 24 hours after creation. Android can also remove cache files. Copies saved or sent outside the app remain under their recipients' control.
  • Support messages and attachments are kept while needed to handle the request and maintain necessary support or legal records. You may request deletion using the privacy contact below; any information that must be retained for an unresolved request or legal obligation is limited to that purpose.
  • Google's SDK records are subject to Google's retention practices. Clearing this app does not erase diagnostic data already received by Google; consult Google's linked privacy information for its handling and available request options.

7. Your choices, access and deletion

No app account exists to close. You can inspect and change locally saved RV settings, view Trips History and export records yourself. Because we do not hold a cloud copy of your tire history, an email request cannot remotely retrieve or erase records held only on your phone.

  1. Delete one trip: open Settings → Trips History, open the trip, choose Delete and complete the confirmation swipe.
  2. Delete history: open Trips History, choose Clear History and complete its confirmation swipe.
  3. Reset configuration and history: use Factory Reset and complete the confirmation swipe. This clears the app's pairing, settings and history and its cached QR sharing images.
  4. Remove all app-local storage and caches: use Android Settings → Apps → Spartan RV TPMS → Storage → Clear storage/Clear data, or uninstall the app.
  5. Control permissions: use Android's app-permission settings to change camera, Bluetooth/Nearby Devices, Location or notification access. You can stop background monitoring using Android's app controls, with the reception and alert limitations described above.
  6. Remove external copies: separately delete exported files and email attachments from their destinations, or ask the recipient/provider to delete them. Resetting this app cannot remove those copies.

For access, correction or deletion of information sent to support, email support@spartanlync.com with the subject “Spartan RV TPMS privacy request”. Identify the correspondence concerned and the request you want handled. We may ask for information reasonably needed to verify the request. Do not send passwords or unrelated identity documents. Applicable legal retention obligations may limit deletion of particular support records.

8. Intended users

The app is intended for adult RV owners and operators, not for children. We do not ask children to create profiles or submit personal information. If you believe a child has sent personal information to support, contact us so that it can be reviewed and deleted where appropriate.

9. This website and other services

This policy describes the app and its support correspondence. Website hosting, content-delivery, email and other external services can process connection information such as IP addresses, browser details, request times and requested pages to deliver and protect their services. Website-level cookies, analytics and forms are separate from the app's local tire monitoring and depend on the published site's configuration and notices. Contact the website operator at the privacy address below for questions about those services. Opening this policy does not grant the app new phone permissions.

10. Contact and policy updates

SpartanLync Technologies
Privacy and support: support@spartanlync.com
Please identify Spartan RV TPMS in your message.

We will update this policy when the app's data handling changes and show the updated effective date here. This policy and the app's Google Play Data safety disclosures should describe the same current practices. Where a change requires a new in-app disclosure or consent, that must be provided before the changed access or processing takes place.

Help & support

We're here when you need us.

Include your phone model, operating-system version, app version and a short description of the issue.

Before driving

Reinflate tires to the manufacturer's recommended cold pressure and confirm that every expected sensor is reporting.

Open the user manual →

To remove local app records, use Trips History, Factory Reset or the phone's app-storage controls. The privacy policy explains deletion and external copies.