Vadacom
Privacy Policy
Mobile Applications

This Privacy Policy explains what personal data Vadacom Limited ("Vadacom") collects from our customer (entity who purchased the product or service from Vadacom) and the user (entity who uses Vadacom's product or service).

Data Collection

Vadacom Limited products may collects a variety of data sources in order to provide our products and services.

Personal Information

First name, family name, email address, phone number, mobile number, avatar image, etc.

Credentials

Passwords and other security information used for authentication.

Device Information

Hardware information, unique device identifiers, unique user identifiers, network information, geolocation data, etc.

Communication Data

Call recordings, call logs, call metadata, instant messages, personal contacts, status updates, etc.

Usage Information

User communication and application interaction data is collected.

Data Usage

Vadacom uses the data collections to provide our products and services. In most cases this data is also accessible to the administrators of the customer's system. Personal data will be kept confidential with the customer and third party providers unless obliged to do so by the law. Vadacom may access the user's or customer's data strictly for internal purposes; in order to provided customer support, security improvements, product or service improvements, etc.

Security

We use industry-recognised security standards to prevent unauthorized access and of disclosure of all sensitive data.

Mobile Permissions

Vadacom mobile applications may request specific permissions from the operating systems on install or during runtime. Here follow a brief explanations of why we have requested permissions pertaining to the users personal data.

Telephony/VoIP/SIP

We require telephone related permission in order to send audio calls over VoIP. Calls via the Buddy softphone, have their audio/video and call metadata transmitted through the Buddy server. The Buddy administrator for your organisation may have enabled permanent call recording and can potentially access the recorded file.

Microphone

We require microphone access in order to transmit audio data for VoIP telephone call. The same implications as per 'Telephony' permissions applies here.

Camera

We may request camera access in order to transmit video data for VoIP telephone call. The same implications as per 'Telephony' permissions applies here.

Network Access

We may require access to determine the devices network in order to select the appropriate method to effectively transmit data.

Phone State

We request access to read incoming cellular calls. We do not record or transmit the information provided. We require this permission in order for the application to manage a concurrent SIP and cellular phone calls. Failure to allow this permission would mean that phone would ring while you are on current call and potentially could have two active phone calls using the same speaker and microphone.

Local Phonebook Contacts

We request access to read local contact information. Firstly we use this information to match incoming caller identification or contact data that are known by the device but unknown by the Buddy server. In this case we do not transmit the data. Secondly the user can optionally upload their personal phone contacts to Buddy desktop applications. This information will be stored in the Buddy server and served only to the Buddy user who uploaded the data.

Battery Privileges

We may request privileged battery access. Due to the real-time nature of a softphone call we need to keep an active network connect open back to the server to allow for incoming calls. This action may decrease the battery life of mobile devices.

Further Information

Further questions or concerns may be requested from our customer service department: service@vadacom.co.nz