Plain language.

Who operates this website

A2C3 Interactive Public Outreach is operated by A2C3 Outreach LLC, a Florida limited liability company.

Information you choose to provide

The Feedback page stores your ratings and written responses. An email address or username is optional. The Contact page stores the name or organization you provide, your email address, the reason for contacting A2C3 Interactive Public Outreach, and your message.

Public programs and children's privacy

A2C3-hosted public programs do not require an account, participant name, email address, telephone number, home address, school name, age, or other directly identifying information to participate.

The Fire Safety Knowledge Challenge and Fire Extinguisher Safety Challenge send privacy-minimized activity events to A2C3 so outreach can be evaluated. Depending on the program and event, these may include the department or installation, campaign attribution, program and build version, event date and time, broad device category and orientation, difficulty, question or scenario, selected response or action, correct, incorrect, safe, or completed outcome, response or completion time, completed-round score and question total, pass outcome, replay or retry activity, supported accessibility-feature use, and technical delivery, loading, fallback, or error information.

Programs that use activity analytics create a random session identifier and may store a random browser identifier to estimate repeat activity without collecting a name or account. The browser identifier expires and is replaced; its lifetime can vary by program and build. It is not an advertising identifier, hardware serial number, fingerprint, or exact count of people.

A2C3 hashes the session and browser identifiers before storing them. Program activity is added to department-, campaign-, date-, program-, question-, topic-, difficulty-, scenario-, device-, and other applicable reporting totals. Short-lived hashed session and estimated-device rows support counting, replay measurement, and delivery-quality review. The reporting system does not store the raw identifier or build a named participant profile, and department dashboards do not show an individual participant's answer history.

Children should not submit the Contact or Feedback forms. A parent, guardian, educator, or authorized organization representative should contact A2C3 on their behalf.

Home Safety Survey information

The Home Safety Survey does not ask for a participant name, email address, telephone number, exact street address, account, or household identifier. It records coded question responses and privacy-minimized department, campaign, date, topic, completion, and assistance-link totals for aggregate reporting. A2C3 does not retain a named household record or an individual survey history.

When an authorized department evaluation configures an assistance link, the link opens that department's official website or contact form. A2C3 may record that the assistance link was opened, but it does not send survey answers or personal information to the department. Information entered on the department's website is governed by that department's own practices.

The survey may keep unfinished progress in this device’s browser for up to 30 days and completed results for up to seven days so you can return to them. This local copy is separate from A2C3’s combined reporting. Clearing the browser’s site data removes the local copy; it does not remove activity already included in reporting totals.

Technical website data

Website hosting and security services may process limited technical information needed to deliver and protect the site, such as a network address, browser or device information, requested pages, date and time, and security signals. This technical information is separate from program answers, actions, and scores. A2C3 does not use public programs to serve targeted advertising. Hosting and security logs may be processed by service providers independently of the aggregate program reporting described above.

Browser storage, analytics storage, and retention

A game device may temporarily store its random browser identifier and a queue of unsent analytics events so interrupted deliveries can be retried. Clearing the browser's site data removes this local identifier and queue.

On A2C3 systems, hashed session and estimated-device rows and random event-delivery receipts are removed by a scheduled retention process after 100 days. Short-lived one-way network-address hashes used for analytics rate limiting are removed after two days. Aggregate reporting totals are retained for three years by default to support program evaluation and trend reporting. A different period may apply when a written customer agreement, legal hold, or applicable public-records obligation requires it. System backups, provider logs, and security records may follow separate operational retention cycles. Aggregate program totals are not connected to a participant name or public participant account.

Current safeguards

A2C3 is in pre-launch development and evaluation. Current safeguards include no public participant accounts, restricted event fields, input validation, department-scoped one-way hashing of session and estimated-device identifiers, rate limiting, event-delivery deduplication, aggregate-first storage, scheduled retention, department-scoped campaign attribution, and access-controlled department reporting. Detail is suppressed below five observations; samples of five through nine receive only very limited aggregate reporting; samples of ten through twenty-four are marked limited; and standard aggregate reporting begins at twenty-five.

Continuing privacy review

A2C3 continues to review field validation, identifier rotation, access logging, provider safeguards, and reporting thresholds as programs evolve. New analytics fields and subscriber-visible breakdowns must be reviewed before they are added to a production reporting contract.

Department reporting access

Authorized adult department staff may use a private reporting dashboard. Staff authentication information is used only to control dashboard access. Staff accounts are separate from public game activity and cannot be used to identify a participant.

Authorized departments may review and export reporting for their own programs and campaigns through dashboards, PDF reports, scheduled report delivery, and CSV exports when those features are enabled. Reports may include completed-round scores, pass outcomes, difficulty, question, topic or scenario results, campaign attribution, broad device context, timing, and accessibility-feature usage in privacy-minimized aggregate form. A2C3 does not sell participant behavior or use it to create advertising profiles.

Spam and abuse prevention

The website creates a one-way, anonymized identifier from the network address used to submit a form. It is used only to limit repeated submissions and reduce spam.

How information is used

Information is used to review public-safety outreach, respond to messages, provide support, and improve A2C3 programs. Form notifications are delivered through Resend and sent privately to A2C3 Interactive Public Outreach.

What A2C3 does not do

A2C3 does not sell personal information and does not use game activity or website submissions for targeted advertising. The public programs do not collect participant names, participant contact information, participant accounts, school identifiers, age, precise location, microphone recordings, photographs, advertising IDs, permanent hardware identifiers, or cross-site browsing activity. A2C3 does not use browser fingerprinting to identify participants or track activity across departments. A2C3 does not directly collect or process payment information through the public-safety website.

Department-branded editions

A customized edition may be hosted or linked by a participating fire department. That department is responsible for reviewing its approved branding, local content, website placement, and any department-specific privacy notice. Reporting remains limited to disclosed activity fields and privacy-minimized reporting outputs. A future written agreement will not, by itself, override participant-facing privacy disclosures; a material change would require appropriate review and an updated notice before use.

Questions or deletion requests

To ask a privacy question or request deletion of information you submitted, use the Contact page.

Because public-program activity is not connected to a name or account and is converted into aggregate totals, A2C3 generally cannot identify or extract a particular person's game responses. Information submitted through Contact or Feedback can be reviewed or deleted when A2C3 can reasonably locate and verify the submission.

Contact and feedback retention

Contact and feedback submissions are normally retained while A2C3 reviews and responds to the request, and for up to 24 months afterward for support continuity, program improvement, and administrative records. A record may be retained longer when required by an agreement, legal obligation, dispute hold, or applicable public-records requirement. Information that is no longer reasonably needed is deleted or de-identified.

Unverified department-access requests are normally removed after 30 days. Verified requests that are not activated, and declined requests, are normally removed after 12 months. Approved or activated request records are normally removed after 24 months. A different period may apply when an agreement, legal hold, or applicable public-records obligation requires it.

Last updated September 23, 2026.