Your data stays yours.

RigSense is operated by Topo Intel LLC, a Texas limited liability company. 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.

Data is split into four clear categories. Most sensor data never leaves your iPhone.

RigSense lets you upload photos to public spots so other users can see what a place actually looks like. We want to be precise about how those photos are stored and served, because the model has trade-offs that aren’t obvious from the upload screen.

How photos are stored. When you upload a photo, it goes to a Supabase Storage bucket called location-photos. The bucket is configured as public — meaning each photo is reachable at a stable, unique URL. This is the same model used by most photo-heavy apps (Instagram, Twitter, Reddit, Yelp). It keeps the app fast, lets photos render in spot detail views without a per-image authentication round-trip, and works with standard CDN caching.

What that means for you. Once you upload a photo, anyone with the URL can view it. The URL doesn’t require a RigSense account or a password. The URL also doesn’t expire 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 the URL starts returning 404 to anyone who tries it. 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 a photo URL was shared and the recipient downloaded the image to their device before you deleted it, that copy is theirs — same as any other photo-sharing platform. We can remove the file from our storage; 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 uploaded to community spots the way you’d treat a photo posted to a public Instagram account or shared in a public forum. Don’t upload anything you wouldn’t want a stranger 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.

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.

Every data type has a defined retention period. Nothing is kept indefinitely unless it's community content you chose to make public.

Security is built into every layer — from device storage to API communication to infrastructure. No third-party analytics SDKs that phone home. No Facebook SDK. No Google Analytics.

Every third party that touches user data has a signed Data Processing Agreement (DPA). We have no data processors for advertising, profiling, or data enrichment — because we don't do any of those things.

To provide location intelligence features, RigSense calls the following public and commercial APIs on your behalf. These APIs receive only your GPS coordinates — no account identifiers, email addresses, or personal data are ever transmitted. All calls are proxied through our Cloudflare Worker; your device never contacts these services directly.

When you delete your account, everything goes. A 7-day grace period lets you cancel if you change your mind. After that, the pipeline is irreversible.

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.