We don't collect your data. We don't sell your data. Both CarPotato and HomePotato are local-first - everything runs on your devices. Optional cloud features (MQTT, remote access relay) are transient and don't log content.
The CarPotato Android companion app and all BrenduhNet products are designed to operate entirely locally. No user data is transmitted to BrenduhNet servers, third-party analytics services, or any external infrastructure. Your data lives on your device and nowhere else.
We collect no personal information. The CarPotato app does not require account creation, user registration, email addresses, phone numbers, or any form of personally identifiable information (PII) to function.
Specifically, the app does not collect:
All data generated by the CarPotato app - including relay configurations, channel names, lighting presets, GPS geofence boundaries, convoy data, and user preferences - is stored exclusively on your local device using the app's internal storage.
No data is transmitted to, processed by, or stored on any server operated by BrenduhNet or any third party. There is no cloud component, no backend database, and no server-side processing of any kind.
If you uninstall the app, all locally stored data is permanently deleted by your device's operating system.
The CarPotato app communicates with CarPotato hardware (base unit, CarTot modules, dash displays, and portable remotes) over local wireless protocols including Bluetooth Low Energy (BLE 5.0), WiFi (802.11 b/g/n), and LoRa. These connections are direct, peer-to-peer, and do not route through any external server or cloud service.
The app requires Bluetooth and WiFi permissions solely for the purpose of discovering and communicating with local CarPotato hardware. These permissions are never used to collect location data, scan for nearby devices not belonging to the CarPotato ecosystem, or transmit data to external services.
The app may request location permissions for the following functionality:
You can deny location permissions and the core relay control functionality of the app will continue to work. GPS-dependent features (geofencing, convoy, trail map) will be unavailable without location permissions.
The CarPotato app supports Android Auto for in-vehicle display and voice control. Android Auto integration operates entirely through the local connection between your phone and your vehicle's head unit. No data from the Android Auto session is collected, stored, or transmitted by BrenduhNet.
Voice commands processed through Android Auto are handled by Google's voice recognition services on your device. BrenduhNet does not have access to, store, or process any voice data.
If you use the optional cellular module (SIM800L on CarPotato or HomePotato), the device communicates over the GSM/GPRS cellular network using MQTT (Message Queuing Telemetry Transport) protocol. This requires connecting to an MQTT broker - either a BrenduhNet-hosted broker or a third-party broker you configure yourself.
When using the BrenduhNet MQTT broker, command and state messages are relayed between your device and the mobile app. Messages are transient and are not stored beyond the duration needed for delivery. We do not log message content. The broker processes your device ID, topic subscriptions, and connection metadata (IP address, connection timestamps) for routing purposes only.
DTMF (touch-tone) control operates over standard phone calls between your phone and the cellular module. BrenduhNet has no access to these calls.
You may configure a self-hosted or third-party MQTT broker at any time. When using a third-party broker, that provider's privacy policy governs your data.
HomePotato is our home automation hub. The following applies to HomePotato-specific features. All general principles above (local-first, no tracking, no ads) apply equally.
Home Fry nodes communicate with the HomePotato hub over your local Wi-Fi network or LoRa radio. All communication stays within your local network. No data from Home Fry nodes is transmitted to BrenduhNet or any external service. Node registration, state updates, and automation rules are processed entirely on-device.
HomePotato bridges Zigbee, Z-Wave, and Matter devices. When you pair a third-party smart home device (smart plug, sensor, lock, etc.), the pairing data and device state are stored locally on the HomePotato hub in non-volatile storage. This data is not transmitted externally.
When you use voice assistants (Apple HomeKit, Google Home, Amazon Alexa) via the Matter protocol, your voice commands are processed by the respective platform (Apple, Google, Amazon) according to their privacy policies. HomePotato receives only the resulting device commands - it does not process or store voice recordings.
HomePotato offers optional cloud-assisted remote access via an outbound WebSocket connection to BrenduhNet relay servers. This feature is opt-in and disabled by default.
When enabled, the hub maintains a persistent outbound connection to
relay.brenduhnet.com. The relay server routes commands between the
mobile app and your hub. We process your device ID, connection metadata, and
command payloads for routing purposes. Command payloads are transient and
not logged or stored. You can disable cloud relay at any time, and all
local functionality continues to work without it.
ClimateGuard monitors temperature readings from sensors in your home. All temperature data, zone configurations, thresholds, and event logs are stored locally on the hub. If you enable SMS alerts for temperature breaches, your phone number is stored on the device only and is not transmitted to BrenduhNet.
The BrenduhNet app does not integrate with any third-party analytics, advertising, crash reporting, or tracking services. This includes but is not limited to:
The app contains no ads and includes no tracking code of any kind.
We do not share any data with any third party because we do not collect any data. There is nothing to share, sell, rent, trade, or disclose.
We will never sell user data. We will never monetize user behavior. We will never provide data to advertisers, data brokers, or marketing platforms.
The CarPotato app is a vehicle control tool not directed at children under the age of 13. We do not knowingly collect any information from children. Since we collect no data from any user, there is no mechanism through which children's data could be collected.
Because all data is stored locally on your device and no data is transmitted to external servers, the security of your data is managed by your device's operating system and your own device security practices (screen lock, encryption, etc.).
Local wireless communication between the app and CarPotato hardware uses the security features native to each protocol (BLE pairing, WiFi encryption). We recommend keeping your device and CarPotato firmware updated to benefit from the latest security improvements.
The BrenduhNet app may request the following device permissions:
The app does not request permissions for: camera, microphone, contacts, phone, SMS, storage (external), calendar, or any other sensitive permission category.
If we ever make changes to this privacy policy, the updated policy will be posted at this URL (brenduhnet.com/privacy) with a revised effective date. We will never retroactively change the nature of data collection without clear notice.
Our commitment to local-only, zero-collection architecture is a fundamental design principle - not a temporary policy.
If you have any questions about this privacy policy or BrenduhNet's data practices, contact us at:
Email: info@brenduhnet.com
Web: brenduhnet.com
BrenduhNet
Christopher Aouate & Burton Enloe