Home Robot Mapping Data in 2026: Why Map Features and Policy Scope Are Not the Same

verification)

When buyers compare robot vacuums, they usually compare suction, dock features,

and obstacle avoidance. But mapping features can also change your data

footprint.

The key point: a robot can offer strong mapping convenience while policy text

still differs on what map-adjacent data is collected, where it is processed, and

which controls you can use. Treat mapping quality and policy scope as separate

checks.

Source table (primary sources)

What policy text currently says

1) iRobot: policy text explicitly references floorplan and room-name data, with map-data controls in app settings

In iRobot’s privacy policy (Last Updated: November 6, 2024), iRobot says

smart-technology devices may collect “device environment” information including

robot movement, floorplan, room names, and object/floor-type context.

The same policy says users can choose, through app settings, not to transmit map

data.

Practical takeaway: iRobot policy text describes map-adjacent collection

categories and an explicit map-data transmission control path.

2) Roborock: app policy documents room-name handling and points to device-level privacy terms for detailed device-data collection

In the Roborock App Privacy Policy (Last Updated and Effective Date: February 1,

2026), Roborock says the app can display self-edited device names and lets users

manage room names.

The same policy states that detailed collection from linked devices is described

in the privacy policy corresponding to each device.

Practical takeaway: Roborock’s app-level policy establishes account/app-side

handling (including room-name management) while directing users to device-level

policy text for full device-data detail.

3) ECOVACS: policy text explicitly includes work-environment maps and, where applicable, vision/audio data categories

In the ECOVACS HOME Privacy Policy (Last Updated and Effective Date:

2025.11.24), ECOVACS says data collected by paired devices can include

working-environment 2D/3D maps, operational logs/status data, and (if

applicable) voice/audio and photos/videos from vision-sensor features.

The policy also describes that the actual categories collected depend on the

product functions used and user settings.

Practical takeaway: ECOVACS policy text is explicit that map data can be part of

paired-device processing, and that some model features can add additional

in-home media signals.

Why this matters before purchase and setup

Useful internal pages while comparing mapping convenience versus data-handling

scope:

• Robots: iRobot Roomba j9+,

Roborock Saros Z70,

ECOVACS DEEBOT X8 Pro Omni

• Manufacturers: iRobot,

Roborock, ECOVACS

• Components: Camera,

Microphone, Wi‑Fi

• Country context: USA, China

7-step map-data verification workflow

1. Confirm policy scope first (app policy, device policy, and region-specific

variant if present).

1. Identify exactly which map-related categories are named (floorplan, room

names, environment map, obstacle media).

1. Check whether map-data transmission controls are documented in settings and

verify those controls in-app.

1. Verify whether advanced features (remote viewing, voice systems, obstacle

snapshots) are opt-in, default-on, or model-limited.

1. Record the policy “last updated/effective” date before setup.
2. After first mapping run, review account and privacy settings again before

enabling sharing/invitations.

1. Keep a short audit note (date, model, settings changed, policy URLs) for

future support or deletion requests.

Bottom line for buyers

The safest buyer mindset is simple: treat “good mapping” and “map-data scope” as

two separate decisions.

A robot can navigate well and still differ significantly in what policy text

says about map-adjacent data. In the current iRobot, Roborock, and ECOVACS

policy materials reviewed here, scope is not described in exactly the same way.

iRobot explicitly names floorplan and room-name categories and also documents

map-data transmission controls. Roborock’s app-level policy includes room-name

management but points users to device-level privacy policies for full

device-data specifics. ECOVACS explicitly lists working-environment map

categories and, for applicable models, additional voice/vision data categories.

For buyers, this means the right pre-check is not “Which brand has maps?” but

“Which policy layers document which data categories, and what controls are

actually available in my model/app region?”

If you care about privacy and long-term support, verify policy scope before

pairing, verify settings right after first setup, and keep a simple record of

what you enabled. That reduces guesswork if you later need support escalation,

account migration, or data-deletion requests.

Sources & References

• iRobot Privacy Policy: https://www.irobot.com/en_US/legal/privacy-policy.html (accessed 2026-03-10)
• Roborock App Privacy Policy: https://files.roborock.com/iot/doc/os/privacy/latest/en.html (accessed 2026-03-10)
• ECOVACS HOME Privacy Policy: https://gl-us-wap.ecovacs.com/content/agreementNewest/PRIVACY/US/DEFAULT (accessed 2026-03-10)

Reverification note

This is a time-sensitive policy topic. Re-check all cited policy URLs after

major app updates or policy-date changes before relying on the same

data-handling assumptions.