Skip to contentErgasa
Robotics & automation

EU Data Act: access to hotel robot telemetry

EU Data Act procurement checks for hotel robot telemetry: access, independent support, GDPR, trade secrets and switching costs.

Dimitris AthanassiadisPublished

Before signing for a connected service robot, a hotel should test whether it can retrieve usable operating records and authorise an independent service provider to receive them[10]. The EU Data Act gives users rights over qualifying data, but buying a robot does not confer unrestricted ownership of every dataset[10]. Regulation (EU) 2023/2854 generally applies from 12 September 2025; its Article 3(1) design obligation covers connected products and related services placed on the market after 12 September 2026[10].

The procurement decision is therefore specific: accept the offer only when the contract identifies the relevant parties, explains what data exists and provides a workable access route. Ask for an export demonstration using a test dataset before acceptance. The recommendations below are procurement analysis, not legal advice or evidence that any particular robot meets the regulation.

What the EU Data Act actually gives the hotel

A hotel established in the EU can qualify as a user through ownership, contractual temporary rights such as rental or leasing, or receipt of a related service[6]. Merely having a robot operate on the premises does not settle that question[6]. An outsourced catering operator might hold the relevant contractual rights instead[6]. The Commission’s January 2026 FAQs distinguish stable rights over the product from simply receiving a service that happens to involve it[6].

Where data is not directly accessible, Article 4 addresses the holder’s obligation to provide readily available product and related-service data, with metadata needed to interpret it[6]. Access must be free to the user, without undue delay, and in a comprehensive, structured, commonly used, machine-readable format[6]. Continuous, real-time access is qualified by relevance and technical feasibility; it is not an unconditional promise for every field[6].

Do not confuse the September 2026 design milestone with a universal retrofit deadline[6]. The FAQs explain that placing on the market concerns each individual unit, not the model family[6]. For a new purchase, request the relevant unit’s placement history and access design[6]. For an older machine, assess the access-on-request rules and available data rather than assuming that age removes every obligation[6].

Classify the records before negotiating access

The starting point is raw and pre-processed data generated through use of the connected product or related service, plus relevant metadata[2]. Highly enriched, inferred or derived information is outside the Chapter II access regime described by the Commission[2]. A supplier’s proprietary prediction is therefore not interchangeable with the underlying sensor measurements[2].

The table is a request list for a hypothetical hotel deployment. It does not assert that these records exist in any manufacturer’s system. Obtain a field-by-field answer, including whether the holder can retrieve each item without disproportionate effort beyond a simple operation. A screenshot showing a daily total does not establish that event records are available.

Candidate record Question to resolve Procurement evidence to request
Mission start, completion and interruption events Are these recorded and retrievable product or related-service data? Sample export, event definitions and timestamp convention
Battery measurements and charging events Which measurements exist, and what do their units mean? Field dictionary, device identifier and sampling interval
Position and obstacle events Are they retrievable, and do they reveal individuals or sensitive locations? Granularity, privacy assessment and access controls
Predicted remaining life or optimisation score Is this derived analytics rather than raw or pre-processed data? Separate explanation of inclusion or exclusion
Camera output Does it function as sensor imagery or as audiovisual content? Purpose, processing architecture and legal assessment

The last distinction matters[6]. The FAQs say audiovisual content is generally excluded, but imagery from cameras acting as sensors can fall within scope[6]. They also explain that privacy-preserving processing does not automatically turn otherwise qualifying data into excluded derived data[6]. Neither “all video is included” nor “all camera data is excluded” is a safe procurement assumption[6].

Name the holder, seller and authorised user

The manufacturer is often the data holder, but it need not be[6]. A related-service provider or another entity can control access, and several holders may be involved[6]. Where only the user can access locally held data and the manufacturer has no access, there may be no separate holder[6]. Identify the actual architecture rather than assigning every obligation to the distributor[6].

Ask the seller, renter or lessor for the Article 3 pre-contract information[11]. Request data types, formats, estimated volumes, generation frequency, storage location, retention and the means of access[11]. A related-service offer needs its own relevant disclosures[11]. Ireland’s competition authority gives a useful plain-language explanation of these access and transparency duties; it is not an authority designation for Greece[11].

Require a contact and escalation route for each holder[10]. State which hotel legal entity is the user, who may request exports and how those rights transfer when the operating company or equipment lease changes[10]. These are proposed contractual controls, not a claim that every hotel has identical statutory rights[10]. Article 7 also contains qualifications for certain smaller manufacturers and service providers; obtain advice if an exemption is asserted[10].

Make independent support possible without promising everything

The hotel can ask for qualifying data to be shared with a third party under Article 5, subject to the regulation’s conditions[2]. The Commission explains that this can support competing aftermarket services, while using the obtained data to develop a competing connected product is prohibited[2]. Designated Digital Markets Act gatekeepers are excluded from this recipient route[2].

User access being free does not mean the recipient can demand every service free of charge[6]. The holder may seek compensation from a business recipient under the applicable rules[6]. Ask a proposed maintenance contractor to distinguish data-access arrangements from its own analysis, integration and repair charges[6]. The EU Data Act does not establish the commercial price of that contractor’s work[6].

Define the recipient’s purpose, permitted fields and onward-sharing controls[2]. Non-EU recipients require separate attention: the Commission explains that the Act does not oblige a holder to share with third parties based outside the EU[2]. Do not treat an overseas support address as proof of an enforceable Article 5 route[2].

