You are signed in. Your saved cloud workspace is held and has not been opened or changed. This desk uses only records saved for this account in this browser. Contact support for help with the saved cloud copy.
Regulation (EU) 2023/1115
Due diligence, product by product.
Collect, assess, mitigate, build the statement, keep the records. Everything stays on this device until you file.
Your products
| Product | HS | Reading | Next step |
|---|
New here? Start with New product, then add its plots and the documents behind them. Your company details go under Your company, once for every product. Each step says what is still missing.
Your company
Who you are and what you declare yourself to be, filled in once for every product. The regulation asks the operator to know its role and size (Art. 2, Art. 4); this page records the declaration and derives what follows from it. It does not decide either for you.
Operator
Declaration
Whisp screening of arriving plots
Enrolled phones · the reader roster
Optional: the phones whose sealed field records this desk treats as its own capture points. A reply on the Collect tab offers its phone with one click; a phone that is lost is revoked here. Two devices in one room? Phone sync shows they were together; it does not locate a plot.
More about enrolment
Phones are named by key hash — the SHA-256 of the phone's signing key, which is the device id in every record it seals. Enrolment is your policy: it is written into no field record and proves nothing about the phone. Enrolling a phone whose public key this desk holds also seals an enrolment record (S58) on this desk, signed by this browser's key — the phone's records sealed after it read as sealed after the enrolment, and the ones already here are named in it. Who held the phone is not said by any of it.
Reader policy
The thresholds this desk applies when it reads a chain. Pre-selected to the profile's defaults; change if your policy differs. They are digested into the roster record so an auditor can see what was applied.
What this page does not do
It does not make the legal determination. It does not decide your role or your size class; you declare them and the page records the consequence. It does not score deforestation from satellites. It does not file until the Information System adapter is enabled. You remain the operator who files and who is responsible.
Where the data lives
On this device, in this browser's storage. When you seal a record, its SHA-256 digest goes to a public randomness beacon and two free timestamp authorities — and a qualified third where this deployment relays to one — through our relay; the record itself does not. A statement reaches the Information System only when you press file, and only once the adapter is enabled for your credentials.
Bring records from the field
Walk the plot on a phone at the site with the farmer's page, stamp it, and add the JSON and its .cts under Plots here — or ask for it from the Collect tab. Evidence files from suppliers can be fingerprinted on the Product tab without ever being uploaded.
To see what a full chain looks like before you have one, open the example chain on the tools page — ten sealed records, loaded in one tap. It stays there: this desk's register is your Art. 12 record, and illustrative data never enters it.
