How the Red Taxi Local SMS Sender handles device permissions and SMS data

This policy covers the Red Taxi Local SMS Sender Android app used by taxi operators to send operational SMS messages through a physical Android phone and SIM card connected to their Red Taxi account.

The app is intended for operator-managed devices. It is not a passenger messaging app and it does not provide a public chat service.

After an operator scans the setup QR code, the app stores the API URL, device token, and polling interval in encrypted app storage. It then checks Red Taxi for outbound SMS messages, sends them with Android SmsManager using the phone SIM, and reports whether each message was sent or failed.

The app also sends a heartbeat so the operator dashboard can show whether the Local SMS device is online.

SEND_SMS lets the app send booking, dispatch, and operational SMS messages from the device SIM. This is the core purpose of the app.

CAMERA lets the app scan the setup QR code from the Red Taxi admin dashboard. The camera is used for setup scanning only.

INTERNET and ACCESS_NETWORK_STATE let the app connect to the Red Taxi API, fetch pending outbound messages, report delivery status, and detect network availability.

FOREGROUND_SERVICE and WAKE_LOCK help the app keep its polling and sending work reliable while the device is being used as an operator SMS sender.

POST_NOTIFICATIONS lets the app show status notifications on Android versions that require notification permission.

The app processes the setup token and connection details needed to authenticate the operator-managed device with Red Taxi.

For each outbound SMS, the app may process the recipient phone number, message body, queue identifier, sent or failed status, and technical timestamps needed for dispatch and support records.

The app does not request contacts, location, microphone, photos, files, call logs, or incoming SMS access in the active Local SMS v2 Android app.

Information is used to send operational SMS messages requested by the taxi operator, update the Red Taxi platform with message status, monitor device availability, troubleshoot failures, and protect the messaging service from misuse.

Red Taxi does not use Local SMS message data for advertising profiling and does not sell this information.

Message data may be visible to the taxi operator that controls the Red Taxi account, authorised support users, hosting providers, and technical service providers needed to operate the platform.

SMS queue, status, heartbeat, audit, and support records are kept only for as long as needed for operational, accounting, security, support, legal, or dispute-resolution purposes.

The app stores setup configuration using encrypted app storage and uses authenticated API requests. Operators should keep the device physically secure and revoke or regenerate setup tokens if a device is lost, sold, repaired, or no longer trusted.

The app should be installed only on an operator-managed Android phone that the taxi business has authorised for sending operational SMS messages.

For privacy questions about the Red Taxi Local SMS Sender app, contact support@redtaxi.co.uk. If your request relates to a specific taxi operator or SMS message, include enough detail to identify the record without sending unnecessary sensitive information.