Roadnetic Privacy Policy

1. Who we are

SOVASH LLC (“SOVASH,” “we,” “us,” or “our”) develops and publishes Roadnetic: Mileage Tracker. Contact: info@sovash.com.

2. Precise location and background location

Roadnetic accesses precise location data, including while the app is in the background or not actively in use, when automatic mileage tracking is enabled. This background access allows Roadnetic to detect and record drives without requiring the app to remain open.

Location is used to record trip routes, calculate mileage and distance, determine trip start and end coordinates, display route maps, resolve readable From/To locations, and create mileage records. If required location permissions or background access are disabled, automatic tracking or route recording may not work.

3. Physical activity / Activity Recognition

Roadnetic uses Google Play services Activity Recognition signals, such as in-vehicle, walking, still, on-foot, running, bicycle, or unknown classifications and confidence information, to help start automatic-drive evaluation and reject non-driving movement. Roadnetic does not directly read raw accelerometer samples for this feature.

Activity-recognition events and related tracking-health/diagnostic events may be stored locally on the device to support reliability and troubleshooting. Diagnostic events are periodically pruned.

4. Trip and route records

Roadnetic may store trip dates and times, distance, duration, classification, review status, start/end coordinates, accepted and rejected GPS fixes, accuracy, speed, bearing, route points, vehicle, client, business purpose, notes, mileage rate/value information, and readable origin/destination text.

These records are primarily stored locally in Roadnetic's private app storage on your device and remain until you delete them, use Delete Local Data, clear app storage, or uninstall the app, subject to the limitations described below.

5. Maps, geocoding, and third-party location processing

Roadnetic does not automatically upload your trip history to a SOVASH cloud account or synchronization service. However, some location information is processed by platform services required to provide Roadnetic features.

• Google Play services Location supplies location fixes used by Roadnetic.
• Android/OEM Geocoder may receive the first and last accepted trip coordinates when Roadnetic needs to convert coordinates into readable From/To place or address text. On some devices this may use a Google-backed network service.
• Google Maps SDK for Android is used to display basemap content and Roadnetic supplies recorded route coordinates, route bounds, and Start/End marker coordinates for map presentation.

Roadnetic does not send client details, expenses, notes, receipts, or business-purpose text to Google Maps through its map-rendering code. Third-party providers may process and retain information according to their own terms and privacy practices, and Roadnetic's local deletion controls cannot delete provider-side records or caches.

6. Human-readable From/To locations

For completed automatic trips, Roadnetic first attempts to use a locally saved Place. If a readable endpoint is unavailable, Roadnetic may submit the first or last accepted coordinate to the device's geocoding provider to obtain a readable location. Resolved From/To text is stored locally with the trip and may appear in reports. Manual-trip From/To text is entered by the user.

7. Expenses, clients, vehicles, purpose, and notes

Roadnetic may store expense amount, currency, date/time, category, merchant, purpose, notes, receipt reference, and linked trip, client, or vehicle. Client records may include name, company, phone, email, address, and notes. Vehicle records may include display name, make, model, year, plate, and related settings. These records are stored locally unless you choose to export or share them.

8. Receipt photos and files

At your direction, Roadnetic can attach receipts using an external camera app, Android Photo Picker, or document picker. Imported receipt copies are stored in Roadnetic's private app files. Temporary camera-capture files may be stored in app cache. Roadnetic does not request direct camera permission for this workflow; it uses the external camera through a secure temporary content URI.

Receipt files may be viewed using an external viewer you choose. Roadnetic reports can indicate that a receipt is attached, but current PDF/XLSX/CSV reports do not embed the receipt binary itself.

9. Reports and exports

Roadnetic generates supported CSV, PDF, and Excel/XLSX reports locally. Depending on the report, exported data may include trips, dates/times, mileage, From/To text, classifications, purpose, notes, mileage values, expenses, merchant information, and related client/vehicle details. Raw GPS route-point rows and receipt binaries are not included in current production exports.

