Privacy Policy

Last Updated: March 6, 2026

1. Introduction

SnagMP is a suite of highway tools designed to help users locate state route mileposts, elevation profiles, cross-sections, and field data. The suite currently includes the SnagMP Extension (a Chrome browser extension) and SnagMP Field (a mobile Progressive Web App). We respect your privacy and are committed to protecting it. This policy explains what information we collect and how it is used across all SnagMP tools.

2. SnagMP Extension — Data Collection and Usage

Location Data

The Extension reads geographic coordinates (latitude and longitude) from the Google Maps page you are viewing, or from coordinates you input manually via search.

• Purpose: This data is used solely to query public government APIs to retrieve milepost information and elevation data.
• Storage: Coordinates are not stored or logged on any servers owned by the developer. They are sent directly to public APIs and processed in real-time.

Local Storage (On Your Device)

The Extension stores the following data locally on your device using Chrome's built-in storage APIs:

• Search History: Your last 10 searches (route and milepost) for quick access. Synced across your Chrome browsers if signed in.
• Preferences: Last searched route/milepost and display settings. Synced across browsers.
• Cache Data: Highway geometry, milepost reference data, and elevation data are cached locally (IndexedDB) to reduce API calls and improve performance. This data expires automatically after 7–30 days.
• Feature Data: User-created feature points and lines are stored locally in IndexedDB.
• API Usage Counter: A simple counter tracking elevation API calls to display usage notifications. Stored locally only.

This data never leaves your device except for Chrome's built-in sync feature for preferences and history (if you're signed into Chrome).

License Verification

If you activate a license key or verify a state employee email address, the extension contacts snagmp.com to verify license status. This request includes only your license key and email address. No location data, browsing history, or other personal information is transmitted during license verification.

Search Telemetry

When you perform a milepost search, the extension sends a minimal, anonymous event to snagmp.com containing the state abbreviation, route number, milepost value, extension version, and timestamp. No personally identifiable information, coordinates, or browsing data is included. This data is used solely to understand which routes and states are most used, to prioritize development.

3. SnagMP Field — Data Collection and Usage

Device Location (GPS)

SnagMP Field uses your device's GPS to determine your real-time position on the state highway system.

• Purpose: GPS coordinates are used locally on your device to calculate the nearest state route, milepost, direction of travel, and offset distance.
• Storage: Your GPS coordinates are processed entirely on your device and are never transmitted to any server. All milepost calculations are performed locally against downloaded route data.

Local Storage (On Your Device)

SnagMP Field stores the following data locally on your device:

• Route Data: State highway geometry and milepost reference data downloaded during initial setup (~15–25 MB per state). Stored locally for offline use.
• Supplemental Datasets: Optional datasets (e.g., Fish Passage Culverts) downloaded by the user. Stored locally for offline use.
• App Settings: User preferences and display settings. Stored locally only.

All Field app data stays on your device. SnagMP Field is designed for offline use and does not transmit location data, usage data, or any personal information to external servers during normal operation.

4. Third-Party Services

The SnagMP Extension sends coordinates directly to the following public government APIs to retrieve milepost and elevation data:

• US Census Bureau — Determines which US state the map view is in
• WSDOT (Washington State Department of Transportation) — Highway geometry, milepost reference data, roadway characteristics, and LRS data
• Caltrans (California Department of Transportation) — Highway geometry, postmile reference data, and roadway characteristics
• ODOT (Oregon Department of Transportation) — Highway geometry and milepoint reference data
• TxDOT (Texas Department of Transportation) — Highway geometry and milepoint reference data
• UDOT (Utah Department of Transportation) — Highway geometry and milepoint reference data
• USGS 3DEP (National Map) — High-resolution LiDAR elevation data
• OpenTopoData — Supplementary elevation data

These services receive only geographic coordinates. No personal information, browsing history, or identifying data is transmitted.

SnagMP Field does not contact third-party APIs during normal use. Route data is downloaded once and used offline.

5. Data We Do NOT Collect

• Personal information (name, email, address) — except as voluntarily provided for license activation
• Browsing history or activity outside of SnagMP usage
• Photo files or image content
• Device location via the Extension (coordinates are read from the Google Maps page, not from device GPS)
• GPS tracks or location history from the Field app

6. Data Security

We do not sell, trade, or otherwise transfer your information to outside parties. All data processing happens on your local device or through direct, encrypted HTTPS requests to the public government APIs listed above.

7. Your Control

You can clear all locally stored data at any time by:

• Removing the Extension from Chrome
• Clearing browser data in Chrome settings
• Removing the SnagMP Field app from your home screen and clearing site data in your mobile browser settings

8. Changes to This Policy

We may update this Privacy Policy as SnagMP evolves. Changes will be posted on this page with an updated "Last Updated" date.

9. Contact Us

If you have questions about this Privacy Policy, please contact us at: info@snagmp.com