EU Data Act Product Data Notice: Article 3 Guide for Connected Products (2026)

Last updated: 23 August 2026

If you manufacture, rent, lease, distribute or sell connected products in the European Union, the EU Data Act creates a practical product-information problem that did not exist in the same form a few years ago: customers need specified information about the data a connected product can generate before they enter into the contract.

In practice, many manufacturers have started publishing this information as a Product Data Notice, Data Notice, Product Information Sheet, or similarly named document. The EU Data Act itself does not require companies to use the title “Product Data Notice,” nor does Article 3 prescribe one mandatory PDF or webpage layout. What the law does require is the underlying pre-contractual information.

That distinction matters. The job is not simply to produce a legal-looking PDF. The real task is to identify the relevant product data, describe it accurately, keep the information understandable, and make it available wherever the connected product is offered.

That can include:

• the manufacturer website;
• a product detail page;
• a stable data-information URL;
• distributor documentation;
• marketplace attributes;
• uploaded marketplace documents;
• QR-linked product information.

This guide explains what Article 3 currently requires, what qualifies as a connected product, the small-enterprise exemption, what real manufacturers are publishing, and how marketplaces such as Kaufland, bol and MediaMarktSaturn are turning the Data Act into operational product-data requirements.

Need to create the notice itself? RegCatalog provides a free EU Data Act Product Data Notice Generator designed to structure the core product information before you publish or distribute it.

Important: This guide is informational and is not legal advice. Product scope, enterprise status, contractual roles and sector-specific rules can change the analysis for a particular company or product.

Quick answer: what is an EU Data Act Product Data Notice?

An EU Data Act Product Data Notice is a practical name for the pre-contractual information that sellers, rentors or lessors of connected products may need to provide under Article 3(2) of Regulation (EU) 2023/2854.

For a connected product, Article 3(2) requires at least information about:

1. the type, format and estimated volume of product data the product is capable of generating;
2. whether the product can generate data continuously and in real time;
3. whether data can be stored on the device or on a remote server, including the intended retention period where applicable;
4. how the user can access, retrieve or, where relevant, erase the data, including the technical means, terms of use and quality of service.

The authoritative source is the EU Data Act on EUR-Lex. The European Commission also maintains a useful Data Act explained overview and publishes Data Act implementation FAQs.

The important operational point is that this is pre-contractual information. It needs to be available in a clear and comprehensible manner before the user concludes the relevant purchase, rental or lease contract.

When did the EU Data Act start applying?

The Data Act has applied generally since 12 September 2025.

There is, however, a separate date that is often confused with the Product Data Notice requirement.

Under Article 50, the specific Article 3(1) access-by-design obligation applies to connected products and related services placed on the market after 12 September 2026. Article 3(1) concerns designing connected products and related services so relevant product and related-service data are accessible by default in a structured, commonly used, machine-readable format and, where relevant and technically feasible, directly accessible to the user.

That 2026 date does not mean that every Article 3 transparency obligation begins in September 2026. The Article 3(2) pre-contractual information requirement belongs to the Data Act regime that has already applied since September 2025.

For current dates and the exact legal wording, see Article 50 of Regulation (EU) 2023/2854.

A note on the Digital Omnibus

The European Commission proposed a broader Digital Omnibus in November 2025 that would amend several EU digital laws, including parts of the Data Act. As of August 2026, the relevant legislative procedure is still listed by EUR-Lex as ongoing.

That means manufacturers should distinguish between:

• the law currently in force;
• Commission proposals that may change it later.

For the proposal and current legislative status, see COM(2025) 837 on EUR-Lex and the procedure page.

This guide therefore uses the currently applicable Data Act as its legal baseline and should be reviewed when amendments are adopted.

What counts as a “connected product” under the Data Act?

This is one of the most important questions because “connected product” is a defined legal term.

Article 2(5) defines a connected product as an item that:

• obtains, generates or collects data concerning its use or environment;
• can communicate product data through an electronic communications service, physical connection or on-device access; and
• does not have as its primary function the storage, processing or transmission of data on behalf of a party other than the user.

The Commission's examples include connected cars, health-monitoring devices, smart-home devices, planes, robots and industrial machines. Germany's federal Data Act information resources similarly describe products across infrastructure, vehicles, home equipment, consumer goods, medical devices, agricultural equipment and industrial machinery.

Useful official references include:

• Article 2 definitions on EUR-Lex
• European Commission: Data Act explained
• Bundesnetzagentur: Data access and data use

