FCC Compliance & Regulatory Guide
Platform-level overview of FCC compliance support across Safe Connections Act, HAC, Broadband Facts, and CPNI.
Overview
Reach operates a managed wireless platform built for U.S. regulatory requirements.
Compliance is supported through platform controls and operating workflows.
Brands can launch faster without building custom regulatory processes from scratch.
This overview focuses on four FCC-driven areas:
Safe Connections Act
Hearing Aid Compatibility (HAC)
Broadband Consumer Labels ("Broadband Facts")
Consumer privacy and CPNI protection
At a glance
Platform: Reach managed wireless platform
Coverage: FCC compliance support at the platform and operational level
Last updated: April 2026
Safe Connections Act
Regulatory background
The Safe Connections Act protects survivors of domestic violence, stalking, trafficking, and related crimes.
It gives eligible survivors a path to separate service from shared accounts.
Key FCC requirements
Wireless providers must:
Allow eligible survivors to separate a line from a shared or family account
Complete separation within two business days of a valid request
Accept remote requests
Avoid notifying the alleged abuser before separation
Protect hotline call and text privacy in consumer-facing logs
Process requests without charging separation fees
How Reach supports compliance
Line separation support
Reach supports line-level separation in account and lifecycle workflows.
An eligible line can move to a standalone account with service continuity.
Remote request handling
Support teams can process requests without in-person visits.
Privacy protection
Consumer-facing account views do not expose raw call or message logs.
This reduces the risk of exposing sensitive communications.
No platform-imposed fees
Reach does not add platform fees to the line separation process.
Brand responsibilities
Brands remain responsible for:
Publishing Safe Connections Act disclosures
Training support teams on intake and escalation
Communicating documentation requirements to consumers
Hearing Aid Compatibility (HAC)
Regulatory background
FCC HAC rules require wireless handsets sold in the U.S. to meet accessibility standards.
The goal is effective use with hearing aids and cochlear implants.
Key FCC requirements
Handset models offered for sale must be hearing-aid compatible
Devices must meet FCC-approved technical standards
Compatibility details must be disclosed to consumers
Annual compliance certifications may apply
How Reach supports compliance
Compliant device catalog
Reach curates a device catalog for U.S. launches using FCC-certified handset models.
Accessibility disclosure support
Device listings can include hearing aid compatibility details in product content.
Upstream certification alignment
Reach validates device compliance through OEM and carrier certifications before onboarding.
Brand responsibilities
Brands remain responsible for:
Displaying accessibility details on device pages
Completing FCC filings where the brand is the provider of record
Broadband Consumer Labels
Regulatory background
FCC Broadband Consumer Label rules require standardized plan disclosures.
These disclosures help consumers compare broadband offers more easily.
Key FCC requirements
Broadband labels must clearly show:
Monthly price and any introductory pricing
Data allowances and overage policies
Typical download and upload speeds
Network management practices
Links to privacy policies and customer support
Labels must appear at the point of sale, including online storefronts.
How Reach supports compliance
Structured plan metadata
Reach captures pricing, data limits, throttling rules, and other label inputs in the product catalog.
Flexible presentation
Labels can appear in Reach-hosted storefronts or through APIs in custom front ends.
This includes no-code builds such as Bubble.io.
Consistency across channels
Labels can be shown consistently across web, assisted sales, and digital purchase flows.
Brand responsibilities
Brands remain responsible for:
Publishing labels at the point of sale
Ensuring displayed data stays accurate
Updating labels when plans or pricing change
Consumer Privacy and CPNI Protection
Regulatory background
Section 222 of the Communications Act requires protection of CPNI.
This includes usage data, service details, and billing information.
Key FCC requirements
Providers must:
Protect customer data from unauthorized access
Limit data use to service delivery unless consent exists
Apply secure authentication and access controls
Maintain auditability and breach response processes
File annual compliance certifications where required
How Reach supports compliance
Centralized data control
Reach manages customer data centrally across the platform.
This reduces fragmentation and unauthorized access risk.
Role-based access controls
Sensitive information is restricted by role for agents, admins, and support tiers.
Secure integrations
Reach secures APIs and integrations with authentication keys and scoped permissions.
Audit and monitoring support
System activity and access events are logged for audits and investigations.
Brand responsibilities
Brands remain responsible for:
Publishing privacy policies
Completing FCC certifications where legally required
Training customer-facing teams on compliance obligations
SIM Fraud Protection, Account Lock, and Verification
Overview
Protecting customer accounts from fraud is a core platform priority.
Reach uses Account Lock, one-time verification codes, and identity checks to reduce the risk of unauthorized SIM swaps, port-out fraud, and account access.
These controls help protect high-risk actions without relying on static PINs.
What Account Lock does
Account Lock lets customers control when sensitive account actions can happen.
When an account is locked:
SIM swaps are blocked
Port-out requests are blocked
All lines on the account stay protected together
This helps ensure critical account changes happen only with explicit customer approval.
Locking and unlocking
Customers can lock or unlock the account through self-care.
Locking uses a simple on/off toggle
Unlocking requires a one-time verification code sent to the customer’s email
The code expires shortly after delivery
This creates a controlled window for sensitive actions.
One-time verification codes
For high-risk actions, Reach uses time-limited, single-use verification codes instead of reusable PINs.
How this helps
Codes expire automatically
Each code works one time only
Each action needs a new code
Incorrect code entry triggers a customer notification
This reduces fraud risk, even if someone attempts to impersonate the customer.
SIM swap protection
A SIM swap changes which SIM is linked to a mobile number.
Because this is a high-risk action, extra verification applies.
To complete a SIM swap:
The account must be unlocked
A verification code is sent to the customer’s email
The code must be confirmed before the swap proceeds
If the account is locked, the SIM swap cannot be completed.
Number port-out protection
Port-out requests move a number to another provider.
These requests require additional safeguards.
When a customer requests a port-out:
The account must be unlocked
A port-out PIN is sent to the customer’s email
The PIN stays valid for a limited time
If the account is locked at any point, the port-out request is blocked and must be restarted after unlocking.
Secure support access
When customers contact support, Reach protects account access through identity verification.
This may include:
A one-time verification code
Specific account details known only to the customer
If verification cannot be completed, support agents cannot access or modify the account.
Notifications and alerts
Reach keeps customers informed during sensitive actions.
Customers receive alerts when:
A verification code is sent
A code is entered incorrectly
Important account or SIM-related changes occur
These alerts help customers spot unauthorized activity quickly.
Why one-time codes are used instead of static PINs
Traditional PINs stay the same and can be reused, shared, or guessed over time.
One-time verification codes provide stronger protection because they:
Expire automatically
Are created only when needed
Cannot be reused by another party
This is especially important for actions such as SIM swaps and port-outs.
Summary of responsibilities
Safe Connections Act
Core support and workflow tooling
Disclosures and team training
Hearing Aid Compatibility
Device compliance gating
Consumer-facing accessibility disclosures
Broadband Consumer Labels
Plan data structure and label enablement
Publication and accuracy
Consumer Privacy and CPNI
Security controls and access management
Certifications, policies, and internal training
Conclusion
Reach helps brands meet FCC requirements through platform controls, standard workflows, and operational safeguards.
Reach provides the technical foundation.
Brands still own consumer-facing disclosures, policy publication, and regulatory filings where applicable.
Last updated