Recce Privacy Policy

Effective date: 2026-05-20

Recce is a field map and team communications app for hunters and small teams. This policy describes the current iOS beta posture. It is not a substitute for final legal review before public release.

Summary

Recce is local-first. The current iOS beta does not require an account, does not use advertising SDKs, does not use analytics SDKs, and does not send your field data to a Recce or C-137 server.

Recce can store and process sensitive field information on your device, including location, map markers, routes, tracks, notes, imported files, offline map packs, radio/team settings, and chat history.

Data Stored On Your Device

Recce may store these items locally:

• Precise location used for the map dot, tracks, markers, navigation aids, and optional foreground team-location sharing.
• User-created content such as pins, routes, tracks, areas, notes, chat messages, quick messages, range-card style information, and imported/exported Recce packages.
• Offline map pack metadata and cached map tiles.
• Downloaded or imported map/layer records such as public-land, boundary, and parcel records where supported.
• Meshtastic radio information such as connected radio identity, node information, channel readback, and remembered radio UUID for reconnect.
• Field status and sensor readings while features are in use, such as battery, thermal status, compass heading, motion state, altitude trend, and barometer values where supported.

Data Shared By User Action

Recce can share selected field data when you use sharing or team features. Examples include:

• Messages, pins, packages, routes, and foreground location updates sent over a user-connected Meshtastic radio.
• Files or packages exported through iOS share/export flows.
• Team invite text or QR codes that contain private channel configuration. Treat these invites like passwords.

Normal Recce radio traffic is intended for private encrypted Recce team channels. The app blocks normal chat, pin, package, location, and ACK traffic until the connected radio reports a named encrypted Recce channel.

Permissions

Recce requests permissions only when needed for user-visible features:

• Location When In Use: map location, following/current-location, tracks, field status, and optional foreground team-location sharing.
• Bluetooth: Meshtastic radio scan/connect and radio data exchange.
• Camera: team invite QR scanning.
• Motion: Field Sensors view for movement, stability, altitude trend, pedometer, and barometer values where hardware supports them.

Recce does not use background location in the current iOS beta.

No Sale Or Advertising Tracking

Recce does not sell personal data. The current iOS beta does not use advertising tracking, advertising identifiers, or tracking domains.

Map And Layer Sources

Recce may display public, official, user-owned, or properly licensed map/layer data. Offline availability depends on each source's terms. Boundaries, parcels, public-land data, map layers, weather, and field information may be incomplete, delayed, or wrong. Always verify legal access and current rules with official sources.

Data Deletion

You can remove local Recce data by deleting content in the app where supported or by deleting Recce from the device. Deleting the app removes app-local Recce data from that device according to iOS behavior.

Changes

This policy will be updated before public release if Recce adds accounts, cloud sync, analytics, crash-reporting uploads, payments, subscriptions, public team discovery, background location, or any new data collection.

Contact

For beta support, use the TestFlight feedback channel or the published Recce support page once hosted.