Privacy Policy

Account registration collects first name, last name, email address, and a password. Passwords are stored as one-way hashes, not readable plaintext. The service also stores assessment answers and results, mission checklist and Preparedness Point progress, session records, and controlled Emergency Planning learning-progress identifiers.

Operational and test logs may record request timing, errors, route information, and technical diagnostics. They should not intentionally contain completed emergency plans.

Watchman Command does not collect or store completed emergency-plan answers. Do not submit household-member details, home addresses, emergency contacts, meeting locations, evacuation destinations, medical information, utility shutoff locations, or completed printable worksheet answers.

Emergency Planning stores only controlled module or worksheet identifiers and learning-progress timestamps. Completed worksheets remain offline with the user.

The Go-Bag Builder saves checklist selections and user-created generic item labels in local storage. Welcome-video display preferences are also stored locally. This browser-local information is not sent to the application database by those tools. Clearing site data removes it from that browser.

Authentication uses cookies and signed session tokens to keep users signed in and protect account-specific routes. See the Cookie Policy for the current categories and browser-storage behavior.

Information is used to provide accounts, authenticate users, calculate and display assessment results, track mission progress and points, record educational progress, operate and secure the service, diagnose faults, and test the application.

Information may be retained while an account is active and as reasonably needed for operations, security, dispute resolution, and legal obligations. Retention periods require final owner and legal review. Administrative, technical, and organizational safeguards are used, but no system can promise absolute security.

Depending on location, users may have rights to request access, correction, deletion, restriction, objection, or portability. Identity may need to be verified before a request is fulfilled. support@avigilantlife.com

The service is not directed to children under 13, and the operator does not knowingly seek their personal information. Applicable age requirements and parental-consent obligations require final legal review for launch jurisdictions.

This policy may change as the service or legal requirements change. Material updates should be identified by a revised “Last updated” date. support@avigilantlife.com