SpixSpix
PricingRecipesBlogDocs
Menu
PricingRecipesBlogDocs
Get Started
Legal

Communications Compliance Policy

This Communications Compliance Policy explains the rules customers must follow when using Spix for calls, texts, emails, recordings, transcripts, and AI-assisted communications.

Effective March 26, 2026VoiceSMSEmailRecordingTranscription

On this page

ScopeConsent and Contact ProvenanceCalling Hours, Frequency, and SuppressionRecording, Transcription, and AI DisclosuresIdentity, Content, and RepresentationChannel-Specific RulesDocumentation and Audit SupportSpix Rights and EnforcementQuestions

Related policies

Terms of UsePrivacy PolicyAcceptable Use PolicyCookie Policy

Questions

Send policy questions to [email protected].

Related policies

Terms of UsePrivacy PolicyAcceptable Use PolicyCookie Policy

Scope

This Policy applies to every communication you send, trigger, automate, record, transcribe, or analyze through Spix, including calls, SMS, MMS, email, voicemail, and follow-up workflows.

Spix may offer tooling that helps with registration, suppression, routing, opt-out handling, or workflow controls, but those tools do not replace your obligation to understand and follow the laws and rules that govern your use case.

Consent and Contact Provenance

Before using Spix to contact a person, you must determine what permission, notice, or lawful basis is required and obtain it before the communication is sent or the call is placed.

  • Maintain records showing who consented, when they consented, how they consented, and what they were told at the time.
  • Do not use purchased, scraped, borrowed, or otherwise unverifiable contact lists.
  • If consent is revoked, or if a contact opts out, immediately stop the prohibited or withdrawn communication type for that contact.

Calling Hours, Frequency, and Suppression

You must apply calling, texting, and emailing rules based on the recipient location, recipient timezone, applicable quiet-hours rules, and campaign category.

  • Honor do-not-call lists, internal suppression lists, unsubscribe lists, and carrier or provider suppression requirements.
  • Do not repeatedly contact recipients in ways that are excessive, coercive, or inconsistent with the consent you obtained.
  • When laws or carrier rules require a cooling-off period, follow-up limit, or contact-frequency limit, you must enforce it.

Recording, Transcription, and AI Disclosures

You are responsible for determining whether call recording, transcription, summarization, voice cloning, or AI-agent participation requires notice, consent, or another disclosure under the laws that apply to you and the recipient.

  • Provide required recording and monitoring disclosures before recording or transcribing a call.
  • Provide any AI-use disclosure required by law, contract, carrier rule, or platform policy.
  • Do not continue recording, transcribing, or analyzing communications after consent has been withheld or withdrawn where consent is required.

Identity, Content, and Representation

All communications sent through Spix must accurately identify the sender or caller and must not mislead recipients about who is contacting them, why they are being contacted, or what action is being requested.

  • Use accurate branding, caller ID, sender identity, reply paths, and campaign descriptions.
  • Do not mimic government entities, emergency services, courts, employers, financial institutions, or trusted brands in a deceptive way.
  • Do not use prompts or agent workflows that are designed to coerce, mislead, threaten, or bypass lawful objections.

Channel-Specific Rules

Different channels create different legal and operational obligations. You are responsible for the ones that apply to your use case.

  • Voice: comply with laws governing prerecorded or artificial voice calls, caller ID accuracy, call recording, abandonment, and calling times.
  • SMS and MMS: comply with opt-in requirements, STOP or equivalent opt-out handling, HELP or support expectations where applicable, campaign registration requirements, and carrier content rules.
  • Email: use accurate headers and subject lines, include an opt-out mechanism when required, honor unsubscribe requests, and avoid deceptive routing or domain practices.

Documentation and Audit Support

You must be prepared to explain and substantiate your traffic. If we ask for evidence of consent, campaign context, opt-in flows, recording disclosures, or sender identity, you must provide it promptly.

We may reject traffic, require additional review, or suspend access if you do not provide sufficient information or if we believe your use creates unacceptable risk.

Spix Rights and Enforcement

To protect the platform, our providers, and recipients, Spix may throttle, reject, suspend, or terminate traffic or accounts that appear to violate this Policy, our Terms, provider rules, or applicable law.

We may update this Policy from time to time to reflect legal developments, provider requirements, product changes, or abuse trends.

Questions

Spix does not provide legal advice. If you have questions about your obligations, consult your own counsel. Questions about this Policy may be sent to [email protected].

SpixSpix

Communications infrastructure for AI agents.

Product

PricingRecipesDocsDashboard

Compare

Spix vs TwilioSpix vs Bland AISpix vs VapiSpix vs Retell AISpix vs AgentMail

Resources

BlogQuickstartMCP Server

Open Source

GitHubspix-mcpHackathon Kit

Legal

Terms of UsePrivacy PolicyAcceptable UseCompliance PolicyCookie Policy

© 2026 Spix

Contact