Voice & AI Service Terms

Effective Date: April 18, 2026

1. AI Identification

Inflowence provides automated Voice Assistants. Customer is solely responsible for determining, and complying with, applicable law in each jurisdiction where its Voice Assistants initiate or receive calls.

Jurisdictions that require AI disclosure. Certain jurisdictions require clear and conspicuous disclosure that a communication is automated or AI-generated. These include, without limitation:

  • California. Bot Disclosure Act, Cal. Bus. & Prof. Code §§ 17940–17943, where a bot is used to incentivize a purchase or sale of goods or services or to influence a vote in an election.
  • Utah. Utah Artificial Intelligence Policy Act, Utah Code § 13-2-12, which requires proactive disclosure by regulated occupations and on-request disclosure in other consumer-facing contexts.
  • Colorado. Colorado Artificial Intelligence Act, SB 24-205, effective February 1, 2026, for consumer-facing use of high-risk AI systems.
  • Federal — outbound calls. The Telephone Consumer Protection Act (47 U.S.C. § 227) and 47 CFR § 64.1200 impose identification and consent requirements on outbound artificial-or-prerecorded-voice calls, which the FCC's February 2024 Declaratory Ruling (CG Docket No. 02-278) confirms include AI-generated voice.

Where any such law applies, Customer must configure the Voice Assistant to make a clear and conspicuous disclosure, in the Voice Assistant's first utterance and before any request for information, that the caller is speaking with an "AI Assistant," "Automated System," "AI Receptionist," or substantially similar language. The word "virtual" alone does not satisfy the clear-and-conspicuous requirement, because "virtual receptionist" is a well-established industry term for a remotely-located human receptionist and a reasonable consumer may understand it that way.

Jurisdictions that do not require AI disclosure. In jurisdictions without an applicable bot-disclosure statute — including, as of the Effective Date above, Arizona and most other U.S. states for inbound customer-service calls — such disclosure is not legally required, and Customer may choose whether its Voice Assistant proactively identifies itself as AI. Inflowence recommends disclosure as a best practice even where not required, because undisclosed AI interactions can still expose Customer to claims under general consumer-protection laws, including the Arizona Consumer Fraud Act (A.R.S. § 44-1521 et seq.), Section 5 of the FTC Act (15 U.S.C. § 45), and analogous state unfair-and-deceptive-acts-and-practices statutes, where a reasonable consumer would have believed they were speaking with a human. Customer assumes all risk of a non-disclosure decision.

Prohibited in all jurisdictions, regardless of disclosure choice. Customer shall not configure, prompt, or otherwise cause a Voice Assistant to:

  • impersonate a specific natural person;
  • impersonate, or falsely suggest affiliation with, any federal, state, tribal, or local government agency, court, or law-enforcement body;
  • impersonate, or falsely suggest affiliation with, any actual business, brand, financial institution, healthcare provider, insurer, utility, or other real entity without that entity's express written authorization; or
  • affirmatively represent to an End-User that the Voice Assistant is a human being, or deny being AI in response to a direct question from the End-User. Silence as to the Voice Assistant's automated nature, in a jurisdiction where proactive disclosure is not required, is not an affirmative representation and is permitted; a spoken denial of AI status is not.

This obligation reflects, without limitation, the FTC Rule on Impersonation of Government and Businesses (16 CFR Part 461), applicable state anti-impersonation statutes, and general UDAP principles.

Customer responsibility. Customer is solely responsible for its prompts, agent configurations, Voice Assistant self-identification choices, and deployments in every jurisdiction in which it operates. Inflowence is not liable for Customer's configuration choices or for Customer's failure to assess or comply with applicable law. Customer's indemnification obligations under the Terms of Service apply to any claim arising from a disclosure or non-disclosure decision.

2. Call Recording & Consent

Customer acknowledges that certain jurisdictions require the consent of all parties to a recording.

Inbound Calls: Customer must ensure that any call answered by a Inflowence Voice Agent includes a "This call is being recorded for quality/training purposes" disclosure immediately.

Customer Responsibility: Customer assumes all liability for ensuring that the use of recording features complies with local "Two-Party Consent" laws.

Two-party / all-party consent states. Jurisdictions that require consent from all parties to a recorded call include, without limitation, California (Penal Code §§ 631–632, CIPA), Florida (Fla. Stat. § 934.03), Illinois, Maryland, Massachusetts, Montana, New Hampshire, Pennsylvania, and Washington. Customer must obtain affirmative verbal consent before recording calls with parties in these jurisdictions.

3. Biometric Data Disclaimer

Inflowence and its sub-processors (AWS, GoHighLevel) process voice data for transcription and intent recognition only. Inflowence does not use voice data to identify specific individuals or for biometric "fingerprinting." Customer is prohibited from using the Service to collect or process biometric identifiers.

Customer biometric prohibition. Customer shall not use the Service to create voiceprints or voice signatures, perform biometric authentication, or maintain databases of biometric voice data, including any use that would trigger state biometric privacy laws such as the Illinois Biometric Information Privacy Act (BIPA, 740 ILCS 14), the Texas Capture or Use of Biometric Identifier Act (CUBI, Bus. & Com. Code § 503.001), Washington RCW 19.375, or the California Consumer Privacy Act's sensitive personal information provisions. Because Inflowence does not create biometric identifiers through transcription and intent recognition, these laws do not apply to Inflowence's processing; they may apply to Customer's configuration choices.

4. AI "Hallucinations" & Liability

Inflowence provides the Voice Agent "as-is." Customer is responsible for reviewing the logic and responses of their AI agents. Inflowence is not liable for any commitments, contracts, or misinformation provided by an AI Agent to an End-User.

Indemnification. Customer shall indemnify and hold harmless Inflowence from any claims, damages, or liabilities arising from the Voice Agent's responses, commitments made by the Voice Agent, misinformation conveyed by the Voice Agent, or Customer's failure to properly configure or monitor its Voice Agents.

5. Data Processing, Retention & Sub-Processors

Call recordings, transcripts, and associated metadata are retained in accordance with the retention periods configured on Customer's account and the Inflowence Privacy Policy. Voice data may be processed by Amazon Web Services (AWS) for hosting and transcription and by GoHighLevel (GHL) for call routing and management. A current list of sub-processors is available at Subprocessors.

Related Policies

Contact Us

For questions about voice and AI compliance:

Email: compliance@inflowence.ai

By using Inflowence's Voice & AI features, you acknowledge that you have read, understood, and agree to this policy.