Decide what data and dependency you accept before a map of your home becomes useful. “Local processing” and “works without cloud” are separate questions.
Inventory the data path
List the sensors, account requirements, network connection, map storage, image handling, remote-access features, analytics, voice-assistant links, and deletion controls. Read the policy for the robot service, not only the company homepage.
Local processing is not the whole answer
An object-recognition feature may process images on-device while maps, account events, diagnostics, or remote commands still use cloud services. Ask separately where each data class goes.
Camera choices
A front camera may help recognition or remote viewing. If a camera in the home is unacceptable, choose a sensor stack without one rather than relying only on a setting you might forget.
What works offline
Physical start buttons may still launch a whole-home clean while room selection, schedules, maps, updates, or history require the app. Confirm the degraded mode and whether Wi-Fi setup can be skipped.
Account exit plan
Before returning, selling, or recycling a robot, remove schedules, unlink voice assistants, delete maps and recordings, remove the device from the account, and perform the documented reset.
Before you buy
- Camera presence is acceptable
- Map and image storage are explained
- Account deletion path exists
- Core offline behavior is sufficient
- Guest/household access is controllable
- Security updates are part of support policy
- Reset steps are documented
How to use this guide
This guide is a durable editorial framework. It explains system tradeoffs without assigning product scores or pretending a manufacturer claim is a shared lab measurement. For a model-specific decision, record the exact SKU, region, source URL, checked date, and what remains unknown.