Technical register
Data formats and interfaces
This is the technical register required by Article 26 of Regulation (EU) 2023/2854. It describes how your data is structured, in which formats you can take it away, how switching works, and what does not work yet.
It is part of the information you receive before entering into a contract with us, and it is kept current. It covers everything you have sent us and everything the service has produced for you.
1. What a record looks like
These are the fields the export contains, one by one.
Your organisation and account, common to every service
| Organisation | legal name, address, VAT identification number |
|---|---|
| People | email address, assigned role, invitations issued and the state of each |
| Credits | purchases, internal allocations, and one record per operation with date, service and quantity in credits |
| Invoices | the invoices we issued to you |
| Settings | interface language, notification preferences, your organisation logo if you uploaded one |
| Messages | what you sent us from the feedback form, the files attached to it, and our replies |
LabelCheck, one record per analysis
id | the identifier of the analysis |
|---|---|
title | the name you gave it |
lang | the language the analysis was produced in |
score | the result of the check |
report | the full report, as text |
summary | the findings in structured form |
resolved | the findings you marked as resolved |
versions | the history of the versions |
chat | the conversation about the report, when you used it |
created_at, updated_at | creation and last change |
Declarations, one record per declaration
id | the identifier of the declaration |
|---|---|
title | the name you gave it |
markets | the markets it covers |
score | the result |
blocking_open | how many blocking points are still open |
report | the structured report |
summary | the summary in structured form |
documents | the documents it references |
checked | the points you checked |
versions | the history of the versions |
lang | the language |
created_at, updated_at | creation and last change |
2. The formats
| Structured data and findings | JSON | RFC 8259, encoded UTF-8 |
|---|---|---|
| Reports and declarations | Markdown or PDF | CommonMark · ISO 32000 |
| Files you uploaded | unchanged | the format you uploaded them in |
| Dates and times | ISO 8601 | UTC |
| Languages | two-letter codes | ISO 639-1 |
| Markets and countries | two-letter codes | ISO 3166-1 alpha-2 |
| Ingredient names | INCI | Decision (EU) 2019/701 |
3. Open interoperability specifications
The formats above are open, published, and implemented by software we did not write. Nothing in your export needs our software to be read: JSON opens in any tool, Markdown is text, PDF is a published ISO standard.
There is no sector-wide interoperability standard for cosmetic regulatory records: no common schema another compliance tool could import without mapping, and no standard to declare conformity to. We use open formats and stable field names, so that mapping is a short job for whoever receives them, and we answer the technical questions of the provider you choose.
4. How switching works
Ask us in writing at info@cosmetifull.com. The export is free, it is delivered in one go, and it covers every field listed in section 1 of this page. We deliver within 14 working days of the request. You can ask at any time, not only when leaving, and as often as you need. On your written instruction we make the same export and the same technical answers available to the provider you have chosen, on equal terms. Your relationship with that provider stays yours: we assist you, we do not act for them. We tell you in advance what does not transfer, so that you can plan around it.
5. What we know does not work yet
The export is delivered on request, not from a button
There is no self-service export in the account today. You can already open and save every report and declaration as PDF, and see the full list of what you have produced; the single complete export goes through a written request and the 14 working days above.
There is no public API for a receiving provider
The provider you choose receives the exported files and can ask us technical questions about structures and formats. There is no machine-to-machine interface for them yet.
Attachments to declarations are not retained
You can attach supporting documents to a readiness check, and they count as your assertion that the document exists: their content is never passed to the model, and no attached file is kept, so there is nothing under this heading to export. If retention becomes active, attached files are part of the export in the format you uploaded them in.
Consumption is exported in credits, not in internal units
One record per operation, with date and service. Credits are the unit of the contract. The internal measurement we use to price our own costs is not a record of anything you produced, and it is not part of the export.
Our regulatory knowledge base is not exportable
The rules, the analysis models and the platform are ours. What is yours is everything you sent us and everything the service produced for you, and that is what you take away.
6. Changes to this page
When a limitation above is closed, the line changes with it, and if a new one appears you find it listed alongside the others.