Companion Robot Long-Term Storage Checklist: 18 Battery, Data and Restart Tests
How to place a companion robot into storage without damaging its battery, losing account control, exposing private data or creating an unsafe restart months later.
Quick answer
For long-term storage, follow the manufacturer’s battery state-of-charge and temperature limits, shut the robot down fully, isolate approved removable packs, protect joints and sensors from load, and record account, software and warranty status. Store it dry, stable and inaccessible to children. Inspect periodically for heat, odor, swelling, corrosion, pests or leaks, and never restart a damaged battery or robot simply to test whether it still works.
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. Choose storage only after checking alternatives
Decide why the robot is being stored and for how long. A paused subscription, repair delay, household move, deployment, bereavement or product recall may require different treatment. Ask whether vendor service, lawful disposal or transfer is safer than indefinite storage. Record the decision owner and next review date. “Put it in a closet” is not a plan for a heavy connected machine containing batteries, lubricants, private data and parts that may settle under load.
2. Read model-specific battery instructions
Find the exact storage state of charge, temperature, inspection interval and removal procedure specified for the robot and every accessory. Do not copy advice from a phone or unrelated battery chemistry. If the manual is silent, ask the manufacturer in writing. CPSC identifies battery hazards during use, charging and storage. Generic percentages cannot override a product’s battery-management system, warranty conditions or an active recall.
3. Inspect for damage before shutdown
Look for swelling, heat, odor, leakage, cracked housings, crushed cables, loose connectors, abnormal noises, corrosion and charging errors. Review official recall notices for the precise model and pack. Do not store a suspect battery inside a living space or restart it for screenshots. Isolate the area from combustible materials and contact the manufacturer or local hazardous-waste authority for instructions. A storage checklist cannot certify damaged equipment.
4. Export minimal records and preserve account control
Save serial numbers, receipts, warranty coverage, support tickets, installed versions and the owner account’s recovery method. Export only necessary settings; avoid duplicating conversations, recordings and biometric profiles. Confirm that recovery email, multi-factor authentication and passkeys will still be available months later. A robot that is physically protected but tied to an abandoned phone number or expired company email may become impossible to update, erase or transfer safely.
5. Reduce data without destroying needed evidence
Remove unnecessary media, guest profiles, Wi-Fi history and integrations using documented controls. Retain safety logs or dispute evidence separately when justified. If the storage follows an incident, do not factory-reset until the responsible person decides what records must be preserved. Label whether cloud data continues to exist and whether subscriptions remain active. Physical storage does not pause vendor retention, remote access or billing.
6. Install required security updates before isolation
Check the official support channel for security, battery-management and shutdown updates, then apply only those appropriate for the model with a stable power and network connection. Retest emergency stop, sensors and charging afterward. Do not begin a risky feature update simply to have the newest version. Record the final versions and support status so the future owner can determine how far the device has fallen behind before reconnecting it.
7. Use the documented full shutdown
Park the robot safely, disable schedules and automations, sign out where appropriate and follow the manufacturer’s long-term shutdown sequence. Confirm displays, motors, heaters, radios and wake-word functions remain inactive. Sleep mode or a dark screen may continue network traffic and battery drain. Do not disconnect internal batteries, defeat safety interlocks or pull a plug during a firmware operation unless the manual explicitly instructs it.
8. Remove batteries only when designed to be removable
Use the approved release, terminal covers and storage container for removable packs. Label each pack with model, serial, condition and inspection date without covering vents or safety markings. Never dismantle a pack into individual cells, substitute a charger or place loose terminals near metal objects. CPSC warns against separating cells from designed packs because protection can be lost. Internal packs should remain untouched unless qualified service documentation says otherwise.
9. Protect posture, joints and soft materials
Use shipping braces or the manufacturer’s storage pose so weight does not remain on one joint, wheel, cable or soft covering. Avoid improvised ties that compress sensors, pinch wiring or trap moisture. Support heavy sections against tipping and separate detachable accessories. Photograph the correct posture. Months of static load can cause deformation even when electronics remain healthy, and a distorted joint may move unpredictably during the first restart.
10. Choose a dry, stable and secure location
Use a location within the manufacturer’s temperature and humidity range, away from direct sun, heaters, flooding, vibration and combustible clutter. Prevent access by children, pets and unauthorized visitors. Do not seal a warm device in plastic; allow it to cool and dry first. Keep it off bare concrete if the maker warns about condensation or corrosion. A smoke alarm and clear access route are sensible, but they do not make unsafe storage acceptable.
11. Control dust, moisture and pests without blocking safety
Use the recommended breathable cover and caps for exposed ports. Avoid liquids, household sprays, desiccants or pest chemicals that can attack plastics or sensors. Leave required vents unobstructed and keep documentation outside the enclosure. Inspect for nesting, droppings, insects and moisture because stored equipment offers sheltered cavities. If contamination reaches electronics or batteries, seek qualified cleaning guidance rather than powering the robot to warm or dry it.
12. Keep chargers and accessories identifiable
Store approved chargers, docks, keys, braces, tools and manuals together but not pressing against batteries or finishes. Label voltage and ownership, and quarantine incompatible spare chargers. Do not leave a charger energized for months unless the manufacturer explicitly requires a managed storage mode. Future users often choose the connector that fits, yet polarity, voltage, current and communications can differ. An accessory inventory prevents a dangerous guess at restart.
13. Schedule inspections without unnecessary power-ups
Set documented visual inspection dates based on the manufacturer’s guidance. Check temperature, odor, swelling, corrosion, moisture, pests, physical stability and the storage environment. Record findings before moving anything. Do not wake the robot at every inspection merely to see a screen; unnecessary charging cycles and unattended updates create risk. If maintenance charging is required, use the approved process while present and stop on any abnormal condition.
14. Monitor vendor support and recalls while offline
Keep a calendar reminder to review official recall, security and end-of-support notices for the exact product. Save important manuals locally because websites and apps can disappear. If a vendor announces battery replacement, account migration or cloud shutdown, act before the deadline rather than discovering it during restart. NIST’s manufacturer-documentation guidance stresses communicating support capabilities and limitations throughout the product life.
15. Plan the restart as a controlled maintenance event
Before reconnecting power, re-read the manual and stored records, inspect every battery and cable, clear the movement area, locate emergency stop and ensure an adult responsible for the device is present. Use a trusted network and official app version. Do not install months of updates while the robot can roam. Start with power, stop controls and one low-energy movement, then test sensors, privacy controls and charging in a bounded sequence.
16. Revalidate accounts, privacy and network access
Review administrators, paired phones, guest profiles, API tokens, Wi-Fi credentials, cloud retention and subscriptions. Remove accounts that no longer belong and rotate compromised credentials. Verify microphone mute, camera indicators and remote viewing before normal use. A robot stored offline can reappear with outdated trust assumptions, while the household network and vendor platform may have changed substantially. Reconnection should be treated as onboarding a new IoT device.
17. Decide release, repair or disposal after testing
Mark each restart test pass, fail or unknown. Keep the robot restricted when emergency stop, battery health, movement, privacy indicators, software support or account control cannot be verified. Obtain repair estimates and parts availability before repeated experiments. If safe restoration is impractical, follow local electronics and hazardous-battery disposal rules. Never put a lithium-powered device in ordinary trash or conceal a known defect in a sale.
18. Maintain a complete storage record
The final record should include why storage began, dates, battery instructions, physical condition, account owner, software versions, inspections, incidents, restart result and next decision. Store it separately from the robot and protect personal information. This history helps a technician, insurer, buyer or family member distinguish normal aging from damage. More importantly, it prevents the common failure of finding an undocumented machine years later and powering it without knowing its battery, data or support state.
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.