Phone Service Terms

#1. Scope and relationship to other terms

These Phone Service Terms apply when Customer uses Elios functionality for telephone numbers, voice calls, messaging, recordings, or related communications capabilities (“Phone Services”). They supplement the Terms of Service between Elios Superintelligence, Inc. (“Elios”) and Customer. Capitalized terms not defined here have the meanings given in the Terms of Service.

Customer may incorporate Phone Services into Customer’s applications and make those applications available to Customer’s users, subject to the Agreement. Customer remains responsible for its applications, its users’ permitted access, and the communications Customer or its users initiate. A separate agreement is required if Customer intends to resell standalone telecommunications services in a way that requires additional carrier approval or regulatory arrangements.

These terms control a conflict with the general Terms of Service specifically concerning Phone Services. An accepted Order may expressly vary these terms, subject to applicable law and mandatory carrier conditions. The Data Processing Addendum controls conflicts concerning processing covered by that addendum. These terms do not transfer to Customer any legal obligation imposed directly on Elios.

#2. Availability and permitted countries

Phone Services are available only for the countries, number types, destinations, capabilities, and use cases identified in the applicable documentation or Order. Number availability does not by itself establish that every calling or messaging use is permitted in that country. Some capabilities may require identity checks, local addresses, business verification, registration, or carrier approval before activation.

Customer must provide accurate registration and verification information, keep it current, and cooperate with reasonable requests needed to supply the Phone Services lawfully. Customer must not use another person’s identity, misdescribe its business, or register a campaign on behalf of an undisclosed sender. If Customer registers a downstream customer, Customer must have that customer’s authority and submit that customer’s accurate information.

Elios may decline an unsupported country, number type, destination, or use case. Where a carrier or regulatory requirement changes, Elios may make the corresponding service change and will give notice when reasonably possible. Customer may stop the affected use in accordance with the Agreement. Required changes do not retroactively authorize charges that were not disclosed under the Agreement.

A Phone is one United States phone number with voice calls, SMS and MMS messages, and contacts. Elios currently provides United States numbers only. Elios supplies numbers, calls, and messages through its carrier, BulkVS, and carries call signaling and live audio through Elios’s own call servers in the United States and the European Union.

#3. Customer applications, agents, models, and voices

Customer controls the applications, agent instructions, recipients, purposes, and content of communications it initiates. Customer must configure appropriate permissions, spending limits where available, access controls, and human oversight for its use case. Customer must test its application before enabling production traffic and provide a way to stop unwanted or malfunctioning communications.

Customer is responsible for models, speech services, voices, and other third-party services it connects to Phone Services. Customer must obtain the licenses and permissions needed to use those services and any person’s voice or likeness. A technical connection does not grant permission to impersonate a person, use a protected voice, or make a communication lawful.

Customer must not mislead recipients about the identity of the caller, sender, organization, or person represented. Customer must provide disclosures about automated or AI-generated interactions where applicable law requires them and must not conceal automation for a deceptive purpose. Customer must not present an AI-generated statement as a person’s own statement without that person’s authorization.

Elios supplies communications infrastructure. Elios’s provision of a number, API, recording feature, or communications connection does not constitute approval of Customer’s script, model, campaign, or legal compliance.

#4. Calling and messaging permissions

Customer must have all permissions required for each communication before initiating it. Applicable requirements can depend on the caller and recipient’s locations, the destination number, the technology used, the communication’s purpose, and whether it includes advertising or marketing. Customer must not assume that an inbound inquiry, a purchased contact list, a prior transaction, or permission for one purpose authorizes unrelated or recurring communications.

Where required, Customer must obtain and document prior express consent, prior express written consent, or another legally sufficient permission. Customer must comply with applicable do-not-call rules, suppression lists, permitted calling hours, frequency limits, sender identification requirements, and restrictions on artificial or prerecorded voice calls. AI-generated voices must be assessed under applicable artificial or prerecorded voice rules, rather than treated as automatically equivalent to live human speech.

Customer must maintain records sufficient to demonstrate the permissions and legal basis for its traffic for the period required by applicable law and relevant disclosed carrier requirements. Records should identify the recipient, the permission obtained, the applicable sender and purpose, when and how permission was obtained, and any withdrawal. Customer must provide relevant evidence reasonably requested by Elios to investigate a complaint or satisfy a lawful carrier or regulatory request, using a secure method and limiting disclosure to what is necessary.

Customer must ensure its downstream customers and users follow these requirements. Customer must not route prohibited traffic through another account, number, campaign, or provider to avoid a restriction.

#5. Opt-outs and unwanted communications

Customer must provide accessible opt-out methods required by applicable law and the carrier requirements disclosed for its traffic. Customer must recognize and honor valid withdrawal requests within the applicable deadline and must stop the communications to which the withdrawal applies. Customer must not obstruct an opt-out, require unnecessary personal information to complete it, or treat a withdrawal as consent for a new campaign.

For messaging, Customer must support the applicable standard opt-out keywords and any additional legally required method. Customer must use opt-out instructions appropriate for the channel, language, and campaign. An allowed confirmation of an opt-out must not contain additional marketing. Customer must obtain any new permission required before resuming communications after an opt-out.

If Elios or a carrier operates a blocking or suppression mechanism, Customer must not bypass it. Such a mechanism does not replace Customer’s duty to maintain its own records and honor requests received through Customer’s application, support channels, or other legally valid means.

Business texting to United States numbers requires A2P 10DLC campaign registration. Elios may ask Customer for information about its business and use case to register, and SMS may stay disabled for a number until registration is complete. Phone recognizes the standard STOP-family and HELP keywords in messages a Phone receives. When a recipient opts out, Phone adds them to that Phone’s suppression list, blocks further messages to them from that Phone, and sends one standard confirmation. When a recipient sends HELP, Phone sends one standard reply. Customer remains responsible for consent, message content, and every other requirement in this section.

