RingCentral

Overview

RingCentral is a cloud communications platform providing Voice over IP (VoIP) telephony, video meetings, and team messaging. When detected on websites, RingCentral typically appears through embeddable click-to-call widgets, softphone interfaces, or video meeting components that enable visitors to connect with sales or support teams directly from the browser. The platform serves businesses that integrate their phone systems with their web presence for customer engagement.

What This Script Does

RingCentral embeds load from RingCentral's CDN and initialize communication widgets on the page.

• Scripts loaded: RingCentral's Embeddable Voice widget or RingCX digital engagement scripts load from RingCentral's CDN, rendering click-to-call buttons, softphone interfaces, or chat widgets within the host page
• WebRTC connections: For voice and video calls, the SDK establishes WebRTC connections through RingCentral's media servers, handling call setup, audio/video streaming, and call control (mute, hold, transfer)
• Cookies set: Session cookies to maintain the communication widget's state and authenticate the agent-side connection. The visitor-facing widget may set minimal session cookies for call continuity.
• Data collected: Device capabilities (microphone, speaker availability), network quality metrics for call optimization, caller identification data, and call metadata (duration, timestamp). Visitor-submitted information through pre-call forms (name, reason for call) is transmitted to RingCentral's servers.
• Browser storage: Session tokens and widget configuration may be stored in localStorage or sessionStorage to maintain widget state across page navigations.

Consent & Compliance

RingCentral falls under the functional consent category.

Under GDPR and ePrivacy, RingCentral communication widgets serve a functional purpose — enabling real-time communication initiated by the visitor. Session cookies and browser storage used for call management are required for the communication service to function. If the widget pre-loads on every page (setting cookies before visitor interaction), those cookies may not qualify as strictly necessary under the ePrivacy Directive until the visitor initiates a call.

Under CCPA/CPRA, call metadata, caller identification data, and any personal information submitted through pre-call forms constitute personal information. RingCentral processes this data for communication delivery under its data processing terms.

Should You Block This Without Consent?

No. RingCentral widgets provide functional communication features that visitors initiate by clicking to call or chat. Blocking the widget would remove the communication channel. For a conservative approach, implement a click-to-load pattern where the full RingCentral widget initializes only after the visitor clicks a static call button, avoiding pre-loading scripts and cookies on every page.