Information handled
- Account and authentication information: the RTC extension number, service domain, SIP password and control-service credentials contained in the user-selected
.figprofile. - Identity and call information: agent names or identifiers, caller names and telephone numbers, dialled numbers, call direction, outcome and timestamps.
- Communications: microphone audio and incoming call audio needed to provide live WebRTC calls. The extension does not record or retain call audio.
- Operational information: login, queue and pause state, selected pause reason, waiting-call information, parked-call information and live wallboard data.
- Technical information: IP addresses and connection metadata necessarily processed by the configured SIP, WebRTC and control infrastructure.
How information is used
Information is used only to register the authorised RTC extension; place, receive and control calls; send keypad tones; provide agent login, queue and pause controls; show caller ID and call history; display the live wallboard; and troubleshoot service operation.
Local storage and retention
The imported profile, the latest selected pause reason and up to 50 call-history entries are stored locally in the browser profile so the extension can operate between sessions. Users can remove the saved profile from the extension settings. Local extension data can also be removed by uninstalling the extension or clearing its stored data. Retention of server-side operational logs is governed by the configured RTC service and the relevant customer agreement.
Sharing and transfers
The extension sends information only to the customer-specific RTC, SIP and control endpoints identified by the authorised profile, and to infrastructure providers needed to deliver those services. TaxiApps does not sell user data, use it for advertising, transfer it for unrelated purposes, or use it to determine creditworthiness or for lending.
Website and browser activity
The extension does not read or modify visited webpages, collect browsing history, inject scripts into websites, monitor general keystrokes or mouse activity, or collect website content. Number-key input is handled only while the extension phone is in use for dialling and DTMF.
Security
WebRTC call media uses browser-provided encrypted transport. Access credentials are used only to authenticate with the configured service endpoints. Users should protect access to their browser profile and device and should import profiles only from an authorised administrator.
Chrome Web Store Limited Use
The use of information received from Chrome APIs complies with the Chrome Web Store User Data Policy, including its Limited Use requirements.
Your choices
Microphone access can be denied or withdrawn in browser settings, although calling will then be unavailable. Users can clear call history and profile data by removing the extension’s stored data or uninstalling it. Questions or data requests should be submitted through the TaxiApps contact page or the user’s TaxiApps service administrator.
Changes to this policy
This page may be updated when the extension or its data handling changes. The effective date above will identify the latest version.