LEGAL · DATA-EXPORT REGISTER · v1.0
Data-export register
LAST UPDATED: 25 October 2026 · VERSION 1.0
What this register is.
This is the register of data structures, data formats and interfaces that Article 26(b) of the EU Data Act (Regulation (EU) 2023/2854) requires, for the export described in Terms of Service Section 15(c). Every customer, on every plan including the free tier, can export the data listed here free of charge, and so can a provider the customer switches to and authorises. We keep this register up to date: a change to any file below is recorded here, with its new schema version, before it takes effect.
The export interface.
In the console, Export all my data produces one ZIP archive containing the files below. The same archive is available by an authenticated, read-only HTTPS request to GET /api/v1/export, using an export key issued from the console on any plan; a customer can issue such a key to the provider it switches to. Encoding is UTF-8; times are ISO 8601 in UTC; identifiers are the numeric IDs the console shows.
Files in the archive (schema eudrclear.export/1).
manifest.json— JSON:schema(the schema version,eudrclear.export/1),generatedAt(when the archive was generated),account(theidandemailof the account it covers), andfiles(one entry per other file in the archive: itspath, its size inbytesand itssha256hash).plots.geojson— GeoJSON (RFC 7946) FeatureCollection, one Feature per registered plot: geometry as a Point, Polygon or MultiPolygon in WGS 84 longitude/latitude (null where the stored coordinates cannot be read as one); propertiesid,name,commodity,geometryType,coordinates(the coordinates exactly as entered),areaHa,country,createdAt.collection-links.json— JSON array, one object per supplier collection link:supplierLabel,commodity,status(pending, submitted, expired),geometryTypeandcoordinatesas the supplier submitted them,submittedAt,createdAt,expiresAt. The link token itself is not exported.screenings.json— JSON array, one object per screening:id,plotId,status,verdict,isDemo,engineVersion(the EUDR Clear engine version),datasetVersions(for a live screening, the Whisp version underopenforis-whispand the time Whisp processed the request, UTC, underprocessedAtUtc; for a demo screening, the demo dataset labels),signals(tree-cover loss by year),summary,inputGeometry,layers,rawResponse(the provider response, verbatim),custodyHash,plotIdentityHash,retainedUntil,createdAt(the analysis time, UTC).packs/<referenceCode>.json— JSON, one file per evidence pack:referenceCode,screeningId,status,content(the pack content as rendered),otsAnchoredAt,createdAt; andpacks/<referenceCode>.ots— the OpenTimestamps proof (binary, OpenTimestamps format) for the pack digest, present once the pack has been anchored. A reference code that is not a plain file name is written aspacks/pack-<id>.jsoninstead.alerts.json— JSON array, one object per monitoring alert:id,plotId,severity,message,isRead,createdAt.account.json— JSON: the accountemailand displayname;subscription(plan, which is free for the free tier, starter49 for Starter, pro149 for Growth or business499 for Scale, the plan names on the pricing page;status;currentPeriodEnd), or null where no plan has been taken out;usage, the counts for the 30 days before the archive was generated, the period the plan limits count (periodStart,periodEnd,plotson the account, completedscreenings,evidencePacks,apiCalls);apiKeys, as metadata only (name,keyPrefix,scopes,createdAt,lastUsedAt,revokedAt; never the secret); andapiUsage, one record per API call (keyPrefix,endpoint,createdAt).
Standards used: GeoJSON (RFC 7946), JSON (RFC 8259), ZIP (APPNOTE 6.3), OpenTimestamps proof format, SHA-256 (FIPS 180-4). A verification lookup for any custody hash or pack reference remains available on the public /verify page.
What is not exported.
As Terms Section 15(c) states, these are exempt because they are internal to the Service and protected as our trade secrets or intellectual property: the engine and its source code; the internal scoring and threshold implementation, beyond the published methodology; other customers' data, including the inputs behind corroboration counts and published aggregates; and security and access logs.
Fees on switching (Art. 29).
Standard service fees are the plan prices on the pricing page: free tier €0; Starter €49, Growth €149 and Scale €499 per month, exclusive of VAT. On switching or exit, we charge no switching or data-egress charges. Standard plan fees apply while the Service runs, including during the transitional period. Monthly plans carry no early-termination penalty; fees prepaid for an annual term are not refunded on an early switch.