Active and Recent Nets
Monitor emergency communications and net activity in real-time.
No nets found
Get started by creating your first emergency net.
Create New Emergency Net
Set up a new communication net for emergency operations.
After creating your net
You'll receive magic links for Net Control (NC) and Backup Net Control (BNC) authentication. Save these links securely as they provide management access to your net.
Authenticating...
Processing your magic link token and establishing secure session.
Help & Authentication Guide
Learn how to access and manage emergency communication nets.
Quick Start
Get up and running with emergency net logging in minutes.
For Net Control Operators
Create a new emergency net using the form
Save the magic links for NC and BNC access
Click your role-specific link to authenticate
Manage check-ins and net operations
Security: Magic links work as long as the net is open. Don't share them with unauthorized personnel. Magic links expire after 6 hours, and active sessions expire after 24 hours.
For General Users
View all active and recent nets
Monitor check-ins in real-time
No authentication required
Access from any device
Role Badges & Access Levels
Net Control
Full management access
Backup Net Control
Full management access
Net Types
When creating a net, you can categorize it by selecting one of the following types:
Casual gatherings for operators to chat and connect. A great way to meet new people on the air.
Nets focused on technical discussions, equipment, and operating techniques.
For passing formal messages (radiograms). Practices skills used by the National Traffic System (NTS).
For handling critical communications during actual emergencies like natural disasters or public safety incidents. Activation is often rapid, and participation may be restricted to trained operators from groups like ARES or RACES.
Official nets for Amateur Radio Emergency Service (ARES) or Radio Amateur Civil Emergency Service (RACES) groups, often in support of served agencies.
Nets operating for a limited time to commemorate a special occasion, such as a historical anniversary, a festival, or a contest.
Privacy Policy
How we handle your information on ARES Net Logging
Our Commitment to Your Privacy
ARES Net Logging is operated by KJ5DJC as a free service to the amateur radio community. This privacy policy explains how we handle information collected through this service.
Simply put: We do not sell, rent, trade, or otherwise monetize your data in any way. This service is run purely to support amateur radio emergency communications.
Information We Collect
Public Information
- Net Information: Net names, frequencies, bands, locations, start times, and public notes
- Check-in Data: Amateur radio call signs and optional comments from operators who check into nets
- Operator Information: Publicly available data from HamDB.org including operator names, locations, license classes, and grid squares
Authentication & Session Data
- Magic Link Tokens: Temporary authentication tokens for Net Control and Backup Net Control operators (expire after 6 hours)
- Session Cookies: HTTP-only cookies to maintain authenticated sessions (expire after 24 hours)
- IP Addresses: Stored in audit logs for security and troubleshooting purposes
Audit Logs
We maintain immutable audit logs of actions performed on the system (creating nets, adding check-ins, etc.) including timestamps and IP addresses for security and accountability purposes.
How We Use Your Information
- To display active and historical emergency communication nets
- To facilitate real-time check-in logging during emergency operations
- To generate ADIF, CSV, and ICS-309 reports for emergency management purposes
- To provide authentication for Net Control operators
- To maintain security and prevent abuse of the service
- To improve and troubleshoot the application
Data Sharing
We do not sell, rent, or trade your information to third parties. Period.
Net information and check-ins are publicly viewable by design, as this service is intended for emergency communications coordination. This is similar to how amateur radio transmissions are public by nature.
Operator information (names, locations, license classes) is sourced from publicly available FCC/HamDB.org data and is already public information.
Third-Party Services
- HamDB.org: We query HamDB.org to automatically populate operator information based on call signs. This data is cached for 24 hours to reduce API calls.
- Hosting Provider: The application is hosted on infrastructure that may have its own privacy policies and data handling procedures.
Data Security
We implement reasonable security measures to protect your information:
- Authentication uses temporary magic links instead of passwords
- Session tokens are stored in HTTP-only cookies to prevent XSS attacks
- All API inputs are validated and sanitized to prevent injection attacks
- Rate limiting is in place to prevent abuse
- Audit logs track all data modifications for accountability
Your Rights
Since this service deals primarily with publicly available amateur radio information and is designed for emergency communications, most data is intentionally public.
However, if you have concerns about your information appearing in this system, please contact us at the GitHub repository linked in the footer.
Data Retention
- Active Sessions: Authentication sessions expire after 24 hours of inactivity
- Magic Links: Magic link tokens expire after 6 hours
- Net Data: Net records and check-ins are retained indefinitely for historical and emergency management purposes
- Audit Logs: Maintained for security and compliance purposes
- Deleted Check-ins: Soft-deleted (marked as deleted but retained in the database)
Children's Privacy
This service is designed for licensed amateur radio operators. In the United States, amateur radio licenses are available to individuals of all ages. We do not knowingly collect information from individuals under 13 without parental consent. If you believe we have collected such information, please contact us.
Changes to This Policy
We may update this privacy policy from time to time. Any changes will be posted on this page. Continued use of the service after changes constitutes acceptance of the updated policy.
Contact
For questions or concerns about this privacy policy or how we handle your information, please open an issue on our GitHub repository.
Last Updated: November 1, 2025
Loading...
Please wait