When you use Android's share sheet or save an exported file outside Roadnetic, the selected destination receives the data you chose to share. Copies outside Roadnetic are not controlled by Roadnetic's deletion tools.

10. Notifications

Roadnetic uses Android notifications for active mileage tracking, trip-completion notices, trip-classification actions, tracking status, and other enabled app functions. Roadnetic does not use a third-party push-notification provider for these notifications.

11. Google Play Billing and Roadnetic Pro

Google Play processes Roadnetic Pro subscription purchases. Roadnetic accesses Google Play product/offer information and purchase/subscription status to display localized offers, reconcile entitlement, and acknowledge purchases. Roadnetic stores a limited local entitlement cache and verification timestamp. SOVASH does not receive your full payment-card number from Google Play.

Deleting Roadnetic data or uninstalling the app does not cancel a Google Play subscription. Subscription records are maintained by Google Play and can be restored/reconciled later.

12. Analytics, advertising, and SOVASH cloud services

Roadnetic currently contains no advertising SDK, no advertising identifier integration, no Firebase Analytics or equivalent analytics SDK, and no third-party crash-reporting SDK such as Crashlytics, Sentry, or Bugsnag.

Roadnetic currently has no SOVASH authentication backend, cloud trip store, cloud synchronization API, or direct Roadnetic-authored network client that automatically uploads your trips, route data, expenses, receipts, clients, vehicles, or profile to SOVASH servers.

13. SOVASH website and support

Roadnetic can open SOVASH support, privacy, terms, security, and data-request pages in your external browser, and can open your email app for support. Fixed website links do not include your Roadnetic trip records. If you send an email or attach information, the content you choose to send is processed by your email provider and received by SOVASH for support purposes.

14. Local storage and device backup

Roadnetic's primary records are stored locally using Android application storage, including Room/SQLite and DataStore. Roadnetic's Android cloud-backup and device-transfer backup are disabled for its app data. Roadnetic does not add application-layer encryption to Room/DataStore; data is protected by Android's application sandbox and platform storage protections.

15. Retention

Trips, route points, metadata, expenses, clients, vehicles, preferences, mileage rates, and owned receipt files generally have no automatic time-based expiry. Local diagnostic events are periodically pruned. Cached export files may be replaced or cleared by Android.

16. Deletion

Roadnetic provides local deletion controls. Depending on the record type, you may delete trips, expenses, clients, and receipts, archive vehicles, or use Delete Local Data to remove Roadnetic's local Room data, DataStore preferences, owned receipt/camera files, and cached exports. Delete Local Data requires that no trip is actively recording and disables automatic detection as part of the reset.

Deleting local Roadnetic data does not delete copies already exported/shared, original source photos/documents outside Roadnetic, emails already sent, Google Play purchase history, or information already processed/retained by Google or other platform providers. See Roadnetic Data Requests & Deletion.

17. Uninstalling Roadnetic

Normal uninstall removes Roadnetic-owned private app data from the device, including its local database, preferences, private receipts, and app cache. Uninstalling does not cancel Roadnetic Pro, delete files previously exported/shared elsewhere, delete original photos/documents, or establish deletion of information previously processed by third-party platform services.

18. Sharing and sale of personal information

SOVASH does not sell Roadnetic personal information. Data may be processed by platform/service providers as described above, or transmitted to a destination you explicitly select when exporting, sharing, viewing a receipt, opening a website, or contacting support.

19. Security

We use reasonable safeguards appropriate to Roadnetic's local-first architecture. No method of electronic storage or transmission can be guaranteed completely secure.

20. Children's privacy

Roadnetic is not directed to children under 13, and SOVASH does not knowingly collect personal information from children under 13 through Roadnetic.

21. Changes to this policy

We may update this policy when Roadnetic's features, service providers, or legal requirements change. The effective/updated date on this page will be revised when appropriate.

22. Contact

SOVASH LLC
30 N Gould St, Ste R
Sheridan, WY 82801
United States
Email: info@sovash.com
Phone: +1 (307) 998-2030