This Privacy Policy describes how AUR (Home IoT) ("we", "us", "our", or "App") respects and protects your privacy. Our primary commitment is that AUR is designed as an offline-first, local-control application. We do not operate external cloud databases to track, harvest, or sell your personal data.
1. Information Handled by the App
A. Local Bluetooth & HID Input Commands
- Bluetooth Keyboard & Trackpad Reports: When you use the Pro Remote to control your PC, Mac, or TV, keystrokes, trackpad coordinates, and clicks are formatted locally as standard Bluetooth HID reports and transmitted directly to your paired computer over offline Bluetooth.
- Zero Keystroke Logging: We do not log, store, or transmit your typed keystrokes, passwords, or mouse movements to any remote server.
B. Local Remote Canvas & Device Configurations
- Custom canvas button configurations, button modes, commands, and target device IDs are saved locally on your phone using Android's Room SQLite database (`RoomRepository`).
- Bluetooth paired device MAC addresses and custom macro shortcuts stay 100% local on your device.
C. Smart Home & Sensor Data
- BLE UART and MQTT telemetry readings (temperature, humidity, power consumption) are stored locally in Room DB for real-time visualization.
2. Android App Permissions & Purpose
AUR requests only necessary system permissions required to perform core hardware functions:
- BLUETOOTH_CONNECT, BLUETOOTH_SCAN, BLUETOOTH_ADVERTISE: Required to scan for nearby Bluetooth LE smart devices, pair with host PCs, and manage the Bluetooth HID peripheral role.
- CAMERA (Beta/Dev Only): Optional permission requested only when using the experimental AI Air Mouse gesture tracker. Camera frames are processed strictly in real time on-device via MediaPipe and are never recorded or saved.
- FOREGROUND_SERVICE: Required to maintain a stable Bluetooth HID proxy connection when running in the background or with the screen turned off.
3. Local Storage & Security
- Local-Only Storage: All user preferences, macro shortcuts, and custom remote canvas buttons remain exclusively on your device.
- Device Encryption: Stored data is protected by Android's native file system encryption when device lock/encryption is enabled on your phone.
4. Third-Party Services & Monetization
AUR integrates trusted third-party SDKs for billing and advertisement services. These third parties collect data according to their own privacy policies:
A. Google Play Billing Library
Used to handle secure one-time in-app purchases (such as Lifetime Pro access). We do not collect, process, or store your credit card or financial payment details. All transactions are securely managed by Google Play Store.
Privacy Policy: Google Privacy Policy
B. Google Mobile Ads (AdMob) & User Messaging Platform (UMP)
Used to display banner, interstitial, and optional rewarded video ads (allowing free users to earn extra usage time). AdMob may collect pseudonymous device identifiers (Ad ID), IP address, and general location data for ad delivery, fraud prevention, and frequency capping.
AdMob Privacy Policy: Google Ads Privacy & Terms
5. Data Sharing & Third-Party Transfer
We do not sell, trade, or rent your personal information. We do not share your custom remote configurations, MAC addresses, or IoT device topics with any third party. Direct Bluetooth and MQTT transmissions occur exclusively between your Android device and your selected hardware target.
6. Children's Privacy
AUR does not knowingly collect or solicit personal data from children under the age of 13. If you believe a child has provided us with personal information, please contact us so we can take immediate action.
7. Data Retention & User Control
Because your configurations reside locally on your phone, you retain full control over your data. You can delete all data at any time by uninstalling the app or clearing App Data in your phone's Settings → Apps → AUR → Clear Data.
8. Changes to This Privacy Policy
We may update our Privacy Policy periodically. Any changes will be posted on this page with an updated "Last Updated" date.
9. Contact Us
If you have any questions or concerns regarding this Privacy Policy, please contact us at:
Effective Date
This Privacy Policy is effective as of September 3, 2026.