# MultiBot Controller App — Privacy Policy

**Effective Date:** 19 August 2026
**Last Updated:** 19 August 2026

## 1. Introduction

Welcome to **MultiBot Controller** (“the App”, “we”, “us”, or “our”).

MultiBot Controller is a mobile application designed to allow users to control compatible electronic devices, robots, Arduino/ESP32 projects, Bluetooth modules, IoT devices, LEDs, RC cars, and other supported hardware.

Your privacy is important to us. This Privacy Policy explains what information the App may access, how that information is used, and how we protect your privacy.

By using MultiBot Controller, you agree to the practices described in this Privacy Policy.

—

## 2. Information We Collect

### 2.1 Personal Information

MultiBot Controller does **not require you to create an account** and does not require you to provide personal information such as:

* Your name
* Home address
* Telephone number
* Email address
* Date of birth
* Contacts
* Photos
* Messages
* Payment information

unless a future feature specifically requires such information and clearly informs you before collecting it.

—

## 3. Bluetooth Information

MultiBot Controller uses Bluetooth and Bluetooth Low Energy (BLE) to communicate with compatible hardware.

Depending on your device and Android version, the App may request Bluetooth-related permissions such as:

* Bluetooth scanning
* Bluetooth connection
* Bluetooth communication

These permissions are required for functions such as:

* Searching for nearby Bluetooth devices
* Finding BLE devices such as HM-10 modules
* Connecting to Bluetooth devices
* Sending commands to connected devices
* Receiving data from connected devices
* Controlling Arduino, ESP32, RC cars, LEDs and other compatible hardware

Bluetooth device information may include a device name, Bluetooth address/identifier, connection status, and technical information required to establish and maintain the connection.

### Important

Bluetooth information is used to provide the App’s device-control functionality.

We do not sell Bluetooth device information to third parties.

—

## 4. Location Permission

On some Android versions, Android may require location-related permission or settings to be enabled when an application performs Bluetooth/BLE scanning.

If MultiBot Controller requests location permission solely because it is required by the Android operating system for Bluetooth functionality, the permission is used to enable the Bluetooth scanning feature.

**MultiBot Controller does not use Bluetooth scanning to determine, track, or monitor your physical location.**

Where Android provides newer Bluetooth permissions that do not require location access, the App will use the appropriate permissions for the supported Android version.

—

## 5. Device and Technical Information

The App may process limited technical information necessary for normal operation, including:

* Android operating system version
* Bluetooth capability and status
* Connected device information
* Bluetooth device name
* Bluetooth device identifier/address where provided by the operating system
* App version
* Connection status
* Technical error information

This information is used to:

* Establish device connections
* Maintain Bluetooth connections
* Diagnose connection problems
* Improve reliability
* Provide the requested device-control functions

—

## 6. Commands and Device Data

MultiBot Controller allows you to send commands to connected hardware.

Examples include commands for:

* LED ON/OFF
* RGB LED control
* RC car movement
* Stop commands
* Text commands
* Smart-home controls
* IoT controls
* Other user-configured hardware commands

Commands are sent to the hardware selected by the user.

The App does not claim ownership of data generated by your connected hardware.

You are responsible for ensuring that the commands you send are appropriate and safe for your equipment.

—

## 7. Wi-Fi and IoT Communication

Certain versions or features of MultiBot Controller may communicate with IoT devices using Wi-Fi or Internet-based protocols such as MQTT.

When an IoT feature is used, the App may communicate with the device or server specified by the user.

Depending on the configuration, information transmitted may include:

* Device commands
* Device status
* Sensor information
* User-configured messages
* MQTT topics
* Connection information

The App only uses such information to provide the IoT functionality requested by the user.

Users should not enter confidential, sensitive, or private information into device commands, MQTT messages, or other fields unless they understand how their configured IoT infrastructure handles that information.

—

## 8. Data Storage

MultiBot Controller may store limited information locally on your device when necessary for App functionality.

For example, the App may remember:

* Previously selected devices
* User preferences
* App settings
* Connection preferences
* User-configured control settings

Such information is stored locally where possible.

The App does not require a cloud account for basic Bluetooth device-control functionality.

