Wireless E911 Location Accuracy Requirements
In this document, the Federal Communications Commission (the FCC or Commission) proposes rules to strengthen wireless 911 location accuracy rules and to put more actionable location information in the hands of Public Safety Answering Points (PSAPs) and first responders.
What this rule actually says
The FCC is proposing that wireless carriers must pinpoint 911 callers' locations more accurately and send that location data to emergency dispatch centers (PSAPs) in a more useful format. Right now, when someone calls 911 from a cell phone, dispatchers often get a rough location; the FCC wants precision within 50 meters indoors and 30 meters outdoors, plus richer data that helps first responders actually find people faster.
Who it applies to
- If you build a mobile app or chatbot: This applies only if the app itself handles emergency calling or emergency location services. A hiring chatbot or medical scribe running on a phone doesn't trigger this.
- If you operate a wireless carrier or MVNO: This is primarily for carriers. If you're a founder using standard telecom infrastructure (Twilio, etc.), you're not directly regulated.
- If you collect location data from users for non-emergency purposes: This rule does NOT affect you. It only covers 911-specific location data.
- Jurisdictions: This is a US-only FCC rule. International founders can ignore it unless deploying in the US.
- User data scope: The rule is about emergency dispatch data, not your product's user data. Your privacy policies don't need to change unless you're directly integrating with 911 systems.
What founders need to do
- Check if you touch 911 at all (1-2 hours): Read your app's code and terms. If you don't handle emergency calls or expose location to dispatch, stop here.
- If you do integrate with 911 services: Contact your telecom provider (e.g., Twilio's emergency services team) to confirm they're compliant (1-2 days). Don't build this yourself—let carriers handle it.
- Monitor the rule's final status (ongoing, low effort): This is still "proposed" as of May 2025. Set a calendar reminder to check the FCC website in 6 months. Final rules may have a 1-2 year phase-in.
- Update 911 disclosures if needed (1 day): If your app does route emergency calls, ensure your privacy policy and in-app warnings clearly state that location data goes to emergency services. This rule doesn't require that, but it's good practice.
- Plan budget for carrier updates (planning only, now): If your product depends on 911, budget for potential carrier-side changes down the line, though costs should fall on telecom companies, not you.
Bottom line
Monitor, don't panic: Unless you're building emergency calling features, this doesn't touch you; if you are, your carrier handles the heavy lifting, and you just need to watch for final rule details over the next year.