Typical examples

Depending on their actual functionality, connected products may include:

• smart locks and access-control equipment;
• connected HVAC controllers and thermostats;
• smart appliances;
• industrial sensors;
• agricultural equipment;
• connected pumps and machinery;
• EV charging equipment;
• telematics devices;
• smart lighting;
• wearables;
• connected medical and health devices;
• connected vehicles;
• cameras and certain security equipment.

The legal definition still needs to be applied to the actual product. “Has Wi-Fi” is not a complete scope test, and neither is “contains software.”

What may fall outside the definition?

Products whose primary function is storing, processing or transmitting data for another party can fall outside the connected-product definition. Servers and certain networking infrastructure are common examples used when explaining that boundary.

Similarly, the Data Act distinguishes the connected product from a related service. A related service is a digital service, including software, linked to the product in a way that affects one or more of its functions. The legal test is more specific than simply “the manufacturer also has an app.”

If the scope is uncertain, document the reasoning and obtain appropriate legal advice rather than treating a generic product category as definitive.

What is “product data”?

Article 2(15) defines product data as data generated by use of a connected product that the manufacturer designed to be retrievable through an electronic communications service, physical connection or on-device access by a user, data holder or third party.

The Commission explains that Chapter II can cover raw and pre-processed data generated through use of connected products or related services that are readily available to the data holder. Examples can include sensor measurements such as:

• temperature;
• pressure;
• flow rate;
• pH;
• liquid level;
• position;
• acceleration;
• speed.

Depending on the product, practical manufacturer notices also identify data such as:

• device state changes;
• operating hours;
• battery information;
• component temperatures;
• alarm and fault events;
• configuration values;
• environmental sensor readings;
• maintenance data;
• location information;
• energy or consumption data;
• diagnostics.

The Commission also distinguishes these data from inferred or derived data and from content itself. For example, a connected television may generate data about screen brightness, but the film being watched is not product data merely because it appears on the connected product.

See the Commission's Data Act explained page for the current overview.

What information should a Product Data Notice contain?

For the connected-product side of Article 3(2), a useful Product Data Notice should map clearly to the four required information groups.

1. Type, format and estimated volume of product data

This is more useful when it is concrete than when it says only “usage data may be collected.”

A product-data table could look like this:

The law asks for an estimated volume. Real products do not always generate a fixed amount, so notices often explain what influences the estimate.

For example, MAN's Data Act information explains that estimated volume depends on product configuration and use. Honda's Miimo product information likewise describes product-specific formats and estimated data volumes.

The purpose is not false precision. The purpose is to give the prospective user a meaningful description of the product-data characteristics.

2. Continuous and real-time generation

State explicitly whether the connected product can generate data:

• continuously;
• in real time;
• only on events;
• periodically;
• only when a particular function is used.

This matters because many products do not behave the same way.

For example, Philips Hue's Data Notice describes product data as being generated when events or state changes occur rather than simply saying that everything is continuous. By contrast, industrial or vehicle systems may generate some operational data continuously.

Avoid collapsing “continuous” and “real time” into one vague yes/no statement if the real behavior is more nuanced.

3. Storage and retention

The notice should explain whether data can be stored:

• on-device;
• on an external/remote server;
• in both places;
• only transiently.

Where applicable, state the intended retention period.

Examples of useful descriptions include:

• “Stored locally until the buffer is overwritten”;
• “Stored in the cloud for 30 days”;
• “Retention varies by account configuration”;
• “Not retained remotely by the manufacturer”;
• “Stored while required to provide the contracted service.”

A generic privacy-policy statement such as “we retain data as long as necessary” may not answer the product-specific question clearly enough by itself.

4. Access, retrieval and erasure

Explain how the user can actually obtain the product data.

Possible mechanisms include:

• mobile application;
• customer portal;
• API;
• downloadable file;
• USB/physical interface;
• direct device interface;
• support request;
• manufacturer data-access portal.

Also explain, where relevant:

• how data can be erased;
• the technical means required;
• relevant terms of use;
• quality-of-service information.

The notice should be operational. “Contact us for your rights” is less useful than explaining what the user needs to do and what they should expect.

Product Data Notice vs. privacy notice: they are not the same thing

A frequent mistake is treating the EU Data Act Product Data Notice as another GDPR privacy notice.

They overlap, but they answer different questions.

A privacy notice primarily explains how personal data is processed under data-protection law.

