Crescendo AI

crescendo.ai

Crescendo AI declares 8 subprocessors in its subprocessor list, which we last checked on Nov 11, 2026 (evidence). No published changes since we first read it on Nov 6, 2026. 2 tracked vendors name Crescendo AI as a subprocessor, including Otter Meeting Agent and Concord.

Subprocessors CSV · Atom DORA draft CSV what's this? · 

8 third parties.

NamePurposeLocationListed since
Partner Hero America S de RL Honduras; Location; Purpose; Services and support
Partner Hero Central America S. de R.L. de C.V. Honduras; Location; Purpose; Services and support
Partner Hero Eastern Europe S.R.L Location; Purpose; Romania; Services and support
Partner Hero International LLC Location; Purpose; Services and support; United States
Partner Hero Philippines Corporation Location; Philippines; Purpose; Services and support
Partner Hero Services Canada Canada; Location; Purpose; Services and support
Partner Hero South Africa (Pty) Ltd. Location; Purpose; Services and support; South Africa
Resources
AI service provider: real time conversations, transcriptions, CX insights; AI-powered knowledge platform; Admin; Automatic speech recognition: call recordings; Azure: text-to-speech, real time conversations, transcripts, CX Insights; Both; CRM – manage prospect/customer contact data, track interactions, send sales/marketing/support communications; Cache: transcripts; Cloud hosting services; Cloud-based customer service platform: communications content such as cloud recordings or in-meeting chat transcripts; Cloud-based real-time voice/WebRTC media transport and room infrastructure; processes live audio and related session metadata for voice interactions.; Description of Processing; Google Cloud Platform: cloud hosting services; Google Gemini and Vertex AI — generative AI services used for conversation processing, transcript analysis, CX insight generation, assistant response generation, and knowledge/document processing; Google Workspace: file storage, content collaboration, communications; Internal communications and customer-facing Slack integration messaging and conversation content.; Outbound emails, transcripts; Platform; Purpose; Real time conversations, transcripts, and CX insights; Secure BYO-PC technology; Speech-to-text, Text-to-speech, real-time conversations; Telephony: voicebot and inbound telephony; Text to Speech and Real Time conversations; Text to Speech, Real Time conversations
Amazon Nova Sonic (Amazon Web Services, Inc.); Deepgram Inc.; Elasticsearch BV; ElevenLabs Inc.; Google LLC; Groq Inc.; Guru Technologies, Inc.; HubSpot, Inc; LiveKit Incorporated; Location; Microsoft Corporation Inc.; Name; OpenAI LLC; Redis Inc.; Salesforce Inc. (Slack); Soniox Inc.; Twilio Inc.; Twilio Inc. (Sendgrid); United States; Venn US Inc.; Zendesk Inc.

Web TechnologiesCSV · Atom

Crescendo AI's homepage made 162 requests to 36 domains, 17 services controlled by another company, and 1 domain not identified.

Analytics (5): HubSpot, Meta, LinkedIn, Contentsquare, LeadfeederAdvertising (2): Google Cloud, OpenAIMarketing automation (1): ApolloA/B Testing (1): WebflowCDN (1): jsDelivrOther (7): Page builders: Finsweet (Consent Pro); usually detected as Page builders: Finsweet; Security: ClickCease™; usually detected as Security: Amazon Web Services; Appointment scheduling: RevenueHero; Email: LiveIntent; reviewed as Video players: Vimeo

17 third parties by category: Analytics 5Advertising 2Marketing automation 1A/B Testing 1CDN 1Other 7

Third parties 17 · 158 requests
Webflow Intellimize Webflow 1.6.0 jQuery 3.5.1 38% of the page's requests 62
Google Cloud DoubleClick Floodlight Google Analytics Google Font API Google Hosted Libraries Google Tag Manager 27% of the page's requests 44
HubSpot HubSpot HubSpot Analytics 6% of the page's requests 9
jsDelivr jsDelivr 6% of the page's requests 9
Meta Facebook Pixel 2.9.438 3% of the page's requests 5
RevenueHero RevenueHero 3% of the page's requests 5
LinkedIn Linkedin Insight Tag 2% of the page's requests 4
LiveIntent LiveIntent 2% of the page's requests 4
Apollo Apollo.io 2% of the page's requests 3
OpenAI ChatGPT Ads Measurement Pixel 2% of the page's requests 3
Contentsquare Contentsquare 1% of the page's requests 2
Finsweet (Consent Pro) Finsweet 1% of the page's requests 2
Leadfeeder Leadfeeder 1% of the page's requests 2
Amazon Web Services s3-us-west-2.amazonaws.com <1% of the page's requests 1
ClickCease™ ClickCease <1% of the page's requests 1
Finsweet finsweet.com <1% of the page's requests 1
Vimeo vimeo.com <1% of the page's requests 1
Unknown 1 · 1 request

