Robocall Mitigation & Caller Authentication

Defined Terms

Application within Robocall Mitigation & Caller Authentication. “ARCAMUSA,” “we,” “us,” and “our” mean Arcamusa, Inc., operator of ARCAMUSA Wholesale. “Customer” means the business entity authorized to use the Wholesale Services. “Traffic” means calls, signaling, metadata and related activity submitted to or received from the Wholesale Services. “Caller ID” or “CLI” means calling-party identification information. “Downstream Customer” and “End User” mean persons or entities using services through Customer.

Application within Robocall Mitigation & Caller Authentication. “Agreement” includes applicable online terms and policies together with any signed MSA, Order Form or Rate Sheet. “CDR” means a call detail record used for operational, billing, reconciliation, security or compliance purposes. Defined terms apply consistently across the Legal & Trust Center unless a document expressly provides a narrower meaning.

Regulatory Identity & RMD

ARCAMUSA Wholesale is operated by Arcamusa, Inc., FCC FRN 0038769774, Form 499 Filer ID 839219, and RMD Filing Number RMD0041523 as a listed Voice Service Provider. These identifiers are not government endorsements.

Reasonable Mitigation Framework

ARCAMUSA prohibits illegal robocalls, deceptive CLI and traceback evasion; performs customer and Traffic risk review; may request records; and may restrict or suspend Traffic presenting credible abuse or regulatory risk.

Customer & Reseller Responsibility

Customers must know relevant downstream parties, maintain accurate Traffic and CLI authority records, flow down use restrictions, investigate complaints and promptly stop abusive sources.

STIR/SHAKEN Status

ARCAMUSA is proceeding with caller-ID authentication readiness. ARCAMUSA does not make a public representation regarding production caller-authentication status beyond its current regulatory filings and documented service implementation. Authentication treatment may vary according to provider role, number authority, implementation and call path.

Attestation Principles

No customer is promised A-attestation. Treatment depends on provider role, verified identity, telephone-number authority, implementation and standards. No page states that all calls are signed, authenticated or verified.

Traceback & Evidence

Customers must preserve and provide responsive CDR, origination and downstream identity records for legitimate traceback. Public cooperation language describes Customer responsibilities and does not create a response-time guarantee beyond applicable law or an executed Agreement.

Abuse, Remediation & Cooperation

Credible reports may result in preservation, investigation, targeted restriction, remediation, suspension, termination and lawful cooperation with the FCC, law enforcement or the designated traceback consortium.

Regulatory Framework

ARCAMUSA maintains public regulatory disclosures and evaluates obligations applicable to its current role and services without treating a filing as government endorsement.

Mitigation Program

Risk-based mitigation may include business vetting, traffic review, complaint analysis, CLI controls, investigation, restriction and cooperation with traceback.

Know Your Business

Customer identity, ownership, authority, service purpose, downstream structure and regulatory posture may be reviewed before and during service.

Traffic Monitoring

Operational review may consider volume shifts, call duration, destination patterns, complaints, source changes and other signals without publishing exploitable thresholds.

Caller ID Authority

Customers must substantiate authority for caller identification and correct inaccurate, misleading or unauthorized use.

STIR/SHAKEN Principles

Caller authentication is applied according to applicable rules, verified relationships and technical facts. No public statement promises signing or a specific attestation for any call.

Traceback

Customers and resellers must preserve routing and source information and cooperate accurately through legitimate traceback channels.

Downstream Responsibility

A reseller remains accountable for downstream traffic and must be able to identify, restrict and remediate each source.

Investigation and Remediation

Credible concerns may trigger evidence requests, controlled testing, traffic restrictions and corrective-action requirements.

Suspension

ARCAMUSA may suspend affected traffic or service when necessary to protect networks, users, regulatory standing or lawful investigations.

Regulator Cooperation

Information may be preserved or provided in response to valid legal and regulatory processes subject to applicable law and safeguards.

Regulator Cooperation: review and closure. The matter is not closed until the responsible party has preserve responsive routing and customer records, verify the requesting channel, provide accurate scoped information and prevent investigated traffic from re-entering through another path. Closure may be documented through request identifiers, authority verification, timestamps, source and destination records, preservation actions, responses and corrective measures. ARCAMUSA may reopen review if later traffic or reliable information materially contradicts the basis for closure.

Contract Hierarchy & Related Documents

This policy governs robocall mitigation, caller authentication and traceback cooperation for submitted voice traffic. The Caller ID Policy separately establishes number authority, Acceptable Use prohibits unlawful campaigns, and Traffic Integrity addresses anomalous patterns requiring containment.

An authentication result does not establish consent, lawful calling purpose or exemption from mitigation. Customer obligations under this policy apply alongside the Wholesale and Reseller Terms and survive route changes while an inquiry, traceback or remediation request remains open.