Privacy Policy

1. Overview

Red Grid MGRS is built with a privacy-first, offline-first architecture. The app does not run Red Grid user accounts or embed analytics, advertising networks, or tracking systems. Your location data, waypoints, report worksheets, incident records, saved areas, session history and configuration stay on your device unless you deliberately export, share, or transmit them. Website measurement is described separately under Third-Party Services.

2. App Data and Support Messages

Red Grid MGRS does not send us a feed of your GPS positions, saved waypoints, photos, contacts or usage activity. There is no Red Grid account system or Red Grid cloud sync. Saved information remains in local app storage unless you use an export or sharing feature.

If you contact support or submit the website form, we receive the contact details and message you choose to send. Map providers, app stores and your device platform handle data for their respective services, as described below.

3. Peer-to-Peer and Mesh Data

Red Grid MGRS can optionally interact with Meshtastic radios over Bluetooth to place your teammates on your offline map and exchange short tactical messages. Red Grid MGRS does not provide direct phone-to-phone Bluetooth or peer-to-peer Wi-Fi team transport; its radio features require compatible Meshtastic hardware. These workflows are initiated by the user and do not use Red Grid servers.

Peer-to-peer or mesh data:

• Travels directly between nearby devices or radios
• Is not sent to Red Grid Tactical servers
• May be retained locally by a receiving device or radio
• Uses the relevant platform, Bluetooth, Wi-Fi, or radio transport for that feature

Red Grid MGRS team payloads can use AES-256-GCM with a shared team key. The active key is stored locally so the team can persist across app restarts; leaving the team removes that app key. Encryption does not hide radio metadata such as sender identifiers or packet timing. Radio channel settings and optional position sharing also affect what is transmitted.

4. Local Storage

The apps store the following data locally on your device:

• App settings and preferences
• Saved waypoints
• Saved areas of operation and offline tile status
• Team key and team preferences, where configured
• Active route progress and a limited local history of manually confirmed route points
• Cached map tiles and compatible locally imported MBTiles data
• Report worksheet values and their location/time references
• Incident details and resources, ICS 214 activity entries and correction history, and unfinished incident/activity drafts
• Local previous-record and recovery copies used to recover damaged report records
• Purchase entitlement status, receipts and store transaction identifiers used for purchase restoration or verified revocation handling
• Local purchase-handling counters and review-prompt eligibility/history, which are not uploaded as app usage analytics

From version 4.1.2, report worksheets, incident workspaces and unfinished incident/activity drafts are saved in a local database and survive app restarts after saving completes. Wait for the saved confirmation before closing. Saved incident records remain readable and exportable if Pro expires. Earlier app versions may keep report drafts only for the current session.

Calculator and tool input drafts stay in process-session memory until cleared or the app process ends. Saved settings and files produced by those tools are separate. Use the available controls to clear report worksheets or delete archived incidents, saved lists, map data or a team key.

Generated PDF/JSON files may remain in the app cache for system sharing; caches are not a secure-erasure guarantee. Uninstalling normally removes app-local data, but exported files, device backups and copies held by other apps or recipients must be managed separately. Protect devices and exported records according to your organization's requirements; local storage alone is not a regulatory certification.

5. Diagnostics

Red Grid MGRS does not embed third-party analytics, advertising or crash-reporting SDKs. Apple, Google or the operating system may provide store reports and technical diagnostics according to their own policies and your device settings.

6. In-App Purchases

Subscription and purchase transactions are processed by the Apple App Store or Google Play Store. We do not receive your payment-card or bank details. The app receives store entitlement and transaction information, and Apple or Google may provide sales, subscription and other developer reports under their policies. Those reports do not give us a live feed of your in-app activity. Subscription management is handled through your store account settings.

7. Third-Party Services

Online maps use platform map services and map tile providers. Those providers may receive your IP address, requested map area or tile coordinates, and standard request information. The app may retain map tiles locally. Current versions disable public-provider bulk downloads and support compatible local MBTiles imports instead. Available local map tiles can be displayed without requesting those tiles from a provider; verify the area is covered before going offline.

Red Grid MGRS does not embed third-party advertising, analytics, or social media SDKs.

The website is hosted on Cloudflare. Cloudflare processes standard web request information to deliver and protect the site, and domain-level Cloudflare Web Analytics provides aggregate traffic estimates such as visits, page views, referrers, browsers, and countries. This website measurement is separate from Red Grid MGRS and does not add analytics to the app.

App Store and Google Play links include a shared campaign label identifying the website section that referred you. Apple and Google use these labels in their store reports. The labels contain no personal identifier or location, and we do not add an analytics SDK to the app.

The contact form on our website (redgridtactical.com) is delivered through Formspree, which forwards only the name, email address, and message you choose to submit so that we can reply. This applies to the website contact form only, not to the apps. You can also reach us directly at [email protected].

8. Children's Privacy

The App is not directed at children under 13. We do not knowingly collect any information from children.

9. Changes to This Policy

We may update this Privacy Policy from time to time. Changes will be published here with an updated date. We will provide any notice or request consent required by applicable law.

10. Contact

If you have questions about this Privacy Policy, contact us at [email protected].