Voice & AI Service Terms
Last Updated: December 2025
1. Mandatory AI Identification
Inflowence provides automated Voice Assistants. Customer agrees that every interaction initiated or received by a Voice Assistant shall begin with a clear disclosure that the caller is speaking with an "AI Assistant," "Automated System," or similar language. Customer shall not configure Voice Agents to impersonate a specific human being or to deceive End-Users regarding their non-human nature.
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.
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.
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.
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.
Inflowence provides:
- Default recording disclosure language in voice prompts
- Tools to configure custom disclosure messages
- Call recording features subject to your compliance
- Technical capabilities to capture and store consent
Inflowence does not:
- Determine which laws apply to your specific calls
- Guarantee legal compliance of your configurations
- Provide legal advice regarding recording laws
- Assume liability for your recording practices
3. Biometric Data Disclaimer
3.1 What We Do
Inflowence and its sub-processors (AWS, GoHighLevel) process voice data for:
- Transcription: Converting speech to text
- Intent Recognition: Understanding caller requests
- Sentiment Analysis: Detecting tone and emotion
- Quality Monitoring: Improving service quality
3.2 What We Don't Do
Inflowence explicitly does not:
- Use voice data to identify specific individuals ("voiceprints")
- Create biometric identifiers from voice recordings
- Use voice data for biometric authentication
- Maintain a database of voice biometric profiles
- Share voice data for biometric identification purposes
3.3 Customer Prohibition
You are prohibited from:
- Using Inflowence to collect or process biometric identifiers
- Creating voiceprints or voice signatures
- Using voice data for biometric authentication
- Maintaining databases of biometric voice data
- Any use that would trigger biometric privacy laws (e.g., Illinois BIPA)
3.4 State Biometric Privacy Laws
Several states have biometric privacy laws, including:
- Illinois (BIPA): Strict requirements for biometric data collection
- Texas (CUBI): Civil liability for biometric data misuse
- Washington: Prohibits enrolling biometric data without consent
- California (CCPA): Treats biometric data as sensitive personal information
These laws do not apply to Inflowence's transcription and analysis because we do not create biometric identifiers.
4. AI "Hallucinations" & Liability
4.1 Nature of AI Technology
Artificial intelligence systems, including Inflowence's voice agents:
- Generate responses based on training and prompts
- May produce inaccurate, incomplete, or nonsensical responses ("hallucinations")
- Cannot guarantee 100% accuracy
- Improve over time but are not perfect
- May misunderstand context or intent
4.2 Your Responsibility
You are responsible for:
- Reviewing the logic and responses of your AI agents
- Testing voice agents before deploying to customers
- Monitoring AI interactions for quality and accuracy
- Updating prompts and training to reduce errors
- Providing human oversight for critical interactions
- Handling complaints about AI responses
4.3 Inflowence's Disclaimer
Inflowence provides Voice Agents "as-is" and makes no warranties about:
- Accuracy of AI-generated responses
- Suitability for any particular purpose
- Freedom from errors or "hallucinations"
- Compliance with your specific legal requirements
- Quality or appropriateness of interactions
4.4 Limitation of Liability
Inflowence is not liable for:
- Commitments or promises made by AI agents
- Contracts or agreements formed by AI agents
- Misinformation provided by AI agents
- Decisions made based on AI responses
- Financial losses from AI errors or hallucinations
- Reputational harm from AI interactions
- Legal violations resulting from AI behavior
4.5 Indemnification
You agree to indemnify Inflowence for any claims arising from:
- Your AI agent's responses or actions
- Commitments made by your AI agents
- Misinformation provided by your AI
- Your failure to properly configure or monitor AI agents
5. Data Processing & Storage
5.1 What We Collect
When you use Voice AI features, we may collect:
- Audio recordings of calls
- Transcripts of conversations
- Metadata (duration, phone numbers, timestamps)
- Intent classification and sentiment scores
- Quality and performance metrics
5.2 How We Use Voice Data
Voice data is used to:
- Provide the voice agent service
- Generate transcripts for your review
- Improve AI model performance
- Ensure quality and compliance
- Provide customer support
5.3 Data Retention
- Call recordings are retained per your account settings
- Transcripts are retained with associated records
- Metadata is retained for service improvement
- You can configure retention periods in your account
- See our Privacy Policy for details
5.4 Data Security
We protect voice data with:
- Encryption in transit (TLS)
- Encryption at rest
- Access controls and authentication
- Regular security audits
- Compliance with industry standards
5.5 Sub-Processors
Voice data may be processed by:
- Amazon Web Services (AWS): Hosting and transcription
- GoHighLevel (GHL): Call routing and management
- See our Subprocessors List for complete details
6. Compliance Templates
6.1 Recommended Call Scripts
Professional Inbound (Standard):
"Thank you for calling [Business Name]. Please note that this call is being recorded for quality assurance and will be handled by our AI Assistant. How can we help you today?"
Direct & Concise (High Volume):
"Hi! You're speaking with [Business Name]'s automated AI assistant on a recorded line. To get started, may I have your name?"
Outbound Lead Follow-up:
"Hello, this is an automated AI assistant calling from [Business Name] on a recorded line regarding your recent inquiry about [service]. Do you have a moment to chat?"
6.2 Two-Party Consent States Script
For calls to California, Florida, Illinois, etc.:
"Hello from [Business Name]. Before we begin, I need to inform you that I'm an AI assistant and this call is being recorded. Is it okay if we continue?"
[Wait for affirmative response before proceeding]
6.3 Recording-Only Notice (One-Party States)
For states where only one-party consent is required:
"This call is being recorded for quality and training purposes. I'm an AI assistant from [Business Name]. How can I help you today?"
7. State-Specific Requirements
7.1 California (CIPA)
California Invasion of Privacy Act requires:
- All-party consent for call recording
- Explicit consent from all parties
- Criminal penalties for violations
Best Practice: Always obtain verbal "yes" before recording in California.
7.2 Florida
Florida Statute § 934.03 requires:
- All-party consent for recording
- Civil and criminal penalties for violations
- Consent can be verbal or through notification
7.3 Illinois (BIPA)
Illinois Biometric Information Privacy Act:
- Does not apply to general voice processing for transcription
- May apply if creating biometric identifiers from voice
- Remember: Inflowence does not create voiceprints
7.4 Federal (TCPA)
Telephone Consumer Protection Act:
- Regulates automated calls and texts
- Requires prior express consent for marketing calls
- AI agents are subject to TCPA rules
- See our Messaging Policy for details
8. Monitoring and Enforcement
8.1 Compliance Checks
Inflowence may review:
- AI agent configurations for required disclosures
- Call recordings for proper notices
- Customer complaints about AI interactions
- Adherence to this policy
8.2 Violations
Violations of this policy may result in:
- Warning and required corrections
- Temporary suspension of voice features
- Account termination for severe violations
- No refunds for policy violations
9. Updates and Changes
This policy may be updated to reflect:
- Changes in applicable laws
- New AI technologies or features
- Court decisions or regulatory guidance
- Industry best practices
Material changes will be communicated via email.
10. Your Legal Obligations
By using Inflowence's Voice AI features, you acknowledge:
- You are responsible for legal compliance in your jurisdiction
- You understand recording consent requirements
- You will provide all required disclosures
- You will not use voice data for biometric identification
- You accept responsibility for AI agent behavior
- Inflowence is not your legal advisor
Recommendation: Consult with a licensed attorney familiar with telecommunications law in your state before deploying voice AI agents.
Related Policies
Contact Us
Questions about Voice & AI compliance:
- Email: compliance@inflowence.ai
- Legal: legal@inflowence.ai
- Website: Inflowence
Legal Disclaimer: This document provides information about Inflowence's Voice AI features and general guidance on compliance. It is not legal advice. You should consult qualified legal counsel to ensure compliance with all applicable laws in your specific situation.