EFFECTIVE // SEPTEMBER 28, 2026
Readiness assessments
The Command Center stores a written preparedness focus, broad zero-to-four capability ratings, ten system scores, an overall score and a short action plan. Before an email account is verified, the record is linked only to a secure browser cookie on that device. If a completed baseline exists when an assessment application is submitted, that baseline may attach privately to the application.
Optional readiness accounts
You may take the assessment without creating an account. If you choose to save results, Supabase Auth verifies your email using a temporary six-digit code and maintains the secure sign-in session. The site then links your verified account identifier and email to current and previous readiness scores, priority actions and applications so they can be accessed from another device. The site does not create or store an account password.
Sign-in email and Field Brief consent
Brevo delivers required account-verification emails through the authenticated Appalachian Preparedness sending domain. Permission to receive the optional Appalachian Preparedness Field Brief is separate and unchecked by default. Creating an account or submitting an application does not automatically provide marketing consent. If you opt in, the site records the email, consent status, source and time. You can withdraw that preference from the account page and unsubscribe from future marketing messages.
Optional assessment reminders
Signed-in users may separately choose to receive no more than three service reminders for an unfinished assessment, scheduled approximately one hour, 24 hours and three days after the most recent saved progress. This permission is off by default and is independent of Field Brief marketing consent. Completing the assessment or using the reminder opt-out link cancels remaining messages. The system records reminder scheduling, delivery outcome and resume-link use so the recovery process can be measured and limited.
Application information
Household professional-service applications collect contact details and the additional facts needed to decide whether a Diagnostic Call is appropriate. These may include household composition and broad dependency considerations; state, property type and broad utility or infrastructure characteristics; desired preparedness capability and timeline; decision participants; desired level of AP involvement; separate professional-service and implementation budget ranges; written goals, concerns and qualification responses; and referral source. A completed Household Readiness Assessment is reused privately so applicants are not asked to repeat its 30 capability ratings, score, vulnerabilities or action plan. The site also creates an application reference and records submission and status-update times. Applications submitted while signed in are linked to that readiness account.
Business, media, partnership, vendor and other professional inquiries are routed separately from the household qualification process and do not receive household Diagnostic Call calendar access. The system may suggest an internal route using explainable rules based on stated need, complexity, desired involvement, assessment findings and financial fit. That suggestion is decision support only. AP reviews the facts and makes the final decision; a higher budget does not automatically produce a higher service recommendation.
Application status
Signed-in users can view broad workflow status for linked applications. The public status page separately requires the application reference and exact application email. A successful match returns only the reference, requested service, broad workflow status and relevant dates. It does not display contact details, property information, household information, budget, preparedness focus, baseline scores, goals or referral answers.
What not to submit
Do not submit inventories, account numbers, access codes, defensive plans, camera or alarm locations, precise equipment locations, medical records, detailed medical diagnoses, detailed financial-account information or exact vulnerabilities. The initial application asks only whether additional planning requirements exist. Written preparedness, property and budget answers should remain broad. A separate private process is established if an engagement is accepted.
Use of information
Readiness information supports the user's score, history and action plan. Application information is used to evaluate fit, determine the appropriate service, respond to the request, prevent abuse and plan a potential engagement. Information is not sold. Limited information is processed by service providers that host, secure or deliver the site and its verification emails.
Technical information
The hosting platform, authentication provider and security systems may process routine technical information such as request time, browser or device information, network information and error logs. Secure first-party cookies keep a device signed in, associate an unfinished device-only assessment and maintain an opaque funnel session. The funnel session may record the landing path, referring host and campaign parameters supplied in a link, such as platform, campaign, content and CTA identifiers. Funnel events may be associated server-side with that opaque session and, where available, a readiness profile, account or application identifier. Event metadata does not contain an email address, assessment answers, preparedness focus, readiness score or identified vulnerability. Appalachian Preparedness does not use an advertising tracker for this system and does not send sensitive assessment information to an analytics platform.
Retention and control
Readiness records remain available until deleted by the user or removed under a legitimate retention process. Application records may be retained while the request is reviewed, while an engagement or legitimate business need remains active, and as reasonably needed for security, records or legal obligations. Signing out removes the active account and readiness cookies from that device; it does not delete saved records. The Command Center provides a separate deletion control for saved readiness data.
Security limits
Reasonable safeguards, limited collection, email verification and private server-side storage reduce exposure, but no internet transmission or storage system can be guaranteed completely secure. Sensitive assessment details should be exchanged only through the private process established after acceptance.
Contact
Privacy questions and requests can be sent to AP@appalachianpreparedness.com. Include an application reference when relevant, but never include passwords, access information or sensitive preparedness details.