911E911HQ.comCompliance field desk

US privacy, cookie, and emergency-data notice

Compliance

A practical notice for readers, subscribers, and consulting contacts using E911HQ.com. It explains what data the site processes and where emergency-calling data should not be submitted.

Privacy notice

E911HQ.com is an editorial and consulting-resource site about US E911, dispatchable location, enterprise emergency calling, VoIP routing, wireless 911 location, and public-safety technology. We process personal data only where it is needed to operate the site, respond to inquiries, send requested updates, protect the service, and maintain basic business records.

The main personal data collected directly is information you choose to provide: newsletter email address, selected language, consent timestamp, verification status, unsubscribe status, and any information submitted through the consulting contact form. We may also process limited technical data such as IP-derived security signals, user-agent strings, server logs, CAPTCHA status, and anti-abuse metadata.

Newsletter and contact data

Newsletter subscriptions use consent and double opt-in where configured. Every email should include an unsubscribe mechanism. Consulting inquiries are processed so we can respond to the request and decide whether a business engagement makes sense.

Do not submit live emergency incident records, caller location payloads, PSAP recordings, protected health information, or confidential public-safety records through the public contact form. If a consulting engagement requires sensitive evidence, use a separate secure transfer process.

  • We do not sell newsletter subscriber lists.
  • We collect only the fields needed for site operation, email delivery, anti-abuse controls, and inquiry response.
  • We retain unsubscribe records so preferences can be honored.
  • We avoid processing real emergency-call location data through this public website.

Cookies, advertising, and analytics

Essential cookies may support language preference, session security, administration, CAPTCHA, and basic service operation. These are used to keep the site functional and protect forms from abuse.

Advertising and measurement tools may set or read additional cookies only where enabled. Depending on visitor location and browser settings, ad systems may use contextual or consent-based behavior. You can control cookies in your browser and through any consent controls presented on the site.

US privacy and records considerations

US privacy obligations vary by state, sector, customer relationship, and data type. This page is a general operational notice, not legal advice. If California, Colorado, Connecticut, Utah, Virginia, or other state privacy laws apply to a specific deployment, configure notices, contracts, retention schedules, and consumer-rights workflows with counsel.

Emergency-calling records can be sensitive because they may reveal location, workplace presence, incident timing, and security response details. Keep access limited, retention purposeful, and exports controlled.

Security and emergency-data boundary

E911HQ.com discusses emergency communications architecture, policy, standards, and operational readiness. It is not an emergency service, PSAP, emergency-routing provider, or official 911 authority. Do not use this website to request emergency help. In an emergency in the United States, call 911.

Because the site is a public information resource, it should not receive live caller data, real incident PIDF-LO documents, PSAP recordings, or confidential emergency operations records unless a separate written consulting agreement and secure transfer method are in place.

Policy references

These public references inform the site’s editorial and operational context.