Privacy as a feature
RigSense is operated by Topo Intel LLC, a Texas limited liability company. This policy covers the RigSense app for iPhone, from Apple's App Store, and the RigSense app for Android, from Google Play. Both apps keep the promises on this page, and where they work differently, the page says so.
RV owners choose off-grid living because they value independence. An app that tracks, profiles, or monetizes your data betrays that trust. Our privacy posture isn't defensive compliance — it's an active commitment to the community we're building for.
Where iPhone and Android differ
Both apps sign in to the same RigSense account and use the same servers. Everything else on this page applies to both, unless this table or a note says otherwise.
| Topic | iPhone | Android |
|---|---|---|
| Payments | Apple, through the App Store | Google Play |
| Signing in with another account | Sign in with Apple or Sign in with Google, if you choose one | Sign in with Google, if you choose it |
| Push notification token | Issued by Apple's push notification service | Issued by Google's Firebase Cloud Messaging |
| Maps and search | Apple Maps draws the map and handles search and directions, so it gets the words you search for and the places being searched, routed or named | Google Maps draws the map and gets the areas you view. Google Places and Android's geocoder get the words you type in a search box. Your phone reaches them directly. If you pick the vector map style, OpenFreeMap gets the map areas you view |
| Route planning | HERE gets your route's stops and your rig's size only when Height-aware route warnings is on in Settings | HERE gets your route's stops and your rig's size every time you plan a route. If HERE can't answer, openrouteservice and then Valhalla get the same |
| What usage analytics count | App opens and how you use the Full-Screen Display. Each launch also gets its own random ID | The screens you open, searches, map layers you turn on, hardware you pair, stay estimates and trip tracking. A search also carries roughly where you searched, rounded to about 7 miles |
| Location while the app isn't on screen | Only while you record a GPS trace | While trip tracking runs, with a notification showing. It records your GPS trace and, if you share your position with a convoy, sends it. About every 15 minutes the app also checks for severe weather where your rig is, using the last location your phone already has, your camp's location, or the last place the app saw. It doesn't turn on GPS for this. The location goes to our server, or straight to the National Weather Service when you're not signed in. RigSense never asks for "Allow all the time" |
| Sharing a GPS trace | The last 2 miles before you stopped, with points rounded to about 350 feet | Approach Only, which works as it does on iPhone, or Full Trace: the whole route, with about a mile trimmed at each end and points rounded to about 35 feet |
| Sign-in tokens on your phone | Kept in the iOS Keychain and tied to that iPhone | Kept in an encrypted store whose key stays in the Android Keystore, and left out of backups and device transfers |
| Other Google services | Only Sign in with Google, if you choose it | Google Play services checks for app updates and shows the rating prompt. Google's barcode reader scans invite QR codes on your phone. A connection test contacts google.com without your account details or location |
What we collect — and don't
Data is split into four clear categories. Most sensor data never leaves your phone.
- Raw BLE sensor readings (Mopeka, SeeLevel, TPMS, Ruuvi, Epoch/SOK BMS, and Govee on Android)
- Shore power data (Power Watchdog — voltage, current, wiring status)
- Leveling data (your phone's motion sensors or a LevelMate sensor)
- Reading history for charts: raw readings, then 5-minute and hourly averages
- Peplink router readings, and your router login, which stays in your phone's secure storage
- Devices on your rig's own network (Starlink dish, Victron Cerbo GX, Peplink router) are read directly by your phone. RigSense reads the Starlink dish and the Cerbo GX over unencrypted local connections, and the Peplink router over HTTPS. This traffic stays on your rig's network and isn't sent to our servers. It carries rig readings such as signal strength, battery status and solar yield.
- Alert thresholds & evaluation results
- Calculator results
- GPS traces you don't share
- Cached map tiles
- Draft community contributions (before submit)
- Your account: email address, your name if Apple or Google shares it (on Android you can also set one in Settings), and a password (stored only as a hash) or an Apple or Google sign-in
- Rig profile, equipment, boondocking habits and pet profiles, and a photo of your rig if you add one
- Saved spots, stays, trip plans, checklists and maintenance items
- A short record of each finished stay: the place, your rig's type, the arrival and departure dates, how long you planned to stay, and which resource was running out first
- Your latest levels (fresh, grey and black water, battery, propane, fuel), so they follow you to another device
- Daily energy and propane use from a finished stay, added to per-spot monthly averages that carry no account link
- Reviews, photos, and signal, water, crowd, road and night-sky reports you submit (see community photos below)
- People you block and content you report
- GPS traces you choose to share. Deleting a trace on your phone doesn't remove a copy you shared. To have one removed, email support@rigsense.app or delete your account
- Convoy and group event membership: your display name, plus your rig length unless you switch off Share rig details when you join
- Your convoy position, only while you have location sharing on. It's sent about every 30 seconds and shown to the other members of that event
- A push notification token, so alerts can reach your phone
- Usage analytics, linked to your account (details in the table below). You can turn them off
- Crash reports, only if you choose to send them. When you're signed in, a report can be linked to your account
- Places you look up in Location Insight, rounded to about 10 km and stored with no account ID, with how each data source answered and how long it took
- Support requests you send us
- Victron VRM — only if you connect it. Our server uses your VRM access token to read your system's data
- Apple on iPhone, or Google Play on Android — payment processing
- Sign in with Apple (iPhone only) or Sign in with Google — authentication, only if you choose it
- Device IMEI / hardware serial numbers
- Contacts or microphone audio
- Camera images. The camera reads invite QR codes and runs the solar compass on your phone
- Photos from your library beyond the ones you explicitly upload
- Advertising identifiers (RigSense never asks for Apple's IDFA or Google's advertising ID)
- Cross-app tracking data
- Browsing history
- Biometric data (kept by iOS or Android, not the app)
- Convoy location history. Only your latest position is stored
| Data category | Lawful basis | Justification |
|---|---|---|
| Account (email, password hash) | Contract | Required to provide the service |
| Sign in with Google (optional) | Only if you choose Google sign-in; Google receives your profile and device data under its own policy | |
| Rig profile, saved spots, stay history, resource levels | Contract | Core service functionality |
| GPS location (active navigation) | Contract | Required for navigation and spot-finding |
| GPS location (while the app isn't on screen) | Used to record a GPS trace, which is off until you start one. On Android, trip tracking also sends your convoy position if you share it, and a severe weather check uses a location your phone already has (see iPhone and Android). Location needs your permission, and you can turn it off in your phone's settings | |
| BLE sensor data (on-device) Mopeka, SeeLevel, TPMS, Ruuvi, Epoch/SOK BMS, Power Watchdog, LevelMate, and Govee on Android |
N/A | Raw readings and their history are processed on your phone and stay there, including tire pressure, temperature, shore power voltage and leveling angles. Your latest tank, battery, propane and fuel levels sync to your account so they follow you to another device. |
| Victron VRM cloud data | You connect it by entering a VRM access token. Disconnect it any time from the Rig tab | |
| Community contributions | Sent only when you submit them. You can delete a photo you uploaded | |
| Convoy sharing | Off by default. Once you're an approved member of an event, RigSense asks you once whether to share your position with it. Stop at any time from the event's More tab, which deletes your stored position. | |
| Payment information | Contract | Processed by Apple on iPhone or Google Play on Android. RigSense never sees card data |
| Crash reports & analytics | Legitimate interest | Usage analytics count how you use the app. On iPhone that means when it opens and how you use the Full-Screen Display. On Android it means the screens you open, searches, map layers you turn on, hardware you pair, stay estimates and trip tracking. Both apps also count the steps toward RigSense Connected: which setup screens you reach, the first time you enter levels and the first time the countdown shows, Location Insight previews, and the locked features you tap. They note when the subscribe screen opens, from which feature and screen or which moment in the app, how it closes, and whether you start a trial, buy or restore, plus on iPhone whether you open the offer-code screen. A purchase event names the plan, never the price or your payment details. They also note when the app asks Apple or Google Play to show the rating prompt, and why it asked. Apple or Google Play decides whether the prompt appears. Each event carries your device model, your iOS or Android version, the app version, and a random ID made on your phone that doesn't change. iPhone events also carry a random ID for each launch. Events never include your exact location, sensor readings or contact details. An Android search event does carry roughly where you searched, rounded to about 7 miles. They're sent only while you're signed in, to RigSense's own server, which stores them with your account ID. To stop, turn off Share Usage Analytics in Settings → Privacy. Crash reports are off unless you choose: RigSense sends one only if you tap Send in Settings → Support → Diagnostics or turn on automatic sending there. We use both to see how the app is used and to fix problems. |
Photos you upload to community spots
RigSense lets you add photos to spots so other travelers can see what a place actually looks like. Here’s who can see them, and how to remove one if you change your mind.
Who can see your photo. A photo you add to a spot shows up in that spot’s gallery for other RigSense users. It isn’t posted to the open web — there’s no public link, it won’t turn up in a web search, and it can’t be opened without the RigSense app.
What that means for you. People using RigSense can see your photo when they look at that spot. People who aren’t can’t — there’s no public link to pass around, and you need the app and an account to open a community photo. Even a link the app uses to show a photo stops working after a while on its own.
How to delete a photo. Open the photo in the app, tap the … menu, and choose Delete Photo. The file is removed from RigSense storage immediately, the photo disappears from the spot for everyone, and any link to it stops working right away. The Delete action is only available to the photo’s author — nobody else can remove your photos through that path. (Reports of policy-violating content go through the Report flow, which routes to our moderation team.)
If you shared a photo and someone saved a copy to their own device before you deleted it, that copy is theirs — the same as with any photo-sharing app. We can remove the photo from RigSense; we can’t reach into other people’s devices.
Deletion log. When a photo is deleted, we keep a short audit record — who deleted it, which spot it was attached to, the storage path that was removed, the timestamp, and the reason (author self-service, moderator action, or admin purge). This record persists after the photo file and contribution row are gone. The image data itself is not retained. The log is read-restricted to our moderation team and the platform service role; it is never exposed to other users or to the public. The purpose is forensics: if a photo is reported by another user as harmful and the author deletes it before review, we still need to know it existed. The log row is itself deleted if the spot is deleted, or unlinked from a user account if the user invokes their right-to-erasure under GDPR.
What we recommend. Treat photos you add to community spots as shared with the RigSense community — other travelers browsing that spot will see them. Don’t upload anything you wouldn’t want a fellow traveler to see.
Reporting and moderation. Every uploaded photo carries a Report action. If you see something that violates our guidelines, report it. Reported photos are reviewed and removed if they break our rules. Reports are logged and the reporting user is never disclosed to the photo’s author.
Photos you don’t upload. RigSense never accesses your camera roll or photo library beyond the specific photos you choose to attach to a contribution. We don’t scan your library, we don’t auto-upload, and we don’t read EXIF metadata other than the orientation tag needed to display the photo correctly.
How we contact you
We send two kinds of email, and only two.
Service and account email. Account verification, receipts, and notices about problems affecting your account — for example, if a bug stopped your sign-up from completing, or a security issue affects your data. These are part of providing the service you asked for, so they sit under the Contract lawful basis in the table above, and they are not something you opt out of separately. Close your account and they stop.
Marketing email: we don't send any. No newsletters, no product announcements, no promotions. If that ever changes it will be opt-in, and we would ask first. A service email will never carry a promotion.
Mail goes through our transactional email provider, listed in the processors table below. We do not sell, rent, or share your address, and we do not use it to build audiences on any advertising platform.
Your rights
All GDPR individual rights are implemented via in-app controls — no need to email us for most requests. US users are protected under the same framework, which exceeds CCPA/CPRA requirements.
Children's privacy
RigSense is for adults and isn't directed at anyone under 18, on iPhone or Android. We don't knowingly collect data from children. If you believe a child has given us data, email support@rigsense.app and we'll delete it.
How long we keep data
Here's how long we keep each type of data, and what deletes it.
| Data type | Retained for | Deletion trigger |
|---|---|---|
| On-device reading history | Raw readings 12 hours · 5-minute averages 48 hours · hourly averages 30 days | Rolled up and deleted on your phone; never sent to us |
| Account data | Until you delete your account | Account deletion |
| Stay history | Until you delete your account | Account deletion, or deleting a stay |
| Your latest levels | Only the most recent, replaced with each update | Deleted with your account |
| Victron VRM token | Until you disconnect Victron VRM or delete your account | Disconnecting asks our server to delete it; account deletion deletes it |
| Community contributions | Kept to serve other travelers | You can delete a photo you uploaded. Account deletion deletes your photos, reviews and road reports, and keeps your other contributions without your account |
| Usage analytics | 90 days | A weekly automatic cleanup deletes events older than 90 days. Deleting your account removes your account ID from them |
| Crash reports you send | 90 days | A weekly automatic cleanup deletes reports older than 90 days |
| Places you look up | The place: 90 days. Each source's status and response time: kept | A daily cleanup deletes the place after 90 days |
| Push notification token | Until you delete your account | Turned off when you sign out, and deleted with your account |
| Database backups | Up to 30 days | Backup purge completes within 30 days |
| Convoy and group event membership | While you're a member | Deleted when you leave the event or delete your account |
| Convoy and group event positions | Only your latest position in each event, while you share. No trail is kept | Deleted when you stop sharing, leave the event, sign out or delete your account. Also deleted automatically about six hours after your phone last sent it, whether or not the event has ended |
How we protect it
Neither app includes advertising, behavioral-tracking or third-party analytics SDKs: no Facebook SDK, no Google Analytics, no Firebase Analytics. The iPhone app bundles one third-party SDK, Sign in with Google, used only to sign you in when you choose it. The Android app uses Google's own libraries for location, maps, place search, push notifications, payments, sign-in, app updates, the rating prompt and QR code scanning. Google may receive your profile, device and usage data through these under its own privacy policy.
Third-party data processors
These companies handle user data for us. We have no data processors for advertising, profiling or data enrichment, because we don't do any of those things.
Third-party data source APIs
To provide location intelligence features, RigSense calls the following public and commercial APIs on your behalf. Unless noted, each receives only GPS coordinates. No account data or personal information is sent to them. Search services also receive the words you search for, and NHTSA receives the vehicle you look up. Most requests go through our Cloudflare Worker. Some go straight from your phone to the source, for example National Weather Service alerts when you're not signed in, and a source reached that way also sees your IP address. Rows tagged iPhone or Android apply to that app only.
Account deletion pipeline
When you delete your account, RigSense waits 7 days before deleting it. To cancel, sign back in within those 7 days. After that, the pipeline is irreversible. The steps are the same on iPhone and Android. If you no longer have the app, ask us by email and the same pipeline runs.
Deleting your account doesn't cancel a RigSense Connected subscription. Apple or Google Play bills it, so cancel it there.
Contact us about privacy
If you have questions about this policy, want to exercise a data right not available in-app, or need to report a concern — reach out directly. We read every email.
support@rigsense.app · Typical response within 24–48 hours