#6. Recordings, transcription, and communication data

Customer is responsible for deciding whether to enable recording, live audio streaming, transcription, analysis, or onward transfer of a communication. Before doing so, Customer must provide the notices and obtain the consent or other authorization required in all relevant jurisdictions. Customer must not record or intercept communications unlawfully. A recording control does not establish that Customer has satisfied those requirements.

Customer must configure access and retention for recordings, messages, attachments, transcripts, and other communication data appropriately. Customer must provide its own privacy information to affected people and address their requests as required by law. Customer must take account of particularly sensitive information and any restrictions on the processing of biometric information, health information, financial information, or children’s information.

The Privacy Policy describes processing for which Elios determines the purposes and means. The Data Processing Addendum, where applicable, governs processing Elios performs on Customer’s behalf. The applicable documentation and completed processing schedules describe the data handled by Elios and its providers, available settings, and retention periods. The architecture of a control API does not, by itself, mean that communications media or metadata is never processed by Elios or its providers.

Elios does not transcribe calls. Through the API, Customer can stream live call audio to its own systems, where Customer’s own software or providers perform any speech processing. Elios records a call only when Customer starts a recording through the API; recording is off by default. Each Phone has limits on recording storage, contacts, and call and message history, stated in the documentation and subject to change. When recording storage or history reaches its limit, the oldest recordings and records are deleted first, and message attachments expire after the period stated there. Customer should export any recording or attachment it needs to keep. Deleting a Phone deletes all of its data, including its contacts, messages, call records, recordings, and media, within 30 days, and backup copies roll off within 35 days. Elios does not use communications data to train models. The Subprocessors page lists the providers involved.

#7. Numbers, caller identification, and porting

Phone numbers are assigned for permitted use under the applicable numbering rules and carrier arrangements. Assignment through Elios does not give Customer ownership of a number. Customer must use numbers and caller identifiers only as authorized and must not present misleading caller identification or a number it has no right to use.

Any port-in, port-out, number transfer, or release is subject to applicable law, technical support, carrier procedures, and proof of authority. Elios will not restrict a porting right that applicable law gives Customer. Customer must not cancel or release a number before an intended transfer is complete. Customer should plan for possible interruption during a transfer and remove a released number from its applications, public listings, and authentication settings.

Numbers may be reclaimed or reassigned where required by law, an applicable carrier rule, Customer’s release instruction, or a termination permitted under the Agreement. Elios will provide notice and a reasonable opportunity to act when available and lawful. Customer must not rely on indefinite access to a number after it has been released or its assignment has ended.

Elios does not currently support porting numbers in or out. A number is released when Customer deletes the Phone or closes its account. A released number may be reassigned, and Elios cannot guarantee that it can be recovered.

#8. Emergency communications and critical uses

Phone Services cannot call 911 or any other emergency number, and Elios does not provide emergency location information. Phone Services are not offered as a way to contact emergency services or as a replacement for a telephone service that provides emergency calling. Customer must not rely on Phone Services to reach 911, 112, 999, or another emergency number, and must not market its application as providing emergency calling through Phone Services. Customer must clearly communicate this limitation to users where the application’s presentation could create an expectation of emergency calling.

Customer must maintain a separate means of contacting emergency services. Customer must not use Phone Services as the sole channel for emergency dispatch, life-safety alarms, or another use in which a service interruption or communication error could foreseeably cause death or serious physical injury.

#9. Prohibited traffic and protection of the service

The platform-wide Acceptable Use Policy governs spam, fraud, harassment, impersonation, and other prohibited conduct across all Elios products. For Phone Services, Customer must also respect the communication permissions and carrier safeguards described in these terms. Customer must not generate artificial traffic to obtain revenue, inflate usage, test stolen payment methods, or exploit another party’s telecommunications charges.

Customer must secure credentials and promptly notify Elios if it suspects unauthorized access, toll fraud, or abusive traffic. Customer must reasonably cooperate with an investigation and disable compromised credentials or applications under its control. Responsibility for disputed charges is determined under the Agreement and applicable law; this paragraph does not make Customer responsible for Elios’s breach of the Agreement or failure to meet its own legal obligations.

Elios may restrict a number, destination, campaign, or account where reasonably necessary to address unlawful traffic, a serious security risk, a binding carrier direction, or a legal requirement. When practical and lawful, Elios will explain the reason and the steps needed to restore permitted use. Urgent restrictions may take effect before notice. Broader suspension and termination rights remain governed by the Terms of Service.

#10. Charges and delivery limitations

The applicable pricing page or Order and the Billing and Metering Policy describe the billable dimensions and rates for Phone Services. These may include assigned numbers, call duration, message segments, recordings, storage, and separately disclosed carrier or registration fees. Customer must review the actual rate and billing unit for the capability it enables. A message can consist of more than one billable segment. A resource such as an assigned number or retained recording may continue to incur charges while retained even when no call is in progress, where the applicable rate identifies that resource as billable.

Phone Services depend on communications networks and recipients’ systems. Delivery, caller-label presentation, latency, call completion, and message filtering may vary. Elios does not guarantee that a recipient will receive or answer a communication or that a carrier will accept every message. Any availability commitment or service credit must be expressly set out in an accepted Order or separate signed agreement. This section does not excuse obligations that applicable law makes mandatory.

#11. Contacts and updates

For Phone Service questions, write to support@elios.ai. Report abusive calls or messages originating through Elios to abuse@elios.ai. Include the relevant numbers, date, time and time zone, and a short description; do not send unnecessary sensitive content.

Updates to these terms follow the notice and acceptance process in the Terms of Service. Country-specific legal or carrier changes may require faster action as described in section 2.