Acceptable Use Policy

Effective Date: March 1, 2026

This Acceptable Use Policy (the “AUP“) is incorporated by reference into the Inteveo EcoLink Master Terms and Conditions (the “Terms“) and applies to Customer’s use of the Services. Capitalized terms not defined here have the meanings given in the Terms. This AUP supplements, and does not replace, the acceptable-use obligations in Section 5 of the Terms; where this AUP and Section 5 overlap, both apply.

1. GENERAL USE OBLIGATIONS

Customer shall, and shall ensure that each of its users shall:

• use the Services only for lawful business purposes and in accordance with the Documentation;
• comply with all applicable federal, state, local, and international laws and regulations, including telecommunications, privacy, marketing, and recording-consent laws;
• obtain and maintain all consents, notices, registrations, and authorizations its use of the Services requires;
• safeguard account credentials, promptly deprovision departed users, and promptly report any suspected compromise;
• register and keep current accurate physical location information for each device or endpoint used for 911/E911; and
• cooperate with Company in investigating suspected misuse, fraud, or security incidents.

Customer is responsible for all activity occurring under its accounts, whether or not authorized.

2. PROHIBITED USES

Customer shall not, and shall not permit any user or third party to, use the Services to:

2.1 Unlawful activity. Violate any law or regulation, infringe or misappropriate any third-party right, or facilitate any unlawful act.

2.2 Unlawful or abusive communications. Send unsolicited, deceptive, or misleading calls or messages, including any communication that violates the Telephone Consumer Protection Act, the Telemarketing Sales Rule, CAN-SPAM, state telemarketing or do-not-call laws, CTIA messaging principles, or A2P 10DLC/TCR registration, consent, and opt-out requirements.

2.3 Fraud and network abuse. Engage in caller-ID spoofing or falsification, neighbor spoofing, traffic pumping or access stimulation, autodialing in violation of law, international revenue share fraud, toll fraud, subscriber fraud, or any scheme intended to evade billing, regulatory, or carrier obligations.

2.4 Harmful or unlawful content. Transmit, store, or make available material that is defamatory, obscene, harassing, threatening, abusive, hateful, or that infringes intellectual property rights; or that constitutes child sexual abuse material, which Company reports to the appropriate authorities without notice to Customer.

2.5 Security violations. Distribute malware, ransomware, or other malicious code; launch denial-of-service or amplification attacks; probe, scan, or test the vulnerability of any network or system without authorization; attempt to gain unauthorized access to any account, system, or data; intercept communications not intended for Customer; or defeat or circumvent authentication, rate limiting, or other security controls.

2.6 Service integrity. Place abnormal, excessive, or automated load on the Services; exceed published rate limits; use the Services in a manner that degrades service for other customers; or interfere with the operation of Company’s network or that of any Third-Party Provider.

2.7 Unauthorized resale or sharing. Resell, sublicense, rent, or otherwise provide the Services to any third party, or use the Services on behalf of any person other than Customer and its authorized users, except under a written reseller or partner agreement with Company.

2.8 Reverse engineering and competitive use. Reverse engineer, decompile, or disassemble the Services; use the Services to build or benchmark a competing product or service; or access the Services to monitor availability, performance, or functionality for a competitor.

2.9 Restricted data. Upload, transmit, or store protected health information, cardholder data subject to PCI DSS, export-controlled technical data, or biometric identifiers subject to state biometric privacy statutes, in each case without a separate signed addendum, as set out in Section 6.3 of the Terms.

2.10 Reputational or regulatory risk. Use the Services in any manner that could reasonably subject Company to liability, regulatory action, carrier sanction, or loss of a Third-Party Provider relationship.

3. MESSAGING, VOICE, AND COMMUNICATIONS COMPLIANCE

3.1 Consent. Customer is solely responsible for obtaining and documenting all consents required before placing calls or sending messages, and for honoring opt-out and revocation requests promptly and across all channels.

3.2 Registration. Customer is responsible for A2P 10DLC brand and campaign registration, for the accuracy of registration data, and for all associated carrier and registry fees and pass-through charges.

3.3 Recording. Customer is solely responsible for determining whether recording is permitted, for obtaining the consent of all parties where required, and for configuring recording announcements and periodic tone. Several states require the consent of every party to a recorded telephone conversation. See Section 6.1 and Annex 1 of the Terms.

3.4 Content standards. Customer shall not send messages relating to categories prohibited by carriers or the CTIA, including certain high-risk financial offers, illegal substances, and gambling, except where expressly permitted and properly registered.

3.5 Traffic quality. Company may impose or adjust throughput limits, require registration, or throttle traffic where message or call patterns indicate spam, fraud, or a risk of carrier filtering or blocking.

4. SECURITY OBLIGATIONS

Customer shall:

• use strong, unique credentials and enable multi-factor authentication where available;
• limit administrative privileges to personnel who require them, and review access periodically;
• keep endpoints, handsets, and client software current with vendor-supplied updates;
• secure its own network, firewall, and internet connection, including any SIP or session border configuration;
• monitor for abnormal call volume, unusual international destinations, and after-hours activity, which are common indicators of toll fraud; and
• notify Company promptly at [email protected] of any suspected compromise, unauthorized access, or fraudulent use.

Company may impose international dialing restrictions, credit limits, or usage thresholds to mitigate fraud risk. Customer remains responsible for all usage originating from its accounts, including fraudulent and unauthorized usage.

5. ENFORCEMENT

5.1 Investigation. Company may investigate suspected violations and may access account data and usage records to the extent necessary to do so.

5.2 Suspension and termination. Company may suspend the Services immediately, with or without notice, for any violation of this AUP, as provided in Section 5.7 of the Terms. Continued or material violation is a default under Section 5.6 and may result in termination, in which case the Early Termination Charge in Section 3.7 of the Terms applies.

5.3 Cooperation with authorities. Company may report unlawful activity to law enforcement and regulatory authorities and cooperate with lawful investigations.

5.4 No obligation to monitor. Company has no obligation to monitor Customer’s use of the Services. Any monitoring Company performs is for its own protection and creates no duty to Customer to detect or prevent misuse, fraud, or unauthorized usage.

5.5 Costs. Customer is responsible for all charges, fines, penalties, carrier assessments, and remediation costs arising from its violation of this AUP, and shall indemnify Company for claims arising from such violations under Section 12.1 of the Terms.

6. UPDATES

Company may update this AUP from time to time by publishing the updated version. Material changes that reduce Customer’s rights take effect thirty (30) days after notice, as provided in Section 2.5 of the Terms. Customer’s termination right in respect of a material AUP change is set out in Section 5.1 of the Terms.

Inteveo EcoLink, LLC — Acceptable Use Policy, Version 3.26

• About WordPressAbout WordPress
• Get Involved
• WordPress.org
• Documentation
• Learn WordPress
• Support
• Feedback
• Log In
• Search