Robotic lawn mower and the EU Data Act – request operating data for repairs
Short answer: A user of a connected robotic lawn mower may, subject to the EU Data Act, obtain readily available product data and data from related services. Under certain conditions, the user can ask for the data to be provided to an independent repair workshop. This does not create a general right to new measurements, all proprietary analyses or software source code.
Editorial fact-check: 16 November 2026, Regulation (EU) 2023/2854, Swedish context. General information; not individual legal or technical advice.
Who is covered?
The rules can be relevant where a lawn mower collects information about its use or environment and can communicate that information using a network, Bluetooth or another connection. A conventional mower with no connected data functionality does not automatically qualify. A person or business owning, renting or leasing a qualifying connected product may be the user. The data holder may be the manufacturer or the provider of a related digital service; contractual roles must be checked.
The Data Act has generally applied since 12 September 2025. Article 3(1)'s separate obligation to design connected products for direct access applies to products and related services placed on the market after 12 September 2026. Do not confuse that design duty with access rights under Articles 4 and 5. Check Article 7 exceptions affecting certain smaller manufacturers and service providers.
Which data may be requested?
The question is whether a record is covered product data or related-service data, and whether it is readily available to the data holder. The following are possible questions, not guarantees for every model.
| Possible data | Use | Check |
|---|---|---|
| Operating hours; start and stop events | Service and maintenance history | Whether recorded and readily available |
| Error codes; charging or battery status | Recurring shutdowns | Raw records rather than new analyses |
| Sensor events, alerts and timestamps | Compare operation before and after repairs | Availability and explanatory metadata |
| Location or map data | Investigating particular events | Actual existence, privacy and safety limitations |
| Prediction models or source code | Technical interest | Not automatically covered; distinguish derived analytics and trade secrets from readily available data |
How to request operating data: six steps
- Identify the equipment: manufacturer, model, serial number, account and related application. Never include passwords.
- Identify user and holder: read the agreement, product information and privacy notice. The app provider may differ from the manufacturer.
- Specify the records: for example readily available fault codes and operating events for model X during dates Y–Z, including timestamps and metadata. Avoid an unnecessarily broad demand.
- Name the recipient and purpose: ask for access under Article 4 or specify a workshop for third-party sharing under Article 5.
- Request an appropriate format: structured, commonly used, machine-readable data and metadata. Direct or real-time access depends on the applicable technical conditions.
- Preserve the evidence: request, receipt, delivered files, their format, dates, missing records and reasons for any refusal.
Two realistic situations
Consumer: unexplained stoppages
Suppose a connected mower repeatedly stops with no clear fault message. The owner asks for readily available error codes, charging status and timestamps for the relevant week. If the holder can retrieve those data, they may support a workshop's diagnosis. The request does not replace a statutory consumer claim or warranty.
Property company: independent servicing
A company using a connected mower appoints an independent service provider and requests sharing of relevant operating events. It should define the named recipient, troubleshooting purpose and secure transfer, and assess whether the files include other people's personal data.
Exceptions and safeguards
Holders do not have to generate new records or disclose derived analyses beyond covered data categories. Specific provisions protect personal data, trade secrets and product safety. Trade secrets are not a blanket exception regardless of the Regulation's conditions. Recipients must comply with use restrictions, including restrictions on developing a competing connected product from the data.
If personal data relate to someone other than the requesting user, a suitable GDPR legal basis and other relevant requirements must be assessed. Limit the request to what is necessary and record security measures.
What if the provider refuses or sends only a PDF?
Ask which records exist, which cannot readily be retrieved and which legal basis is claimed for any restriction. Also ask whether format and metadata meet the specific rules for usable, structured and machine-readable data. A PDF is not automatically acceptable or unacceptable. Sweden's Post and Telecom Authority (PTS) accepts Data Act complaints but states that its powers to take action remain limited pending complementary legislation.
Frequently asked questions
Can I demand all the mower's internal logs?
Not automatically. Coverage depends on the relevant readily available product and related-service data and any exceptions.
Can data be sent to an independent workshop?
Yes, Article 5 provides for qualifying sharing at the user's request, subject to conditions including data protection, safety and recipient duties.
What about older mowers?
The general access rules and the Article 3(1) design duty have different application dates. Do not treat access to existing readily available data as identical to a duty to redesign older products.
Primary sources and further reading
- Regulation (EU) 2023/2854, Articles 2–7 and 50.
- European Commission: Data Act explained.
- PTS: Data Act and complaints.
For the broader context, read EU Data Act – data access, contracts and cloud switching. This guide focuses on connected robotic lawn mowers.
Explore the topic
Business guides – contracts, HR, AI & complianceEU Data Act 2026 – data access, contracts and cloud switching
Guide to the EU Data Act 2026: data from connected products, data holders, data recipients, unfair B2B terms, and switching between cloud services.
