Bandwidth - Communications Platform Privacy

Overview

Bandwidth is an enterprise communications platform providing voice calling, SMS/MMS messaging, and emergency (911) calling APIs. It operates as backend telecom infrastructure — a carrier-grade network that other platforms (like RingCentral, Zoom Phone, and Microsoft Teams) build upon. Bandwidth has no direct client-side JavaScript presence on third-party websites; all communications are handled server-to-server.

What This Script Does

Bandwidth does not deploy browser-side scripts on third-party websites. Its services are consumed via backend APIs:

Voice API: Server-to-server voice call origination and termination via SIP and REST APIs. No browser JavaScript is involved unless a third-party application (built on Bandwidth's APIs) deploys its own WebRTC client.
Messaging API: SMS and MMS sending and receiving via REST API. Messages are processed entirely server-side.
Emergency services: 911 call routing infrastructure that operates at the network level with no browser-side components.
No cookies: Bandwidth does not set cookies on third-party domains.
No tracking: No visitor data collection, behavioral tracking, or client-side analytics.

If Bandwidth appears in a website's script audit, it is likely miscategorized or detected through DNS resolution patterns rather than actual browser-loaded JavaScript.

Consent & Compliance

Bandwidth falls under the functional consent category as communications infrastructure. It does not process website visitor data or set cookies.

Under GDPR and ePrivacy, Bandwidth's server-side API operations do not trigger cookie consent requirements. There are no scripts accessing the user's terminal equipment. The communications data processed (phone numbers, message content) is handled server-side under the application operator's data processing agreements.

Under CCPA/CPRA, Bandwidth acts as a service provider processing communications data on behalf of its customers, falling under the service provider exception.

Should You Block This Without Consent?

No. Bandwidth has no client-side scripts to block. It operates as backend telecom infrastructure with no cookies, no browser-side tracking, and no visitor data collection. Blocking it would have no effect on the visitor's browser experience.

Visit website

Consent Categories

Functional

Also Known As

bandwidthbandwidth.combandwidth voice apibandwidth messagingbandwidth 911bandwidth communications

Industries

Computers Electronics and TechnologyTelecommunicationsBusiness and Consumer ServicesProgramming and Developer Software

Tracked Domains (1)

bandwidth.comFunctional

Frequently Asked Questions

Does Bandwidth require cookie consent?

Conditional. Bandwidth is a backend telecom API provider with no browser-side scripts on third-party websites. If your site uses a Bandwidth-powered WebRTC client, session cookies may be set for call management — these are functional and typically do not require consent under ePrivacy rules.

What data does Bandwidth collect?

Bandwidth operates server-to-server for voice, SMS, and 911 APIs with no direct client-side tracking. If a WebRTC component is present, it may collect IP addresses and session metadata for call routing. No persistent advertising identifiers or cross-site tracking cookies are set by Bandwidth infrastructure.

How does ConsentStack detect Bandwidth?

ConsentStack classifies Bandwidth as a functional vendor due to its role as backend communications infrastructure. Because it lacks a browser-side tracking footprint, ConsentStack does not block it by default. If a WebRTC session component is detected, it is treated as functional and consent blocking is not applied.