PRIVACY
Privacy
notes.
A plain-language summary of what BackCountrySignal receives when you use the site.
Browsing
You can read this site without creating an account or providing your name, email address, or other profile information. The site uses Cloudflare to deliver pages and APIs. Cloudflare may process technical request information as part of operating and protecting the service.
Visitor performance measurements
Cloudflare Web Analytics is enabled to measure page loading, interaction responsiveness and layout stability. Its beacon reports page paths, performance values and technical browser/device information to Cloudflare. It does not use cookies, local storage or individual fingerprinting for these analytics. The current configuration excludes visitors from the European Union. Browser blocking and sampling can limit the results. Form entries, saved plans and measurement files are not intentionally sent as analytics events.
Cloudflare’s description of the performance data it collects
Saved mesh projects and offline packs
Named projects, build settings, terrain plans, progress checklists and unsent field drafts are saved in this browser. They are not uploaded by project saving or backup. Switching projects restores their saved tools and drafts. Clearing browser data can remove them. Download a private backup before changing devices.
Project JSON backups may include precise terrain coordinates and draft notes. Keep them private. Configuration backups exclude channel encryption keys. Printable field checklists omit precise terrain coordinates; your own notes can still contain information you entered. A downloaded field pack works as a local file without analytics or external scripts.
Correction buttons open an email draft in your chosen email application. You review and send it yourself; entering a correction does not submit it to our database.
Field reports
If you submit a field report, we receive the information you enter in the form, including the general area, observation date, radio or node details, antenna information, terrain or test conditions, result, notes, and any optional contact information you provide.
Reports are stored in the BackCountrySignal database for community review. New reports are pending until reviewed. Public reports may be displayed on the coverage page. Reports marked private are intended to remain available only to the network team and are not included in the public reports API.
Do not submit passwords, private messages, exact residential addresses, or other sensitive information. Use a general area rather than an exact home location.
Host-a-node interest
If you volunteer a potential host site, we receive the general area, site type, optional elevation, power and internet availability, access or maintenance notes, contact information, and any notes you provide. Host-interest submissions are private operational intake and are not exposed through a public API. Do not submit an exact residential address in the form; use a general area until the network team contacts you directly.
Abuse prevention
To limit automated report spam, submission endpoints use short-lived rate-limit records derived from a one-way hash of the client network address and time window. BackCountrySignal does not store the raw client IP address in the application database for this purpose. Cloudflare may separately process network and security data under its own terms.
Public map data
The public map processes publicly observable Meshtastic® MQTT map reports to build a network-observation dataset. It may store node names and IDs, device and radio metadata, approximate or reported positions, telemetry, neighbor information, waypoints, and other protocol metadata needed by the map. The map collector is configured not to store message text, and the public map does not provide a text-message viewer.
Position data can be approximate, stale, or intentionally unavailable depending on what a node publishes and the source packet. The collector also honors the packet-level “OK to MQTT” signal where available.
Public network data
The coverage and map features may display publicly observable or intentionally shared radio-network information. A node's public location or other network metadata may be approximate, stale, or omitted. We do not intentionally publish private node locations simply because they are technically discoverable.
Retention and review
Moderation revision history may retain original and edited report fields privately to document corrections. Contact details, submission tokens, private review notes and revision history are excluded from public JSON and CSV exports.
Field reports and curated network records may be retained while they are useful to the community. Live map observations are automatically purged on shorter operational windows, with node records kept for up to 30 days without being heard and historical telemetry generally retained for about 7 days. We may correct, de-publish, or remove information that is inaccurate, stale, sensitive, or submitted in error. Rate-limit records are designed to be short-lived and are periodically cleaned up.
Terrain planning and map tiles
Online terrain analysis sends the selected endpoint coordinates to our terrain API and the USGS elevation service. Viewing maps requests tiles from their providers, which can reveal the viewed area. Saved plans and drafts remain in this browser until downloaded or deliberately submitted. Clear browser storage to remove local plans; back up drafts first.
Learning and power measurements
Academy progress and your power readings are stored only in your browser. Measurement imports and exports are local files and are not uploaded. Clearing browser storage removes these records; export a backup first if needed.
Third-party services
The site links to external services, including official Meshtastic® documentation and Graham County resources. Those sites have their own privacy practices and are not controlled by BackCountrySignal.
Questions or removal requests
If you submitted information and want it corrected or removed, email contact@backcountrysignal.org. Requests involving a private report should identify enough of the submission for us to locate it without sending sensitive information again.
Opt-in community directory
Directory submissions require the representative’s explicit permission. Only approved name, state, public area, protocol, website, description and consent/review timestamps are published. Private review emails are excluded from the public API, cleared on rejection, and cleared once they are older than 30 days by a daily cleanup job. No precise node coordinates are collected by this form. A private removal token is returned once with your receipt; only its one-way hash is stored. Using it immediately withdraws the listing and clears the contact email and token hash. Request removal through the community contact page with the submission receipt ID.
Preset migration evidence
Preset reports enter a private review queue and never publish automatically. The form collects community, state, city or service area, reported settings, observation date, a public evidence link and notes. Do not submit personal contact information, keys or precise locations. Permission to review and publish the non-sensitive details is required. Raw reports are deleted after 90 days by the daily cleanup job. Editors publish separately reviewed findings and source links through the website release process. Keep the receipt ID for correction or removal requests.