Google Play data safety section for Vivox#

Starting April 2022, Android developers publishing on the Google Play store must define what data their apps collect, including the data collected by integrated third-party SDKs. For your convenience, this topic provides information on Vivox data collection practices.

Important: The following data disclosures are only for the Vivox SDK. You are also responsible for providing any additional disclosures for your app, including other Unity SDKs and/or third-party SDKs used in your app.

For more information on Google's data safety disclosure policies, including terminology definitions, please see the Google documentation.

Data collection survey#

* Voice data is collected only in the context of server-side recording (SSR), and is used for performance monitoring and product improvement purposes. Today, data is processed ephemerally. This stands to change in coming months when we will begin storing it for analysis and model training. Today, users (where SSR is deployed) have no choice but to allow the integrating developer to collect their audio data. The SDK also collects performance data, which users cannot opt out of.

** Voice data is not encrypted, but the signaling is. Voice data is encoded (not encrypted), and gets decoded by the SDK/client side. The purpose of this is for app functionality and analytics.

*** We do not store user data, and thus have little to remove in the event of such requests.

Data types#

****** No if using server-side recording (SSR), otherwise yes.