embedly.com

First party 1 · 3 requests
Crescendo AI Cloudflare Embedly GSAP 3.15.0 HSTS HTTP/3 Open Graph Priority Hints Webpack core-js 3.32.2 2% of the page's requests 3

13 tracked companies loaded by the homepage are not in Crescendo AI's subprocessor list. A website can use a service without it processing customer data.

Subprocessor of (2)CSV · Atom

2 companies
  • Concord concord.app Sales chatbot
  • Otter Meeting Agent otter.ai The subprocessor only has access to Customer Data in the course of customer-initiated support cases.

ComplianceCSV · Atom

Certified
Says it complies with

Certifications as Crescendo AI's trust center lists them; reports are usually shared on request (evidence)

Service statusCSV · Atom

Aug 15: before our history of this status pageAug 16: before our history of this status pageAug 17: before our history of this status pageAug 18: before our history of this status pageAug 19: before our history of this status pageAug 20: before our history of this status pageAug 21: before our history of this status pageAug 22: before our history of this status pageAug 23: before our history of this status pageAug 24: before our history of this status pageAug 25: before our history of this status pageAug 26: before our history of this status pageAug 27: before our history of this status pageAug 28: before our history of this status pageAug 29: before our history of this status pageAug 30: before our history of this status pageAug 31: before our history of this status pageSep 1: before our history of this status pageSep 2: before our history of this status pageSep 3: before our history of this status pageSep 4: before our history of this status pageSep 5: before our history of this status pageSep 6: before our history of this status pageSep 7: before our history of this status pageSep 8: before our history of this status pageSep 9: before our history of this status pageSep 10: before our history of this status pageSep 11: before our history of this status pageSep 12: before our history of this status pageSep 13: before our history of this status pageSep 14: before our history of this status pageSep 15: before our history of this status pageSep 16: before our history of this status pageSep 17: before our history of this status pageSep 18: before our history of this status pageSep 19: before our history of this status pageSep 20: before our history of this status pageSep 21: before our history of this status pageSep 22: before our history of this status pageSep 23: before our history of this status pageSep 24: before our history of this status pageSep 25: before our history of this status pageSep 26: before our history of this status pageSep 27: before our history of this status pageSep 28: before our history of this status pageSep 29: before our history of this status pageSep 30: before our history of this status pageOct 1: before our history of this status pageOct 2: before our history of this status pageOct 3: before our history of this status pageOct 4: before our history of this status pageOct 5: before our history of this status pageOct 6: before our history of this status pageOct 7: before our history of this status pageOct 8: before our history of this status pageOct 9: before our history of this status pageOct 10: before our history of this status pageOct 11: before our history of this status pageOct 12: before our history of this status pageOct 13: before our history of this status pageOct 14: before our history of this status pageOct 15: before our history of this status pageOct 16: before our history of this status pageOct 17: before our history of this status pageOct 18: before our history of this status pageOct 19: before our history of this status pageOct 20: before our history of this status pageOct 21: before our history of this status pageOct 22: before our history of this status pageOct 23: before our history of this status pageOct 24: before our history of this status pageOct 25: before our history of this status pageOct 26: before our history of this status pageOct 27: before our history of this status pageOct 28: before our history of this status pageOct 29: before our history of this status pageOct 30: before our history of this status pageOct 31: before our history of this status pageNov 1: before our history of this status pageNov 2: before our history of this status pageNov 3: before our history of this status pageNov 4: before our history of this status pageNov 5: before our history of this status pageNov 6: before our history of this status pageNov 7: no incident reportedNov 8: no incident reportedNov 9: no incident reportedNov 10: no incident reportedNov 11: no incident reportedNov 12: no incident reported

90 days agotoday

No incidents reported since Nov 7, 2026

As Crescendo AI's status page reports its own incidents (scheduled maintenance left out), read every few hours since (evidence)

ChangesCSV · Atom

See the list as we read it on any date: Time machine

None since tracking began.

Rating badge for Crescendo AI's site

Crescendo AI transparency rating

It updates with the rating.

<a href="https://thirdpartyindex.com/vendors/crescendo-ai"><img src="https://thirdpartyindex.com/badge/crescendo-ai.svg" alt="Crescendo AI transparency rating on Third Party Index" height="20"></a>
[![Crescendo AI transparency rating on Third Party Index](https://thirdpartyindex.com/badge/crescendo-ai.svg)](https://thirdpartyindex.com/vendors/crescendo-ai)