Legal
Privacy Policy
How Fireguy.NET collects, uses, stores, and protects information when you use Fireguy|Repeater Planner.
Last updated: August 24, 2026
Overview
This Privacy Policy describes how Fireguy.NET (“we,” “our,” or “us”) collects, uses, stores, shares, and protects information in connection with Fireguy|Repeater Planner (the “Service”). By using the Service, you agree to the practices described here and to our Terms of Service. If you do not agree, do not use the Service.
We designed the Service for incident radio planning and field ops. That means accounts can hold operational and personal information about you and people you add (roster members, phone contacts, emergency contacts, and similar). We treat that data as confidential and use it to operate the Service—not to sell it.
1. Information we collect
1.1 Information you provide
Account data. When you register, we collect your email address, first and last name, and a hashed password. We use this to create and secure your account and to send transactional messages (email verification, confirmation of email changes, security-related notices, and optional analysis-complete emails).
Profile and preferences. You may add preferred name, call sign, phone number, home agency/unit, display units, travel defaults, ICS qualifications, and up to two emergency contacts. Team profile fields may be visible to incident owners/editors under the access rules described in the product.
Incident and operational content. Data you and authorized collaborators create—sites, RF analyses and saved results, inventory, batteries, frequencies and channel plans, roster and demob information, shifts, phone lists, radio logs, line orders, waybills, diagrams, evaluations, vendor/resource notes, uploads (for example channel-plan imports), and similar—is stored to provide the Service.
Integrations you configure. If you enable ZoneMap publication, GroupMe, Slack, Discord, Courier/SMS-email alerting, OCR, or other integrations, we process the configuration and payloads needed for those features (for example access codes, bot identifiers, webhook targets, and alert content).
Communications. If you contact us (for example at repeater@fireguy.net), we may retain your email and correspondence to respond and improve the Service.
1.2 Information collected automatically
Log and usage data. Servers may log IP address, user agent, request timestamps, URLs, approximate error diagnostics, and similar technical data to operate, secure, rate-limit, and debug the Service.
Cookies and similar technologies. We use session cookies and related mechanisms required for authentication, CSRF protection, and basic site function. These are essential. Where configured, we also use Google Tag Manager to load analytics (for example Google Analytics) on Service pages. Those tools may set their own cookies and collect pages visited, device/browser type, and approximate location (for example country) to help us understand usage. Google’s processing is governed by Google’s Privacy Policy. You can limit some analytics via Google’s opt-out tools or browser settings. Clearing gtm_id in server configuration disables Tag Manager for this site.
Timezone hint. The client may send a timezone offset header so timestamps display in your local wall clock; this is used for usability, not precise geolocation.
1.3 What we do not do
We do not sell your personal information. We do not use Your Content for third-party advertising. We do not require payment card data for ordinary free use of the Service.
2. How we use information
We use information to:
- Provide, maintain, secure, and improve the Service;
- Authenticate users, enforce permissions, and prevent abuse (including rate limits);
- Send transactional email related to your account or long-running analyses you started;
- Operate features you enable (exports, shares, ZoneMap publish, IWI/notification channels);
- Comply with law, respond to lawful requests, and protect rights, safety, and security;
- Analyze aggregated or de-identified usage to improve reliability and features.
Legal bases (where required, for example under GDPR/UK GDPR) include: performance of a contract (providing the Service you request); legitimate interests (security, product improvement, fraud prevention) balanced against your rights; consent (where we rely on it, for example certain cookies/analytics where required); and legal obligation.
3. Sharing and disclosure
We do not sell personal information. We may share information only as follows:
- Collaborators you authorize. Incident members see data according to roles and privacy settings (for example viewers vs editors; phone public/private flags; team profile visibility for owners/editors).
- Integrations you enable. Publishing a channel plan to ZoneMap, linking GroupMe/Slack/Discord, or triggering notification channels sends the data those features require to those providers under their terms.
- Service providers. Hosting, email delivery, analytics (when enabled), OCR, and similar processors act on our behalf under obligations to protect data and use it only as instructed.
- Legal and safety. We may disclose information if required by law, court order, or government request, or when we believe in good faith disclosure is necessary to protect rights, safety, investigate abuse, or address security issues.
- Business transfers. In a merger, acquisition, or asset sale, information may transfer subject to equivalent privacy commitments.
4. Storage, security, and retention
Data is stored on servers we or our hosting providers operate. We use industry-standard measures including HTTPS in transit and hashed passwords. No internet transmission or storage method is perfectly secure; you use the Service at your own risk regarding residual security risk.
We retain account and incident data while your account remains active and as needed to provide the Service. Server logs and backups may persist for a limited period for security and continuity before purge. Email verification and similar tokens expire after a short period and are then removed or invalidated.
If you request account deletion, we will delete or anonymize personal account data we control, subject to: (a) data that must remain in shared incidents owned by others until those owners remove it; (b) legal retention needs; and (c) residual copies in encrypted backups until they rotate out. Contact us as described below to make a request.
5. Your rights and choices
Depending on your location, you may have rights to access, correct, delete, port, restrict, or object to certain processing of personal data, and to withdraw consent where processing is consent-based.
Access and correction. You can review and update much of your profile in Account settings. For other requests, email repeater@fireguy.net.
Deletion. Request account deletion via the same email. Incident owners should export or remove operational records they still need before deletion. Closing your account may not erase content inside incidents you do not own.
Cookies / analytics. Essential cookies are required for login. You may block or delete cookies in your browser; doing so can break sign-in. Analytics opt-out tools are linked in Section 1.2.
California (CCPA/CPRA) and similar U.S. state laws. We do not sell personal information or share it for cross-context behavioral advertising as those terms are commonly defined. California residents may request to know, delete, or correct personal information, and to non-discrimination for exercising rights. We will not discriminate against you for exercising privacy rights. Authorized agents may submit requests as permitted by law; we may require verification.
EEA/UK. You may lodge a complaint with your local supervisory authority. You may also contact us first so we can try to resolve the issue.
We will respond to verifiable requests within the timeframes required by applicable law.
6. International transfers
The Service is operated from the United States. If you access it from elsewhere, your information may be processed in the U.S. or other countries where we or our providers operate, which may have different data-protection laws. Where required, we use appropriate safeguards (such as standard contractual clauses or equivalent mechanisms).
7. Children
The Service is intended for adults (18+) engaged in professional or authorized operational planning. It is not directed to children under 13, and we do not knowingly collect personal information from children. If you believe we have collected information from a child, contact us and we will take steps to delete it.
8. Sensitive and operational information
You may choose to store information that your agency treats as sensitive (personnel contacts, frequencies, locations, logs). You are responsible for following your organization’s policies on what may be stored in a third-party tool, who may be invited, and when data must be purged after an incident. We process such content only to provide the Service as configured by you and authorized users.
9. Do Not Track
Some browsers send “Do Not Track” signals. There is no consistent industry standard for responding to them; the Service does not currently alter behavior solely based on DNT signals. You can control cookies and analytics as described above.
10. Changes to this Policy
We may update this Privacy Policy from time to time. We will post the updated policy on this page and revise the “Last updated” date. Material changes may be communicated via the Service or email when appropriate. Continued use after the effective date constitutes acceptance of the updated policy. If you do not agree, stop using the Service and request account closure.
11. Contact
Privacy questions, requests, or complaints: repeater@fireguy.net.
Operator: Fireguy.NET · Service: Fireguy|Repeater Planner · https://repeater.fireguy.net
Related: Terms of Service · parent network Fireguy.NET