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)
Source
https://www.irobot.com/en_US/legal/privacy-policy.html
- Type
- Manufacturer privacy policy
- Accessed
- 2026-03-10
Source
https://files.roborock.com/iot/doc/os/privacy/latest/en.html
- Type
- Manufacturer app privacy policy
- Accessed
- 2026-03-10
Source
https://gl-us-wap.ecovacs.com/content/agreementNewest/PRIVACY/US/DEFAULT
- Type
- Manufacturer app/device privacy policy
- Accessed
- 2026-03-10
| Source | Type | Accessed |
|---|---|---|
| https://www.irobot.com/en_US/legal/privacy-policy.html | Manufacturer privacy policy | 2026-03-10 |
| https://files.roborock.com/iot/doc/os/privacy/latest/en.html | Manufacturer app privacy policy | 2026-03-10 |
| https://gl-us-wap.ecovacs.com/content/agreementNewest/PRIVACY/US/DEFAULT | Manufacturer app/device privacy policy | 2026-03-10 |
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
- Confirm policy scope first (app policy, device policy, and region-specific variant if present).
- Identify exactly which map-related categories are named (floorplan, room names, environment map, obstacle media).
- Check whether map-data transmission controls are documented in settings and verify those controls in-app.
- Verify whether advanced features (remote viewing, voice systems, obstacle snapshots) are opt-in, default-on, or model-limited.
- Record the policy “last updated/effective” date before setup.
- After first mapping run, review account and privacy settings again before enabling sharing/invitations.
- Keep a short audit note (date, model, settings changed, policy URLs) for future support or deletion requests.
Frequently Asked Questions
Does map data always include photos or audio?
No. Based on policy text reviewed here, map-related handling and media-related
handling are often separate categories, and some media collection is described
as model- or feature-dependent.
If a policy mentions room names, does that prove detailed floor maps are always uploaded?
Not by itself. Room-name management can appear in app-level policy text without
fully describing device-level map telemetry paths. Check linked device policies
for full scope.
Is “can collect” the same as “always collects”?
No. Policy language often describes possible categories conditioned on feature
use, model capability, app settings, and connectivity state.
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.
Database context
Use this article as a privacy verification workflow
Turn the article into a real verification pass
Home Robot Mapping Data in 2026: Why Map Features and Policy Scope Are Not the Same already points you toward 3 linked robots, 3 manufacturers, 3 components, and 2 countries inside the ui44 database. That matters because strong buyer guidance is easier to apply when you can move immediately from a claim or warning into concrete product pages, manufacturer directories, component explainers, and country-level context instead of treating the article as an isolated opinion piece. The fastest next step is to turn the article into a shortlist workflow: open the linked robot pages, verify which specs are actually published for those models, then compare the surrounding manufacturer and component context before you decide whether the underlying claim changes your buying plan.
For this topic, the useful discipline is to separate the editorial lesson from the catalog evidence. The article gives you the framing, but the robot pages tell you what each product actually ships with today: sensor stack, connectivity methods, listed price, release timing, category, and support-relevant compatibility notes. The manufacturer pages then show whether you are looking at a one-off launch, a broader lineup pattern, or a company that spans multiple categories. That layered workflow reduces the risk of buying on a single marketing phrase or a single support FAQ.
Use the robot pages to confirm which products actually expose cameras, microphones, Wi-Fi, or voice systems, then use the manufacturer pages to decide how much of the privacy question seems product-specific versus brand-wide. On this route cluster, Roomba j9+, Saros Z70, and Deebot X8 Pro Omni form the fastest reality check. If you want a quick working shortlist, open Compare Roomba j9+, Saros Z70, and Deebot X8 Pro Omni next, then keep this article open as the reasoning layer while you compare structured data side by side.
Practical Takeaway
Every robot, manufacturer, category, component, and country reference below resolves to a real ui44 page, keeping the follow-up path grounded in database records rather than generic advice.
Suggested next steps in ui44
- Open Roomba j9+ and note the listed sensors, connectivity methods, and voice stack before you interpret any policy claim.
- Cross-check the wider brand context on iRobot so you can see whether the privacy question touches one model or a broader lineup.
- Use Camera to confirm how common that signal is across the database and which adjacent models share it.
- Keep a short note of which policy layers you checked, which device features are actually present on the robot page, and which items still depend on region- or app-level confirmation.
- Finish with Compare Roomba j9+, Saros Z70, and Deebot X8 Pro Omni so the policy reading sits next to structured product data.
Database context
Robot profiles worth opening next
Use the linked product pages as the evidence layer
The linked robot pages are where this article becomes operational. Instead of asking whether the headline is interesting, use the robot entries to inspect the actual mix of sensors, connectivity options, batteries, pricing, release timing, and stated capabilities attached to the products mentioned in the article. That is the easiest way to see whether the warning or opportunity described here affects one product family, a specific design pattern, or an entire buying lane.
Roomba j9+
iRobot · Cleaning · Available
Roomba j9+ is tracked on ui44 as a available cleaning robot from iRobot. The database currently records a listed price of $899, a release date of 2023-09, Up to 120 minutes (Li-ion) battery life, ~3 hours charging time, and a published stack that includes PrecisionVision Camera (front-facing), Cliff Sensors, and Bump Sensors plus Wi-Fi (2.4 GHz & 5 GHz) and Bluetooth.
For privacy-focused reading, this page matters because it shows the concrete device surface behind the policy discussion. Use it to verify whether Roomba j9+ combines sensors and connectivity in a way that could change the in-home data footprint, and compare the listed capabilities such as 3-Stage Cleaning System, 100% Stronger Power-Lifting Suction, and Dual Multi-Surface Rubber Brushes with any cloud, app, or voice layers, including Amazon Alexa and Google Assistant.
Saros Z70 is tracked on ui44 as a available cleaning robot from Roborock. The database currently records a listed price of $1,299, a release date of 2025-05, 6400 mAh Li-ion (runtime varies by mode) battery life, Not officially disclosed charging time, and a published stack that includes LiDAR (StarSight 2.0), 3D Structured Light, and RGB Camera plus Wi-Fi and Bluetooth.
For privacy-focused reading, this page matters because it shows the concrete device surface behind the policy discussion. Use it to verify whether Saros Z70 combines sensors and connectivity in a way that could change the in-home data footprint, and compare the listed capabilities such as OmniGrip 5-Axis Mechanical Arm, Object Pickup (socks, shoes, small items), and Obstacle Relocation with any cloud, app, or voice layers, including Amazon Alexa and Google Assistant.
Deebot X8 Pro Omni
Ecovacs · Cleaning · Available
Deebot X8 Pro Omni is tracked on ui44 as a available cleaning robot from Ecovacs. The database currently records a listed price of $1,100, a release date of 2025-01, Up to 291 minutes (low power mode) battery life, 4h37min charging time, and a published stack that includes dToF LiDAR (Embedded), AIVI 3D 3.0 Camera, and Dual Structured Light plus Wi-Fi and Bluetooth.
For privacy-focused reading, this page matters because it shows the concrete device surface behind the policy discussion. Use it to verify whether Deebot X8 Pro Omni combines sensors and connectivity in a way that could change the in-home data footprint, and compare the listed capabilities such as 18,000 Pa Suction Power, OZMO Roller Instant Self-Washing Mopping, and ZeroTangle 2.0 Anti-Hair-Wrap with any cloud, app, or voice layers, including YIKO-GPT (built-in LLM assistant) and Amazon Alexa.
Database context
Manufacturer context behind the article
Check whether this is one product story or a broader company pattern
Manufacturer pages add the privacy context that individual product pages cannot show on their own. They help you check whether cameras, microphones, cloud accounts, app controls, and policy assumptions appear across a broader lineup or stay tied to one specific product story.
iRobot
ui44 currently tracks 5 robots from iRobot across 1 category. The current catalog footprint on ui44 includes Roomba j9+, Roomba Combo j5+, Roomba Combo 10 Max.
That wider brand context matters because privacy questions rarely stop at one FAQ page. A manufacturer route helps you see whether the article is centered on one premium model or on a company that has several relevant products and therefore more than one place where the same policy or app assumptions might matter. The category mix here currently points toward Cleaning as the most useful next route if you want to see whether this article reflects a wider pattern inside the brand.
Roborock
ui44 currently tracks 6 robots from Roborock across 2 categorys. The company is grouped under China, and the current catalog footprint on ui44 includes Saros Z70, Saros Rover, Saros 20.
That wider brand context matters because privacy questions rarely stop at one FAQ page. A manufacturer route helps you see whether the article is centered on one premium model or on a company that has several relevant products and therefore more than one place where the same policy or app assumptions might matter. The category mix here currently points toward Cleaning, Lawn & Garden as the most useful next route if you want to see whether this article reflects a wider pattern inside the brand.
Ecovacs
ui44 currently tracks 6 robots from Ecovacs across 2 categorys. The current catalog footprint on ui44 includes Deebot X8 Pro Omni, Deebot X12 OmniCyclone, Deebot T90 Pro Omni.
That wider brand context matters because privacy questions rarely stop at one FAQ page. A manufacturer route helps you see whether the article is centered on one premium model or on a company that has several relevant products and therefore more than one place where the same policy or app assumptions might matter. The category mix here currently points toward Cleaning, Lawn & Garden as the most useful next route if you want to see whether this article reflects a wider pattern inside the brand.
Database context
Broaden the scan without leaving the database
Categories, components, and countries add the wider context
Category framing
Category pages are useful when the article touches a buying pattern that shows up across brands. A category route helps you confirm whether the linked products sit in a narrow niche or whether the same question should be tested across a larger field of alternatives.
Cleaning
The Cleaning category page currently groups 52 tracked robots from 23 manufacturers. ui44 describes this lane as: Robot vacuums, mops, pool cleaners, and window cleaners. The workhorses of home automation that keep your spaces spotless.
That makes the category route a practical follow-up when you want to check whether the products linked in this article are typical for the lane or whether they sit at one edge of the market. Useful starting examples currently include Scuba V3, EcoSurfer S2, AquaSense X.
Component signals to keep in view
Component pages stop a buyer from translating a marketing phrase into a certainty too early. They show how often a sensor, connectivity layer, voice stack, or AI label appears across the database, and they make it easier to ask whether the article is really about one brand or about a shared technology pattern.
Camera
Camera is normalized in ui44 as a sensor signal and is currently attached to 3 tracked robots. The component page also preserves 1 source naming variant so you can see how the same technology is described across manufacturers.
For this article, the value of the component route is that it helps you stop translating a headline claim into certainty too early. Open it when you want to see which robots in the database actually share this signal, starting with Ballie, Built-In Vacuum and Mop Robot BCRI3BX1, Roomba Combo 10 Max.
Microphone
Microphone is normalized in ui44 as a sensor signal and is currently attached to 5 tracked robots. The component page also preserves 1 source naming variant so you can see how the same technology is described across manufacturers.
For this article, the value of the component route is that it helps you stop translating a headline claim into certainty too early. Open it when you want to see which robots in the database actually share this signal, starting with As2, Asimov DIY Kit (Here Be Dragons Edition), MiPA.
Wi-Fi
Wi-Fi is normalized in ui44 as a connectivity signal and is currently attached to 116 tracked robots. The component page also preserves 2 source naming variants so you can see how the same technology is described across manufacturers.
For this article, the value of the component route is that it helps you stop translating a headline claim into certainty too early. Open it when you want to see which robots in the database actually share this signal, starting with 4NE-1, A2 Ultra, A3 AWD Pro.
Country and ecosystem context
Country pages give extra context when support practices, launch sequencing, regulatory posture, or manufacturer mix matter. They are not a substitute for model-level verification, but they do help you see which ecosystems cluster together and which manufacturers sit in the same regional field when you broaden the search beyond the article headline.
USA
The USA route currently groups 19 tracked robots from 13 manufacturers in ui44. That gives you a useful regional lens when the article points toward support practices, launch sequencing, or brand clusters that may share similar ecosystem assumptions.
On the current route, manufacturers like Boston Dynamics, Figure AI, Hello Robot make the page a good way to broaden the scan without losing the regional context that often shapes availability, documentation style, and adjacent alternatives.
China
The China route currently groups 54 tracked robots from 15 manufacturers in ui44. That gives you a useful regional lens when the article points toward support practices, launch sequencing, or brand clusters that may share similar ecosystem assumptions.
On the current route, manufacturers like AGIBOT, Unitree Robotics, Roborock make the page a good way to broaden the scan without losing the regional context that often shapes availability, documentation style, and adjacent alternatives.
Database context
Questions to answer before you move from reading to buying
A follow-up FAQ built from the entities already linked in this article
Frequently Asked Questions
Which page should I open first after reading “Home Robot Mapping Data in 2026: Why Map Features and Policy Scope Are Not the Same”?
Start with Roomba j9+. That gives you a concrete product anchor for the article’s main claim. From there, branch into the manufacturer and component pages so you can tell whether the article is describing one specific model, a repeated brand pattern, or a wider technology issue that affects multiple shortlist options.
How do the manufacturer pages change the buying decision?
iRobot help you zoom out from one article and one product. On ui44 they show lineup breadth, category spread, and the neighboring robots tied to the same company. That context is useful when you are deciding whether a risk belongs to a single model, whether it shows up across a brand’s portfolio, and whether you should keep looking at alternatives before committing.
Why should I open the Camera component page too?
The component route turns a feature mention into a searchable technology pattern. Camera currently maps that signal across 3 tracked robots in ui44, which makes it easier to see whether the article is reacting to one implementation detail or to a broader hardware or software layer shared by many products.
When should I switch from reading to side-by-side comparison?
Move into Compare Roomba j9+, Saros Z70, and Deebot X8 Pro Omni as soon as you understand the article’s main warning or promise. The article explains what to watch for, but the compare view is where you can check whether price, status, battery life, connectivity, sensors, and category fit still make the robot a good match for your own home and budget.
Database context
Where to go next in ui44
Keep the research chain inside the database
If you want to keep going, these follow-on pages give you the cleanest expansion path from article to research session. Open the comparison route first if you are deciding between products today. Open the manufacturer, category, and component routes if you still need to understand the broader pattern behind the claim.
Written by
ui44 Team
Published March 10, 2026
Share this article
Open a plain share link on X or Bluesky. No embeds, no widgets, no cookie baggage.