# EU Declaration of Conformity

Article 28 of Regulation (EU) 2024/2847 (the Cyber Resilience Act) requires the manufacturer of a product with digital elements to draw up a written EU declaration of conformity stating that the relevant essential requirements of the Regulation have been fulfilled, and to keep that declaration at the disposal of national market surveillance authorities for ten years after the product has been placed on the market.

\
This page is the public location at which the EU declaration of conformity for each released version of Flopsar is made available, as permitted by Article 28(2) of the Regulation. The declaration is issued under the **sole responsibility of Flopsar Technology Sp. z o.o.**

## When a declaration is issued

A single EU declaration of conformity is issued **per product line** — for example, *Flopsar 7* — and covers all versions of that product line placed on the market from its initial release until either:

* the product line is superseded by a new product line (for example, by *Flopsar 8*), or
* a **substantial modification** within the meaning of Article 3(38) of the Regulation occurs within the product line.&#x20;

Routine maintenance releases — including security updates, bug fixes, and feature additions that do not affect the cybersecurity properties for which the product has been assessed or its intended use — do **not** constitute a substantial modification, in line with Recital 60 of the Regulation, and are therefore covered by the existing declaration without needing a new one.&#x20;

The artefacts that **are** produced for every individual release — release notes, the Software Bill of Materials, and, where applicable, security advisories — are published separately and are referenced by the declaration. See Third-party Components & SBOM, Release notes, and Security Advisories.

## Current declarations

| Product line | Declaration covers                                             | Issued              | Signed by               | Document    |
| ------------ | -------------------------------------------------------------- | ------------------- | ----------------------- | ----------- |
| Flopsar 7    | versions 7.0.0 and later within the 7 series, until superseded | `<TODO YYYY-MM-DD>` | `<TODO name, function>` | PDF (PAdES) |

Each declaration is a self-contained PDF document carrying a **qualified electronic signature** as defined by Regulation (EU) No 910/2014 (eIDAS), in the PAdES B-LT or B-LTA profile. The signature can be verified with any eIDAS-conformant signature validator, including the European Commission's Digital Signature Service (DSS) demonstration application.

## What the declaration covers

For each listed version, the declaration states that the product, as placed on the market by Flopsar Technology Sp. z o.o., is in conformity with the applicable essential requirements of Annex I of Regulation (EU) 2024/2847, covering both the secure design and development requirements (Part I) and the vulnerability handling requirements (Part II).&#x20;

Flopsar is classified under the Regulation as a product with digital elements in the **default category** — it is not listed in Annex III or Annex IV. Conformity assessment is therefore performed using **Module A (internal production control)** under Annex VIII, point 1 of the Regulation. No notified body is involved.&#x20;

Each declaration identifies the references that were used to demonstrate conformity. Where harmonised standards published in the Official Journal of the European Union under the Regulation cover a given essential requirement, those standards are listed. Where such harmonised standards have not yet been published, the declaration lists the technical references and internal practices that were applied in their place — for example, ISO/IEC 27034, ISO/IEC 29147, and ISO/IEC 30111 — as permitted by Article 27 of the Regulation.

## How to verify a declaration

To verify a declaration:

1. Download the PDF using the link in the table above.
2. Open it in a PDF reader that supports PAdES signatures (for example, Adobe Acrobat Reader, the open-source eSig DSS demo, or any eIDAS-conformant signature validator).
3. Verify that the signature is valid, the certificate chain is intact, and the signing certificate was issued by a qualified trust service provider listed on the EU Trusted List.
4. Verify that the document content matches the product line you are evaluating; the product line and the range of versions covered are stated in Section 1 of the declaration.
5. For an individual release, cross-check the release manifest published in the release notes against the declaration's Section 1. If a signature does not verify, or the document content does not match the product you are evaluating, please contact `security@flopsar.com` before relying on the declaration.

## Internal review at every release

Although a declaration is not re-issued for every release, the manufacturer performs and documents an internal review at every release within the product line to confirm that no substantial modification has occurred. The outcome of that review is part of the technical documentation retained pursuant to Annex VII and is made available to market surveillance authorities upon request. Where the review concludes that a substantial modification **has** occurred, a revised declaration is issued and the change is recorded in the Substantial Modifications Register above.

## Translations

The declaration is issued in **English**. Where a Member State requires the declaration to be supplied in one or more of its official languages in connection with a specific placing on the market, a translation is made available on request. The English version remains authoritative.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.flopsar.com/7/eu-declaration-of-conformity.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