A Data Act notice can concern both personal and non-personal product data and focuses on access to and use of data generated through connected products and related services.

The Commission explicitly states that the Data Act works alongside data-protection rules including the GDPR. If requested product data contain personal data, the GDPR and an appropriate legal basis still matter.

This is why manufacturers such as Signify/Philips explicitly distinguish their Data Notice from their Privacy Notice. See the Philips Hue Data Notice for a practical example.

Do not simply rename an existing privacy policy “Data Act Notice.”

Product Data Notice vs. Related Service Data Notice

Another important distinction is between:

• Article 3(2): connected product pre-contractual information; and
• Article 3(3): related service pre-contractual information.

Article 3(3) contains a broader set of disclosures for related services, including information about product data the prospective data holder expects to obtain, related-service data, storage and retention, prospective data-holder identity, intended data use, sharing with third parties and other matters.

Some manufacturers therefore publish separate documents.

For example:

• EZVIZ publishes a Product Data Notice and a separate Related Service Data Notice.
• Signify publishes generic and specific Data Notices for connected-product and related-service contexts.

For a manufacturer with both hardware and a product-linked digital service, forcing everything into one generic four-line notice may hide material distinctions.

Is there an SME exemption?

Yes, and this is an important qualification.

Article 7 states that the Chapter II obligations do not apply to data generated through use of connected products manufactured or designed, or related services provided, by a microenterprise or small enterprise, subject to conditions relating to partner/linked enterprises and subcontracting.

There is also a transitional provision for enterprises that have qualified as medium-sized for less than one year and for certain connected products for one year after they were placed on the market by a medium-sized enterprise.

Read the exact provision in Article 7 on EUR-Lex.

“Under 50 employees” is not the complete test

For the EU SME definition, the European Commission lists the main small-enterprise thresholds as:

• fewer than 50 staff; and
• annual turnover of no more than €10 million or balance-sheet total of no more than €10 million.

But enterprise relationships matter. A company that belongs to a larger group may have to include data from partner or linked enterprises when determining SME status.

See the Commission's current SME definition.

So do not automatically conclude:

“We have 38 employees, therefore Article 3 does not concern us.”

Corporate structure, financial thresholds, subcontracting and the product's manufacturer/provider can change the analysis.

Who is responsible for providing the pre-contractual information?

For a connected product, Article 3(2) refers to the seller, rentor or lessor, which may be the manufacturer.

This is operationally significant because a manufacturer may create the source information, but the product may be sold by:

• a distributor;
• an ecommerce retailer;
• a marketplace seller;
• a reseller;
• a rental business.

The information still needs to reach the prospective user before contract conclusion.

That is one reason a stable manufacturer URL can be useful: downstream sellers can reference the manufacturer's canonical information instead of reconstructing it themselves.

Real marketplace implementation is already moving in this direction.

How Kaufland implements EU Data Act product information

Kaufland Global Marketplace has a concrete seller workflow for the Data Act.

Its EU Data Act Seller University guidance tells sellers to specify whether a relevant product is affected and, where it is, provide the manufacturer's information URL.

Kaufland documents:

• a “Concerns Data Act” field;
• a “Smart Device Info URL”;
• CSV/XML submission;
• Marketplace Seller API submission;
• product-by-product entry.

For feed integrations, Kaufland currently documents attributes including:

• is_smart_device
• smart_device_manufacturer_information_url

Kaufland also states that if relevant EU Data Act information is not submitted correctly, it reserves the right to deactivate listings.

This illustrates why Product Data Notices are not only a legal-document task. The same source information can become a product-catalogue dependency.

Marketplace schemas can change. Always verify the current Kaufland documentation before hard-coding field IDs or production feeds.

How bol handles connected-item Data Act information

The bol partner platform similarly operationalises the requirement.

Its European Data Act guidance tells sellers to check whether they sell connected items and obtain the relevant product-data information from manufacturers.

For affected new electronics, bol says that when a seller indicates the item collects data, the required product information must be supplied before the item can go online.

bol also publishes an English Data Act information template covering:

• type and format;
• approximate data volume;
• continuous/real-time generation;
• local or external storage;
• retention;
• access;
• sharing;
• deletion;
• terms and quality of service.

The practical lesson for manufacturers is straightforward: a clean, reusable product record can reduce the amount of information a reseller has to chase for each SKU.

How MediaMarktSaturn maps Article 3 into product attributes