For drafting, start from the Commission’s voluntary model terms covering holder-to-user, user-to-recipient and holder-to-recipient relationships[4]. Adapt them to the actual product and parties[4]. Their non-binding status means a completed template is neither a compliance certificate nor a substitute for reviewing the negotiated contract[4].

Keep privacy, trade secrets and safety separate

A mission log can contain personal data if it identifies or can be linked to a worker or guest[6]. The Data Act does not displace the GDPR[6]. Where the hotel is not the data subject, access to personal data requires a valid legal basis; a commercial request alone does not supply it[6]. The Commission’s FAQs expressly explain this interaction[6].

Before enabling exports, have the privacy owner review purposes, recipients and retention against the GDPR.[8] Prefer the least identifying dataset that answers the operational question. Link this work to the hotel’s camera and DPIA procurement review. Neither the presence of a camera nor the use of telemetry alone settles whether a DPIA is required.

Trade-secret protection remains relevant under the Trade Secrets Directive.[9] The Data Act provides safeguards before disclosure and mechanisms for withholding, suspension or exceptional refusal[6]. A blanket “everything is proprietary” statement is not the whole assessment[6]. Request the specific fields, proposed confidentiality measures and written reasons; the relevant authority-notification and challenge procedures also matter[6].

Safety restrictions are a separate issue[2]. The Commission describes conditions linked to legal security requirements and serious adverse effects on people’s health, safety or security[2]. Escalate contested restrictions rather than attempting to bypass the robot’s controls[2]. A right to obtain data should never be treated as permission to alter navigation software or disable a protective function[2].

Price the export and test the exit route

Data access and switching cloud providers are different legal questions[6]. A robot’s hosted dashboard is not automatically proof that every Chapter VI switching provision applies to the entire robotics contract[6]. Determine whether the service is a qualifying data processing service, what data is exportable and which assets the hotel has a right to move[6]. The FAQs discuss both definitions and specific treatment of customised services[6].

For in-scope switching, the ban on switching charges begins on 12 January 2027[6]. It does not make maintenance subscriptions, ordinary service use or all termination liabilities disappear[6]. The FAQs also distinguish switching from parallel use of multiple services, where data-egress costs may still be billed under the applicable rule[6]. Obtain an itemised exit quotation instead of writing “free migration” into the budget[6].

Use a worked scenario with placeholders, not invented market prices. Suppose the hotel changes its maintenance analyst while retaining the robot. List the quoted cost of mapping fields, validating timestamps, implementing authorised access and reviewing personal data. Add any legally applicable holder-to-recipient compensation and contractual support charges. Compare that total with the incumbent’s written offer; leave every unquoted amount explicitly unknown.

Record unavailable data as a decision limitation rather than assigning it an imaginary revenue value. If the hotel cannot reconcile completed missions with paid support incidents, it lacks evidence for that part of its operating model. Incorporate the resulting assumptions into the purchase, lease and robotics-as-a-service comparison. Data portability does not itself demonstrate labour savings, payback or uptime.

A decision checklist before signature

  1. Identify the hotel user, each data holder and the seller’s disclosure responsibilities. Resolve any claimed exemption before acceptance.
  2. Obtain an inventory of qualifying records, exclusions, metadata and retention. Mark unknown fields rather than assuming they exist.
  3. Run a test export through the proposed authorised route. Check identifiers, units, time zones and whether an independent technician can interpret the file.
  4. Approve a defined third-party sharing workflow, including recipient eligibility, purpose, confidentiality and personal-data handling.
  5. Separate statutory access from paid analytics, support and integration. Request written prices for services that remain chargeable.
  6. Test the relevant exit process and document what will remain unavailable. Preserve the signed schedule and sample export with the procurement file.

Hold acceptance if the supplier cannot explain who handles an access request or demonstrate the promised export. This is a recommended purchasing gate, not an automatic legal conclusion against the supplier. For unresolved scope questions, the Commission’s Data Act Legal Helpdesk accepts legal questions through EU Login.[7] The FAQ publication page identifies the version used here; guidance is not binding law.[3]

Questions hotel buyers should ask

Does the hotel own all data because it bought the robot?

No[6]. The access regime concerns qualifying product and related-service data, with conditions and exclusions[6]. It does not transfer every proprietary dataset, algorithm or derived insight to the buyer[6]. First establish the hotel’s user status and the fields involved[6].

Must a supplier provide a real-time API?

Not as an unconditional requirement for every system[6]. Access must meet the applicable format and timing requirements, while continuous real-time access depends on relevance and technical feasibility[6]. Ask the supplier to explain its actual route and demonstrate its suitability for the intended task[6].

Can an independent repair provider receive telemetry?

Potentially, through the user’s Article 5 request or another lawful arrangement[2]. Recipient eligibility, purpose restrictions, trade secrets and personal-data rules still apply[2]. Competing aftermarket services are distinct from developing a competing connected product[2].

Can we demand that all historical records be deleted?

The FAQs state that the Data Act does not establish a general GDPR-style erasure right for non-personal data[6]. Negotiate appropriate deletion and handover arrangements, while checking other retention duties and the rights of previous or subsequent users[6]. Personal-data erasure is a separate GDPR assessment[6].

Does a free export make changing robot suppliers easy?

No[6]. Exporting records does not guarantee compatible software, transferable licences or equivalent robot functions[6]. Separate the legal access entitlement from the technical and commercial work of replacement, and test the proposed destination before relying on it[6].

Notify me when an obligation on the tracker changes.

You'll get one email to confirm. Nothing else. Unsubscribe any time.

← Analysis