—

## 9. Data Sharing

We do not sell or rent your personal information.

MultiBot Controller does not share your personal information with advertisers for advertising purposes.

Information may only be transmitted to third-party services where this is necessary for a feature that you choose to use, or where required by law.

For example, an IoT feature configured by the user may communicate with an external MQTT broker or server.

Such third-party services operate according to their own privacy policies and terms.

—

## 10. Advertising

The current version of MultiBot Controller does not intentionally collect personal information for targeted advertising.

If advertising or advertising-related services are introduced in a future version, this Privacy Policy will be updated to explain the relevant data practices.

—

## 11. Analytics and Crash Reporting

The App may use technical diagnostics or crash-reporting services in future versions to help identify software problems and improve stability.

Where such services are used, the information collected may include technical information such as:

* App version
* Operating system version
* Device model
* Crash information
* Error information
* Performance information

Such information is intended to help us identify and fix technical problems.

—

## 12. Security

We take reasonable measures to protect information processed by MultiBot Controller.

However, no electronic communication or storage system can be guaranteed to be completely secure.

Bluetooth, Wi-Fi, MQTT, Internet connections, Arduino devices, ESP32 devices, and other third-party hardware may have their own security limitations.

You are responsible for securing your own hardware, passwords, Wi-Fi networks, MQTT brokers, servers, and other connected systems.

For IoT applications, we strongly recommend using appropriate authentication, encryption, secure passwords, and secure network configurations.

—

## 13. Third-Party Hardware

MultiBot Controller may be used with hardware manufactured by third parties, including Arduino-compatible boards, ESP32 devices, HM-10 Bluetooth modules, Bluetooth adapters, RC vehicles, LEDs, sensors, and other electronic equipment.

We are not responsible for the privacy or security practices of third-party hardware, firmware, websites, servers, Bluetooth modules, MQTT brokers, or other services.

You should review the privacy and security practices of any third-party service or hardware that you connect to MultiBot Controller.

—

## 14. Children’s Privacy

MultiBot Controller is not intended to knowingly collect personal information from children.

The App does not require users to provide personal information for basic device-control functionality.

Parents or guardians should supervise children when using MultiBot Controller with robots, RC cars, electrical equipment, motors, batteries, or other hardware.

—

## 15. Your Choices

You can control the permissions granted to MultiBot Controller through your Android device settings.

You may:

* Disable Bluetooth permissions
* Disable nearby-device permissions
* Disable other optional permissions
* Remove the App from your device
* Clear the App’s stored data
* Disconnect connected devices

Some App functionality may stop working when required permissions are disabled.

—

## 16. Data Retention and Deletion

MultiBot Controller does not require an online user account for its basic functionality.

Information stored locally by the App can generally be removed by:

1. Removing the relevant saved device or settings within the App, where supported; or
2. Clearing the App’s storage/data through Android settings; or
3. Uninstalling MultiBot Controller.

If a future version introduces accounts or cloud-based services, additional information about account data deletion and retention will be provided in an updated Privacy Policy.

—

## 17. Changes to This Privacy Policy

We may update this Privacy Policy from time to time.

When changes are made, the **Last Updated** date at the top of this page will be updated.

We encourage users to periodically review this Privacy Policy.

Continued use of MultiBot Controller after an updated Privacy Policy becomes effective means that you acknowledge the updated policy.

—

## 18. Contact Us

If you have questions, concerns, or requests regarding this Privacy Policy or MultiBot Controller, please contact us:

**App:** MultiBot Controller
**Developer:** Atheem Inovations limited
**Email:** [atheem.ie@gmail.com](mailto:atheem.ie@gmail.com)
**Website:** https://atheem.ie/

—

## 19. Summary

In simple terms:

**MultiBot Controller is designed primarily to control your own electronic devices.**

We do not need your name, address, contacts, photos, or personal information to provide the basic Bluetooth control functionality.

Bluetooth permissions are required so the App can find and communicate with compatible devices.

If you use Wi-Fi, MQTT, or other Internet-connected features, information may be transmitted to the servers or devices that **you configure**.

We do not sell your personal information.

**Last Updated:** 19 August 2026