MediaMarktSaturn marketplace communications, documented by Lengow, map the Data Act into structured product attributes.

The MediaMarktSaturn EU Data Act update identifies fields for:

• form/type/volume of generated data;
• real-time generation;
• storage;
• retention;
• user accessibility;
• additional Data Act information;
• manufacturer information URL.

The documentation also allows a stable manufacturer link that leads directly to the required information.

Again, this is why a single canonical product-data record is more valuable than a one-off legal PDF: different sales channels can require different representations of the same underlying facts.

What real manufacturers are publishing

There is no single universal layout, but current manufacturer implementations show recurring patterns.

EZVIZ

The EZVIZ Product Data Notice includes:

• definitions;
• product-data type, format and estimated volume;
• continuous/real-time generation;
• retention;
• access/retrieval/erasure;
• contact information.

HIKMICRO

HIKMICRO's Product Data Notice uses a similarly structured approach and explicitly frames the document as information for EU Data Act purposes.

Signify / Philips Hue

The Philips Hue Data Notice provides data format, frequency, volume and generation characteristics and separates Product Data and Related Service Data.

Signify also operates an index of generic Data Notices, demonstrating how a larger portfolio can require both generic and product/system-specific information.

Honda

Honda publishes product information sheets for connected products such as Miimo robotic mowers. Its Miimo HRM1000–4000 product information describes generated data, format, estimated volume, continuous/real-time capability, storage, retention and access.

MAN and Volvo Construction Equipment

Industrial and vehicle manufacturers often require more extensive product-specific explanations.

MAN's Data Act information describes formats and data-volume variability across connected commercial vehicles.

Volvo Construction Equipment publishes pre-contractual Data Notices describing generated product data and how its Data Act information is updated.

The pattern across these examples is important: the wording differs, but the underlying data model is highly repetitive.

Should the notice be a webpage or a PDF?

The Data Act focuses on the information being provided clearly and pre-contractually; it does not prescribe one universal file format for an Article 3(2) notice.

In practice, manufacturers use:

• webpages;
• downloadable PDFs;
• product information sheets;
• general notices plus product-specific annexes.

For most multi-product manufacturers, a stable webpage plus downloadable/portable output has practical advantages.

Benefits of a stable webpage

A stable product-specific URL can:

• be updated without changing every reseller document;
• be linked from marketplace product attributes;
• be indexed internally by distributors;
• show a clear “last updated” date;
• provide version/revision information;
• reduce duplicate copies.

Benefits of PDF

PDF remains useful for:

• distributor packages;
• document-management systems;
• marketplace uploads;
• sales documentation;
• offline evidence.

The strongest practical setup is often not “webpage or PDF.” It is:

one structured source → webpage + PDF + marketplace output

That avoids maintaining multiple independent versions of the same product information.

How to build the notice: a practical workflow

A good process starts with product data, not legal prose.

Step 1: identify the product and scope

Record:

• manufacturer;
• brand;
• product family;
• model;
• SKU/GTIN where useful;
• product URL;
• whether the product appears to meet the connected-product definition;
• which company is the manufacturer/data holder/related-service provider.

If scope is uncertain, flag it for review.

Step 2: inventory generated product data

Work with engineering/product teams to list what the product is capable of generating.

For each data category, capture:

• name;
• description;
• format;
• estimated volume;
• generation frequency;
• whether continuous;
• whether real-time.

Do not ask Legal to invent technical data estimates. The source should usually be engineering, firmware, cloud/backend or product architecture.

Step 3: document storage and retention

For every material category, determine:

• device storage;
• remote/cloud storage;
• transient processing;
• retention;
• configuration-dependent retention.

Make sure the notice reflects the real system rather than a generic corporate policy.

Step 4: document user access

Identify the actual route:

• API;
• app;
• portal;
• device interface;
• downloadable file;
• request process.

Record deletion mechanisms where relevant.

Step 5: separate related-service information where needed

If an app or service meets the Data Act definition of a related service, Article 3(3) can require additional information.

Do not force related-service obligations into a product-only four-field template without reviewing the additional requirements.

Step 6: create the canonical output

Publish a versioned source containing:

• effective/revision date;
• product identification;
• required product-data details;
• access information;
• contact;
• related links.

Use an understandable structure rather than copying regulation text line by line.

Step 7: map the record to sales channels

For each marketplace/distributor:

