Introduction
This policy applies to the TaxiApps RTC application for Android and iOS (the “app”). Users import a configuration profile supplied by their taxi or private-hire operator. The app uses it to connect to the operator’s SIP, WebSocket and HTTPS services.
The wallboard can be used without a paid app subscription. An active weekly or monthly Voice Pro subscription, purchased through Google Play or the Apple App Store, is required to make and receive calls. The subscription unlocks app functionality; it does not include telephone service, calling credit or an operator account.
Features include incoming and outgoing audio calls, DTMF keypad tones, mute and speaker controls, agent login and logout, queue controls, pause reasons, a live operational wallboard, call pickup and locally stored call history.
Who controls the data
TaxiApps
TaxiApps is responsible for the design and provision of TaxiApps RTC and is a controller for personal information TaxiApps itself receives and determines how to use, such as information submitted in a support enquiry or diagnostic information deliberately shared for troubleshooting.
Your operator
The operator supplying your configuration normally determines why and how account details, call records, agent status, queue information, wallboard data and other operational information are processed on its systems. It will normally be a separate controller for this processing, and its privacy policy may also apply.
On-device processing
The app processes configuration, credentials, call information and user actions on the device to provide its functions. Depending on the working arrangement, the operator may determine the purposes of this business use. Local storage does not mean that no personal information is processed.
Information stored on the device
The imported profile is stored locally so the app can reconnect. It may contain:
- a SIP extension, SIP domain and SIP password;
- a profile label; and
- a control-service username and control-service password.
TaxiApps RTC also stores call history locally. Users should protect access to their device and import profiles only through an authorised, trusted process.
Microphone and call audio
TaxiApps RTC requires microphone permission so the user can speak during audio calls. Access is used only for calling functionality and is subject to Android or iOS permissions and controls.
Call audio is transmitted as part of the SIP/VoIP session to the services specified by the operator. The operator or its providers may process call audio or call records under their own arrangements. Ask your operator whether calls may be monitored or recorded. TaxiApps does not use microphone or call audio data for advertising or cross-app tracking.
Information processed by operator services
The app communicates directly with the configured SIP, WebSocket and HTTPS endpoints. Information sent, received or generated may include:
- account identifiers and authentication credentials;
- call signalling, call records and call-related identifiers;
- agent login, logout and availability status;
- queue membership, queue controls and pause reasons;
- call pickup and related operational events;
- wallboard and other live operational information; and
- technical connection data required to operate and secure the services.
Live wallboard information comes from the configured operator service. The operator is responsible for explaining its purposes, lawful bases, recipients, retention and any monitoring or recording on its systems.
Purposes and lawful bases under UK GDPR
Where TaxiApps acts as controller, purposes include providing and maintaining the app, responding to requested support, diagnosing faults, protecting the app, investigating security incidents, meeting applicable legal requirements, and optional processing for which consent is specifically requested. The potential lawful bases are performance of a contract, legitimate interests, compliance with a legal obligation, or consent, as applicable. Where TaxiApps acts only on an operator’s documented instructions, the operator is responsible for identifying the lawful basis.
Data sharing and processors
The app sends information to the services specified by the imported configuration as necessary to provide its functions. TaxiApps may disclose information it controls where reasonably necessary to provide requested support, use suppliers acting under appropriate instructions and safeguards, comply with law, or establish, exercise or defend legal claims.
TaxiApps does not sell personal information. The operator is responsible for identifying recipients and processors used for its SIP, control, call-recording or operational services.
International transfers
The location of operator-side processing depends on endpoints, infrastructure and suppliers selected by the operator. Contact your operator to learn whether information is transferred outside the United Kingdom and what safeguards apply.
If TaxiApps transfers personal information it controls to a country not covered by UK adequacy regulations, TaxiApps will use an applicable transfer mechanism and safeguards required by UK law unless a legal exception applies.
Retention and deletion
Configuration details and call history remain locally stored while retained in the app. Users can remove their saved configuration inside TaxiApps RTC. Removing the app deletes its locally stored configuration and call history, subject to normal Android or iOS operation and any backups controlled by the user or their organisation.
Deleting local information does not necessarily delete related information held by the operator. TaxiApps retains personal information it controls only as long as reasonably necessary for its purpose and applicable legal, security or dispute-resolution requirements.
Security
TaxiApps uses proportionate technical and organisational measures intended to protect information against accidental loss, misuse and unauthorised access or disclosure. No application, transmission method or storage system can be guaranteed completely secure.
Diagnostic information may be available through standard Apple and device logs, but credentials must never be intentionally written to logs. Do not share configuration files, credentials or unreviewed diagnostic material with unauthorised people. The relevant operator and its providers are responsible for security of operator endpoints and operator-side records.
Subscriptions, tracking, analytics and advertising
Subscription purchases are processed by Google Play or the Apple App Store. TaxiApps RTC receives entitlement and product information needed to show purchase options and determine whether Voice Pro calling is active. TaxiApps does not receive or store full payment-card details through the app.
TaxiApps does not use TaxiApps RTC to deliver advertising. The app contains no advertising SDKs, does not sell personal information and does not use personal information for cross-app tracking.
The app does not access contacts, photos, precise location, health information or the device camera. Standard diagnostic information may still be generated by Android, iOS or the device. Any independent logging or monitoring by configured operator services is governed by the operator’s arrangements.
Children’s privacy
TaxiApps RTC is intended for authorised business users working with taxi and private-hire operators. It is not directed at children. If TaxiApps learns that a child’s personal information was supplied directly without an appropriate basis, it will take reasonable steps to address the matter.
UK GDPR rights
Subject to applicable conditions and exemptions, you may have rights to be informed, access personal information, correct inaccurate information, request erasure or restriction, object to processing based on legitimate interests, receive certain information in a portable format, and withdraw consent where it is relied upon. You may also have protections concerning solely automated decisions with legal or similarly significant effects. TaxiApps does not make such decisions through TaxiApps RTC.
How to exercise those rights
- Contact your operator about accounts, calls, recordings, agent status, queues, wallboard data or other information on its systems.
- Contact TaxiApps about information provided directly to TaxiApps, such as a support request or shared diagnostic material.
- Use TaxiApps RTC controls to remove the configuration, or remove the app to delete locally stored configuration and call history.
TaxiApps may request enough information to confirm identity, locate records and understand the request. It will respond within the period required by law. Rights are not absolute, and a reasonable fee or refusal may be permitted for manifestly unfounded or excessive requests.
Complaints to the UK Information Commissioner’s Office
Please first contact the organisation responsible for the relevant processing so it can investigate. You also have the right to complain to the UK Information Commissioner’s Office. Current guidance is available at ico.org.uk/make-a-complaint/.
Changes to this policy
TaxiApps may update this policy when the app, its data practices or legal requirements change. A revised policy will show a new “Last updated” date. Material changes may also be communicated through an appropriate additional notice where required.
Contact details
TaxiApps Privacy Contact
Privacy and support enquiries may be submitted through the TaxiApps contact page.
Contact your operator about information it controls.