Companion Robot Home Network Security Checklist: 16 Privacy and Wi-Fi Checks
A practical, source-led checklist for securing a companion robot on home Wi-Fi, reducing unnecessary data exposure, and preserving a recoverable configuration.
Quick answer
Place the companion robot on a separate guest or IoT network when practical, replace every default credential, enable available security updates, disable remote access you do not need, review microphones and cameras, and document how to reset or disconnect the device. Test essential offline controls before trusting it with private spaces or personal conversations.
General consumer-security information, not a guarantee of safety. Follow the manufacturer’s instructions and disconnect the device if physical or privacy risks cannot be controlled.
1. Inventory every connection before changing settings
Write down how the robot connects: Wi-Fi, Ethernet, Bluetooth, cellular service, cloud account, mobile app and any local hub. Include the router name, account owner, device model, firmware version and serial number. This inventory prevents a common mistake: securing the visible app while leaving an older web dashboard, voice service or vendor account active. Photograph labels without publishing serial numbers, and save configuration screenshots in a private folder.
Repeat the inventory whenever an accessory is added. Charging docks, cameras, speakers, smart-home bridges and remote-control tablets can create separate trust paths. A useful diagram shows which component talks directly to the internet and which communications remain inside the home. If the manufacturer does not explain a connection, treat it as unresolved rather than assuming it is harmless.
2. Replace default passwords and remove shared credentials
CISA repeatedly advises organisations and consumers to change default credentials because published or reused passwords can provide easy initial access. Apply that principle to the robot, its companion app, local dashboard and router. Use a unique passphrase for each account and store it in a reputable password manager. Do not reuse the household Wi-Fi password as the robot account password.
Check whether previous installers, family members or sellers still have access. Remove accounts that are no longer needed and review recovery email addresses and phone numbers. If the device offers multi-factor authentication, enable it for the cloud account. A password change is incomplete when an old session, API key or invited user remains authorised.
3. Put the robot on a separate network when practical
A guest or dedicated IoT network can reduce the number of household devices directly reachable from the robot. The goal is not to make the robot untrusted by definition; it is to limit unnecessary paths to laptops, storage devices and work systems. Use router documentation to confirm whether guest clients are isolated from the main network and whether essential local controls still work.
Do not create isolation blindly. Some robots need local discovery from a phone or hub, and a misconfigured guest network can break safety-related controls. Test movement limits, stop commands, updates and charging after segmentation. If a feature fails, document the exact dependency and allow only what is necessary instead of restoring broad access without analysis.
4. Update firmware and applications from official channels
Install security and stability updates offered through the manufacturer’s documented app or support process. CISA’s baseline guidance emphasises regular updates and automated patching where suitable. Before updating, record the current version, charge the device, preserve settings and read the release notes. Avoid firmware files from forums, mirrors or messages that cannot be verified.
Automatic updates reduce delay but can change behaviour. Decide whether the robot should update immediately or during a supervised window, based on vendor options and the device’s role. After installation, verify that privacy settings, local controls, paired devices and emergency-stop functions remain as expected. A version number alone is not proof that every component updated.
5. Disable remote access that the household does not use
Remote viewing, telepresence and vendor support tunnels can be useful, but every enabled service expands the access surface. Turn off internet-facing control when it is not part of the real use case. Check separate toggles for cameras, microphones, location history, notifications and remote wake. A disabled mobile notification does not necessarily disable the underlying upload.
If remote access is needed, define who may use it, from which accounts and for what purpose. Review login history where available and set alerts for new devices. Test revocation by removing a spare account and confirming that access actually stops. Never rely on a household agreement alone when the application still grants technical permission.
6. Treat microphones and cameras as sensitive sensors
Identify every camera, microphone and proximity sensor, including those in a dock or paired tablet. Check whether indicators are hardware-controlled or merely software icons. Position the robot so that private documents, bathrooms, bedrooms and neighbouring property are not captured unnecessarily. Physical covers or power isolation may be appropriate when supported safely.
Review how recordings are started, stored, transmitted and deleted. Distinguish live processing from saved clips and cloud analysis. If the vendor’s explanation is vague, reduce exposure: disable optional recording, restrict rooms and avoid sensitive conversations nearby. Consent matters for visitors and household members even when the device is legal to own.
7. Minimise cloud history and optional analytics
Open the account privacy dashboard and look for voice history, video clips, diagnostics, location information, interaction logs and model-improvement programmes. Disable optional collection that does not provide a feature you value. Where deletion controls exist, test them on a noncritical record and confirm whether the action affects local and cloud copies.
Data minimisation also means avoiding unnecessary profile details. A nickname may be sufficient where a legal name, birthday or detailed biography is optional. Do not upload contact books or photographs merely to complete setup. Read retention statements carefully: deleting an app from a phone does not automatically delete the vendor account or stored history.
8. Verify encryption and certificate warnings without bypassing them
Use the official application and an updated browser for any local dashboard. If a certificate warning appears on an internet service, stop and verify the address through the manufacturer instead of clicking through automatically. Local devices sometimes use self-signed certificates, but that explanation must come from documentation rather than guesswork.
Avoid exposing a local dashboard by forwarding router ports. Universal Plug and Play can create mappings automatically, so review the router’s active port-forwarding and UPnP lists. Remove entries that are not required and retest normal operation. A cloud relay may still exist even when no port is open, which is why the account and network checks complement each other.
9. Secure the phone or tablet that controls the robot
The controller device is often the most powerful credential. Protect it with screen lock, current operating-system updates and a secure account. Review application permissions for camera, microphone, nearby devices, location and local network access. Grant only permissions needed for features that are actually used, while recognising that denying a required safety permission may break control.
Do not leave an unlocked control tablet in a shared area with administrator access. Create separate household profiles if the product supports them, and keep owner-level settings restricted. When replacing a phone, sign out of the old device, remove it from the vendor account and erase it securely. Test that the retired controller can no longer connect.
10. Build a safe offline and outage plan
Disconnect the internet briefly during a supervised test and observe what continues working. Confirm how to stop movement, mute sensors, return the robot to a safe position and power it down without cloud access. Document these steps where household members can find them. The objective is controlled degradation, not an unsupervised stress test.
Plan for router replacement, vendor outage and account lockout. Keep support contacts, proof of purchase and recovery codes offline. If essential controls disappear when the cloud is unavailable, decide whether the robot should remain powered during an outage. Never assume that a companion device will fail in a harmless state without testing its documented behaviour.
11. Review logs and unexpected network behaviour
Use account history, router device lists and vendor diagnostics to establish a normal baseline. Look for new sign-ins, unknown paired devices, repeated authentication failures, unexpected remote sessions or a device that transfers substantial data while idle. A single large update may be legitimate, so investigate context before declaring compromise.
When something is unexplained, preserve timestamps and screenshots, disconnect remote access if safe, and contact the manufacturer through an official channel. Avoid factory-resetting immediately if evidence may be needed, but prioritise physical safety. Consumer router statistics are indicators, not forensic proof; classify the result as unresolved until a credible explanation is obtained.
12. Prepare a documented reset, sale or disposal process
Before selling, returning or disposing of the robot, remove personal media, unlink household accounts, revoke app sessions and follow the manufacturer’s factory-reset process. Also remove the device from the router, voice assistants and smart-home platforms. Keep a record of the reset confirmation without retaining the buyer’s information.
A factory reset may not delete cloud records automatically. Close or clean the associated account separately and verify subscription cancellation. Remove storage cards and inspect accessories for cached data. If the product is transferred, give the new owner public setup documentation rather than your passwords, recovery codes or old configuration backup.
13. Recheck security after repairs or support sessions
A repair centre may replace a mainboard, reset firmware or ask for diagnostic access. Before service, back up necessary settings, minimise stored personal data and document the device state. After return, inspect the serial number and firmware, change credentials, review paired accounts and repeat the network inventory.
Remote support should be time-limited and supervised where possible. Ask what tool will be used, when access ends and what logs remain. Revoke permissions after the session rather than assuming the technician disconnected permanently. If the vendor cannot explain persistent access, keep the robot isolated while seeking a formal answer.
14. Use a quarterly review instead of a one-time setup
Set a recurring household review every few months to check firmware, authorised users, cloud history, router placement and privacy settings. Vendors add features, routers are replaced and household members change. A secure configuration on purchase day can quietly become obsolete when a new integration is enabled.
Record the review date and unresolved questions. The checklist is complete only when exceptions are visible: a required cloud dependency, an account without multi-factor authentication, or a sensor that cannot be disabled. Transparent limitations support better decisions than a blanket claim that the robot is fully secure.
Primary sources and limits
This evergreen guide applies general cyber-hygiene principles to companion robots. Product-specific instructions from the manufacturer remain authoritative, and no checklist can guarantee that a connected device is invulnerable.