• identify the required fields;
• determine whether a manufacturer URL is accepted;
• map existing fields to the marketplace schema;
• generate/upload the required document where necessary.

Step 8: assign ownership

Decide who updates the notice when:

• a new SKU launches;
• firmware changes data behavior;
• a cloud service changes retention;
• access mechanisms change;
• a marketplace changes required attributes.

Without ownership, even a well-written initial notice becomes stale.

A Product Data Notice template structure

A practical structure for an Article 3(2)-focused notice could be:

Product identification

• Manufacturer
• Brand
• Product
• Product family
• Model
• SKU/GTIN
• Notice version
• Effective date

1. Product data generated

For each category:

• data type;
• description;
• format;
• estimated volume.

2. Continuous and real-time generation

State:

• continuous: yes/no/conditional;
• real time: yes/no/conditional;
• generation trigger/frequency.

3. Storage and retention

State:

• on-device storage;
• remote storage;
• intended retention where applicable.

4. Access, retrieval and erasure

State:

• access method;
• technical means;
• access URL/interface;
• retrieval/export method;
• erasure method where relevant;
• relevant terms and service conditions.

5. Contact / supporting information

• manufacturer/data-holder contact;
• product support;
• terms;
• related-service notice where applicable;
• privacy notice where personal data are involved.

This structure is deliberately data-first. A manufacturer may need additional information depending on its role, product, related services, other Data Act provisions and sector-specific law.

Common mistakes to avoid

Mistake 1: treating every device with connectivity as automatically in scope

Use the Article 2 definition. Connectivity is relevant, but the primary function and data characteristics matter too.

Mistake 2: treating the small-enterprise exemption as a headcount-only test

The EU SME definition includes financial criteria and group relationships. Article 7 also has conditions around linked/partner enterprises and subcontracting.

Mistake 3: using the privacy policy as the Product Data Notice

GDPR transparency and Data Act product-data transparency are related but distinct.

Mistake 4: saying “JSON” without explaining what data are generated

Article 3 asks for the type as well as the format and estimated volume.

Mistake 5: giving no usable volume estimate

If volume varies, explain the range or the factors controlling it rather than omitting the field.

Mistake 6: saying “data are available on request” without explaining how

Describe the technical/access mechanism and practical path.

Mistake 7: maintaining independent copies everywhere

If website, PDF, Kaufland, bol and distributor documents are edited separately, inconsistencies are likely.

Mistake 8: publishing once and never assigning an owner

Product behavior changes. So do marketplace schemas.

Why this is becoming a product-data problem, not only a legal problem

The Data Act may originate in regulation, but implementation quickly reaches operational systems.

Consider one connected device sold through multiple channels.

The same facts can be needed as:

• a manufacturer Data Notice;
• a PDF;
• a marketplace URL;
• structured attributes;
• a distributor attachment;
• customer-facing product information.

That creates a familiar product-information-management problem:

one source of truth, many outputs

The goal should not be to create five compliance documents. It should be to maintain one reliable product-data record and render it into whatever each channel needs.

This is especially relevant for manufacturers with dozens or hundreds of connected SKUs, where repetitive manual document creation becomes harder to control.

Checklist for manufacturers

Before publishing a Product Data Notice, verify that you can answer:

• Is the item a connected product under Article 2(5)?
• Does Article 7 create an exemption for the relevant manufacturer/provider?
• Have we identified the specific models/SKUs covered by this notice?
• Have engineering/product teams identified the product-data categories?
• Have we documented data formats?
• Have we provided a reasonable estimated volume or explained the variability?
• Have we stated whether generation is continuous?
• Have we stated whether generation is real-time?
• Have we documented local and/or remote storage?
• Have we documented retention where applicable?
• Have we explained how the user accesses/retrieves the data?
• Have we documented erasure where relevant?
• Do we have a separate related-service analysis where required?
• Does the information appear before contract conclusion?
• Is there a stable manufacturer URL that retailers/distributors can reference?
• Can marketplace teams map the notice to Kaufland/bol/MediaMarkt requirements?
• Is there a clear owner for future updates?
• Does the notice state when it was last updated?

Frequently asked questions

Is a “Product Data Notice” specifically required by name under the EU Data Act?

No. Article 3 requires specified information to be provided to prospective users in a clear and comprehensible manner. The regulation does not require companies to title the artifact “Product Data Notice.” That name has become a common practical convention among manufacturers.

What does Article 3(2) require for a connected product?

