Companion Robot Factory Reset Checklist: 18 Data and Account Checks
A source-led checklist for erasing a connected companion robot, removing cloud access, preserving evidence and confirming that personal data is no longer recoverable.
Quick answer
Before resetting a companion robot, inventory its local and cloud data, export only what you truly need, remove payment methods and third-party integrations, then use the manufacturer’s documented reset. Afterward, verify that old accounts, Wi-Fi credentials, recordings, biometric profiles and paired devices cannot reconnect. A screen that says “reset complete” is not proof that vendor-held data was deleted.
This independent guide provides general consumer safety and privacy information. The manufacturer, qualified service provider and relevant authorities control decisions for a specific device.
1. Define the outcome before touching settings
Decide whether the robot will remain in your household, go to repair, be returned, sold, donated or recycled. Those outcomes require different evidence. A reset for troubleshooting may preserve the owner account, while a transfer should remove every personal association. Write down the intended end state, the deadline and who must approve completion. Do not begin because a buyer, courier or support agent is waiting. A rushed reset can destroy warranty evidence without closing cloud access, leaving both the owner and recipient with an ambiguous device.
2. Inventory every place the robot stores data
List the robot, mobile app, web dashboard, removable storage, charging base, paired phone, home assistant, router, cloud backup and support portal. Record which locations may contain conversations, voice clips, camera images, face models, contact lists, routines, credentials, location history and diagnostic logs. NIST notes that IoT risk spans the product and its lifecycle, not only the visible device. Treat “nothing appears on screen” as an observation, not a complete inventory.
3. Separate useful records from intimate content
Keep receipts, serial numbers, warranty terms, safety incidents, repair tickets and configuration notes needed for ownership or a dispute. Avoid copying entire conversation histories or sensor archives merely because export is available. Store the minimal archive encrypted, name its owner and record a deletion date. A backup without a retention decision simply moves the privacy problem to another laptop or cloud account and may later restore obsolete credentials to a clean device.
4. Confirm administrator control
Sign in through the official app or manually typed vendor domain and confirm which account is the true owner or administrator. Review recovery email, telephone number, passkeys, multi-factor authentication and delegated household roles. Remove unknown sessions before resetting. Never accept instructions to share an owner password with a buyer or repairer. If control is disputed or the account cannot be recovered, pause and open a documented vendor support case rather than attempting unofficial firmware or hidden menus.
5. Remove payments, subscriptions and integrations
Cancel or transfer subscriptions according to written terms, remove stored payment methods, revoke API tokens and disconnect smart-home, calendar, messaging and voice-assistant integrations. Check whether cancellation immediately disables a safety or export feature you still need. Save confirmation numbers without storing card data. Factory reset usually affects the hardware; it may not end a recurring charge, delete a cloud workspace or revoke an integration that can still read historical information.
6. Use the manufacturer’s documented reset
Locate the current procedure for the exact model and hardware revision. Read what the reset erases, what survives, whether internet access is required and how long it takes. Photograph the version screen and safe physical condition first. Do not substitute a forum button sequence, remove batteries during erasure or bypass signature checks. If the documented process conflicts with a safety notice or damaged battery condition, stop using the device and obtain model-specific instructions.
7. Keep motion and charging safe during erasure
Place the robot on a stable surface with people, pets and breakable objects outside its movement envelope. Use approved power equipment if the vendor requires external power, and avoid resetting during storms or unstable service. Confirm the emergency-stop path before any reboot. A reset can restart motors, recalibrate joints or return settings to defaults. Data sanitation is not a reason to ignore physical hazards, unusual heat, odors, swelling or damaged cables.
8. Verify local storage after reboot
Complete only the minimum setup needed to inspect the clean state. Search for prior names, profiles, media, networks, schedules, paired accessories and recent activity. Do not reconnect the old account merely to check whether data returns; use an isolated test account if the vendor supports one. Inspect removable cards and companion hubs separately. Record screenshots that contain no new sensitive content. A welcome screen proves little if old Wi-Fi credentials silently reconnect or stored media remains accessible.
9. Verify cloud deletion separately
Open the official account portal from another trusted device. Review retained conversations, media, training data choices, diagnostic history, device list and deletion requests. Submit a specific deletion or closure request when needed and save its reference, scope and expected completion time. The FTC’s consumer guidance distinguishes erasing a device from dealing with account-linked information. If the vendor offers only deactivation, label the cloud state unresolved instead of certifying deletion.
10. Remove the device from networks and paired hardware
Delete the robot from router reservations, guest networks, Bluetooth lists, home automation controllers and mobile-device permissions. Rotate a shared credential if the product exposed it and revoke certificates or local keys where documented. Do not factory-reset the household router as a shortcut. The goal is to ensure the old device identity cannot rejoin or command other equipment, while preserving unrelated services and records.
11. Test recovery and ownership boundaries
Attempt account recovery using the former owner’s normal route without completing any takeover. Confirm that the serial number is released only when the vendor says it is, and that a new owner cannot see old support tickets or profiles. If transfer requires a vendor-side action, obtain written completion. Conversely, keep activation lock enabled until payment and lawful transfer are complete. Privacy and fraud prevention must be balanced rather than handled as one irreversible click.
12. Document failures and uncertain states
Create a dated checklist with each local and cloud location marked cleared, retained, inaccessible or unknown. Include vendor responses, error codes and what was not tested. Quarantine the device when a reset failed, the account remains linked, storage is encrypted but not erased, or the battery is unsafe. Do not repeatedly reset an uncertain device; repeated attempts can remove useful logs while leaving the remote account unchanged.
13. Complete transfer, repair or disposal responsibly
Give a recipient only the documentation and accessories needed for safe setup. For repair, use service mode or a temporary credential instead of the owner password. For disposal, follow local electronics and hazardous-battery rules; do not put a lithium-powered robot in household trash. For resale, disclose unresolved locks, subscriptions, damage and support limits. The final handover record should state what was erased, what the vendor retains and who is responsible next.
How to record the result
Use a dated worksheet with one owner for each unresolved item. Mark every check pass, fail, not applicable or unknown; never convert unknown into pass. Attach the exact model, hardware revision, software version, source links and support references. Keep intimate recordings, passwords and access tokens out of the worksheet. Restrict the robot whenever battery condition, emergency stop, account control, privacy indicators or remote access cannot be verified.
This process does not certify a product or promise that every vendor implements the named controls. Its purpose is to turn vague confidence into an auditable decision and to reveal where model-specific evidence is missing. Recheck after repairs, account transfers, major updates or a change of household.
Evidence boundaries and an independent second review
This checklist can establish that a careful process was followed, but it cannot independently prove how a vendor handles encrypted backups, replicated cloud records, model-training datasets, dormant administrator access or undisclosed hardware behavior. A local screen, a support email and an account dashboard each describe only part of the system. Record which layer produced every piece of evidence and avoid broad conclusions such as “all data is gone” or “the robot is safe” when the check covered only one device, one account or one moment.
Use a second reviewer for any handover, restart or storage decision involving children, shared households, remote operators, damaged batteries, disputed ownership or intimate recordings. The reviewer should be able to reproduce the critical checks from the written record without using the original operator’s memory. Ask that person to confirm the exact model, inspect the physical condition, compare the documented settings with the current interface, test the stop and privacy controls where safe, and identify every unresolved item. Independence matters more than seniority: the purpose is to catch assumptions, missing locations and ambiguous vendor language before the device returns to normal use or leaves the owner’s control.
Close the review with a decision that is narrower than the evidence. “Approved for supervised local testing on an isolated network” is more defensible than “safe for use.” “Local user profiles removed; vendor cloud deletion pending under ticket 123” is more accurate than “factory reset complete.” Name the person who accepts each residual risk, set a deadline for vendor responses, and keep the robot restricted if a safety, account or privacy control remains unknown. If a later update, repair, transfer, battery event or vendor-policy change invalidates the evidence, reopen the checklist instead of treating the old result as permanent.