AzDeck Privacy Policy

Effective date: June 17, 2026

This Privacy Policy explains how AzDeck handles information when you use the AzDeck mobile application. AzDeck is a robot controller app that lets users create control profiles and connect to their own devices over local network connections, WebSocket, Bluetooth Low Energy, or Classic Bluetooth.

Developer and Contact

Developer: Aztechell
Privacy contact: aztechell@gmail.com

Data We Handle

AzDeck does not create user accounts and does not collect personal information for the developer. The app may process the following information locally on your device to provide its robot control features:

Permissions

AzDeck requests only the permissions needed for app functionality:

How Data Is Used

Data handled by AzDeck is used to save your controller profiles, discover nearby compatible devices, connect to devices you select, send control commands, and display incoming telemetry or status data.

Data Sharing and Sale

AzDeck does not sell user data. AzDeck does not share user data with the developer, advertising networks, analytics providers, or other third parties. Communication data is sent only to the device or network endpoint that you choose in the app.

Data Storage, Retention, and Deletion

AzDeck stores profiles and settings locally on your device. They remain there until you edit or delete them, clear the app's data, or uninstall the app. Exported profile files are stored only where you choose to save them.

Security

AzDeck relies on Android platform protections for local app storage and runtime permissions. Connections to robots or devices are controlled by the transport you choose. If you connect to a device over an unencrypted local network protocol, the connection security depends on your local network and device configuration.

Children's Privacy

AzDeck is not directed to children and does not knowingly collect personal information from children.

Changes to This Policy

This policy may be updated when AzDeck's functionality changes. Updates will be posted on this page with a revised effective date.