At minimum, Article 3(2) requires information about the type, format and estimated volume of product data; continuous and real-time generation capability; on-device or remote storage and applicable retention; and the user's access, retrieval and relevant erasure mechanisms, including technical means, terms of use and quality of service.

Does the EU Data Act apply only to consumer smart devices?

No. The Commission explicitly discusses consumer devices as well as industrial and agricultural machinery, connected vehicles, robots and other IoT products. Both business and consumer users can be relevant.

Does the Data Act apply to small manufacturers?

Article 7 contains an exemption for certain micro and small enterprises, subject to conditions involving partner/linked enterprises and subcontracting. Do not assess the exemption using employee count alone; use the EU SME definition and review the full Article 7 conditions.

Did Article 3 start only in September 2026?

No. The Data Act generally applies from 12 September 2025. The separate 12 September 2026 date concerns the Article 3(1) access-by-design obligation for connected products and related services placed on the market after that date.

Can I use one Product Data Notice for an entire product family?

Potentially, if the information is genuinely accurate for every product covered and differences are clearly described. Real manufacturers use both generic/family notices and product-specific notices. When data types, formats, storage or access differ materially between models, product-specific records or annexes are safer and clearer.

Can a manufacturer publish a stable URL instead of a PDF?

Article 3 does not mandate a universal PDF format. Marketplaces such as Kaufland and MediaMarktSaturn explicitly accommodate manufacturer information URLs in their workflows. PDFs can still be useful for distributors or platforms that require document uploads.

Why does Kaufland ask for a Smart Device Info URL?

Kaufland's seller guidance uses the manufacturer URL as a way to associate relevant EU Data Act product information with individual products. Its current documentation includes a “Concerns Data Act” field and “Smart Device Info URL,” with structured feed/API options.

What information does bol require for connected items?

bol's Data Act guidance and template cover core Article 3 information including type/format/volume, real-time or continuous generation, local/remote storage and retention, and how users access, request or delete data. For affected new electronics, bol says the required content must be added before the item goes online after the seller indicates that it collects data.

Is a Product Data Notice the same as a Related Service Data Notice?

No. Article 3(2) addresses pre-contractual information for connected products. Article 3(3) contains additional pre-contractual information requirements for related services. A manufacturer or service provider may need separate or combined documentation depending on the actual product/service arrangement.

Is a Product Data Notice the same as a privacy notice?

No. A privacy notice addresses personal-data processing under privacy/data-protection law. A Data Act notice focuses on product data and related-service data and can concern personal and non-personal data. Both sets of rules can apply at the same time.

Do we need to update an existing notice?

If the underlying facts change, the published information should remain accurate for the product and user. Manufacturers such as EZVIZ, Honda and Volvo explicitly provide last-updated information or describe updating their notices when product or technical circumstances change.

Build the notice from structured product data

For a single product, a well-maintained document may be manageable manually.

For a portfolio, the more scalable approach is to maintain the underlying information as structured data:

Product
  ↓
Generated data categories
  ↓
Format + volume + frequency
  ↓
Storage + retention
  ↓
Access + erasure
  ↓
Canonical product record
  ↓
Website / PDF / QR / marketplace fields / distributor output

That is the workflow RegCatalog is designed to test.

Create a first draft: Use the free EU Data Act Product Data Notice Generator to structure the core Article 3 information for one connected product. The output is informational and should be reviewed against your actual product, enterprise status, contracts and legal obligations before publication.

Primary sources and further reading

For regulatory questions, start with primary sources rather than relying only on summaries:

1. Regulation (EU) 2023/2854 — EU Data Act, EUR-Lex
2. European Commission — Data Act
3. European Commission — Data Act explained
4. European Commission — Data Act FAQs
5. European Commission — SME definition
6. Bundesnetzagentur — Data access and data use
7. Kaufland Global Marketplace — EU Data Act seller guidance
8. bol — European Data Act guidance
9. MediaMarktSaturn marketplace Data Act attributes — documented by Lengow

Practical manufacturer examples

• EZVIZ Product Data Notice
• EZVIZ Related Service Data Notice
• Philips Hue Data Notice
• Signify Data Notices
• Honda Miimo Product Information
• MAN EU Data Act information
• HIKMICRO Product Data Notice

_RegCatalog provides product-data tooling and informational resources. It does not provide legal advice, legal representation, certification, or a guarantee of compliance. Requirements can depend on the product, company structure, contractual roles, sector-specific law and future legislative changes._