Skip to content

LEGAL · PRIVACY POLICY · v0.5

Privacy Policy

LAST UPDATED: 25 October 2026 · VERSION 0.5

01 — Controller.

AdverseDays LLC (Wyoming, USA), operating the EUDR Clear service, is the controller for account, billing, website, security and audit data, and for the aggregated publications described in Section 10. For plot and supplier data that a Customer enters or collects through EUDR Clear, the Customer is the controller and we act as its processor under our Data Processing Agreement (Section 04).

Our representatives in the EU and the UK (GDPR and UK GDPR, Article 27). AdverseDays LLC has appointed Euverify as its representative. In the European Union: Euverify Limited, Unit 3D North Point House, North Point Business Park, New Mallow Road, Cork T23 AT2P, Ireland. In the United Kingdom: Euverify Ltd (company number 16146525), 3rd Floor, 86-90 Paul Street, London EC2A 4NE, United Kingdom. You and the data-protection authorities may contact them about our processing of personal data, in addition to or instead of contacting us.

02 — Data we collect.

  • Account data — your email address, collected when you request a sign-in link; a display name is derived from it. No password is ever requested or stored.
  • Billing data — for paid plans: the business name, billing address, VAT identification number and our confirmation of that number, plan and payment status, received through Stripe. We never receive card numbers.
  • Plot data — geolocation coordinates (points or polygons) and, where you enter them, plot names, commodity, and supplier references.
  • Screening evidence — inputs as submitted, the engine and Whisp versions per screening, raw provider responses, and custody hashes.
  • Usage logs — request logs, timestamps, and error records.
  • Messages — contact-form messages and newsletter email addresses.

03 — Plot data can be personal data.

Plot coordinates and supplier names usually describe land, but where they relate to an identifiable natural person — for example a sole trader, smallholder, or individual landowner named as supplier — they are personal data under GDPR Art. 4(1). We treat such data as personal data throughout. We do not enrich, profile, or cross-reference plot data against other sources.

04 — When you are a supplier submitting a location.

If you received a collection link from a buyer and submitted a plot location through it, the buyer is the controller of that submission and we process it on behalf of the buyer, as its processor under the Data Processing Agreement in our Terms, for the buyer's EUDR due-diligence purpose. The collection page shows you the buyer's notice before you submit: who is responsible, who handles your location, how long it is kept, why it is asked, and your rights. We act as an independent controller only for the service's own security and audit records and, unless the buyer has withdrawn its authorisation, for including the screening in the anonymised statistics described in Section 10. Your submission is visible only to the buyer whose link you used; it is never used for marketing and never shared with other buyers. Retention is buyer-controlled: a location the buyer has not screened is deleted when the buyer deletes the collection link or the plot, and collection links that expire are purged after 90 days. A location that was screened becomes part of the buyer's screening evidence and is retained for up to 5 years (Section 09) even if the link or plot is later deleted — that retention is the product's point. To exercise rights over a submission, contact the buyer who sent you the link; for the security and audit records we control, use the contact form.

05 — Data minimisation.

We collect only what the service needs: your email address — the only account attribute the sign-in flow collects — the coordinates needed to run your screenings, and logs kept to security-relevant fields. Supplier names are optional where our intake allows it, and plot data is never used for marketing.

06 — Purposes and lawful bases.

  • Running your account, billing and support — contract (Art. 6(1)(b)). Screening, monitoring and evidence packs over plot and supplier data are carried out for the Customer as its processor (Section 04).
  • Security, fraud prevention, audit log, service reliability — legitimate interests (Art. 6(1)(f)).
  • Publication of k-anonymised aggregates — plot passports, benchmark statistics, and public corroboration counts — legitimate interests (Art. 6(1)(f)). The weighing: the records published are business screening records, reduced to one-way plot identity hashes, verdict classes, counts, and dates, and released only above minimum distinct-operator thresholds (Section 10), so no operator, supplier, or buyer is identifiable; the interest is community-level transparency about how the screened datasets behave across plots and over time, which supports every operator's risk assessment. Because this basis is legitimate interests, you may object (Art. 21; Section 11).
  • Anonymous, consent-gated analytics and newsletter — consent (Art. 6(1)(a)); withdrawable at any time.
  • Keeping screening evidence for the fixed 5-year window — where we act as a Customer's processor, on the Customer's documented instruction, for the Customer's own record-keeping under Regulation (EU) 2023/1115 (Section 04 and our Data Processing Agreement); for the custody hashes and audit records we keep as controller, our legitimate interest in establishing, exercising or defending legal claims (Art. 6(1)(f); Art. 17(3)(e)).
  • Accounting and tax records, including confirming VAT identification numbers — our legitimate interest in meeting the accounting and tax rules that apply to us (Art. 6(1)(f)).

07 — Processors.

We use processors under written data-processing agreements: Resend (delivery of one-time sign-in links, email-address confirmations, monitoring alert emails and contact-form notifications to our staff; EU/US), Stripe (payments — we never receive card numbers; EU/US), Cloudflare (edge delivery, denial-of-service protection and, only if you accept, cookieless web analytics; EU/US), and Amazon Web Services (application hosting and managed MySQL, EU region eu-central-1, Frankfurt, Germany). Processors act on our instructions only. We do not use Customer data, plot data or supplier declarations to train any general-purpose AI model. Separately, plot coordinates (no names or other fields) are sent at screening time to the Whisp API of the Food and Agriculture Organization of the United Nations (FAO), which returns the analysis; FAO is an international organisation that receives the coordinates under its own terms, not as our processor (Section 08). The upstream datasets behind it — Hansen GFC, GLAD, RADD, JRC TMF — are public geospatial datasets and are not processors of personal data.

08 — International transfers.

The application and its database run on Amazon Web Services in the EU (eu-central-1, Frankfurt, Germany); the site and files are delivered through Cloudflare (see our data-location statement). Where personal data is transferred out of the EU/EEA or the UK to Stripe, Resend and Cloudflare (United States: payments, transactional email and edge delivery), or through support access from Costa Rica, where the controller's personnel are located, the transfer relies on the European Commission's Standard Contractual Clauses (Decision 2021/914, with the UK Addendum where applicable) or the recipient's certification under the EU–US Data Privacy Framework. Plot coordinates — no names or other fields — are sent for screening to the Whisp API of the Food and Agriculture Organization of the United Nations (FAO), an international organisation. No adequacy decision covers FAO, and no Standard Contractual Clauses are in place with it; we send coordinates only, and on request we describe the basis for that transfer. We apply transfer-impact assessments where required.

09 — Retention.

  • Account data — for the life of the account; after it ends, for the retrieval period in Terms Section 15(d), then deleted.
  • Screening evidence — 5 years from each screening, on the Customer's instruction, for the Customer's own record-keeping under EUDR Art. 12; the custody hashes and audit records we keep as controller are kept for the same period to establish, exercise or defend legal claims (Art. 17(3)(e) GDPR). This evidence-retention window is fixed: it applies to every plan alike and is neither shortened nor extended by the plan purchased.
  • Screenings produced by the deterministic demo engine — retained under the same 5-year horizon, so that a demo result re-renders to its custody hash.
  • Billing and tax records — for as long as the accounting and tax rules that apply to us require.
  • Error logs (no request logs) — IP addresses are used transiently for rate limiting and are not stored.
  • Leads, contact messages, newsletter — 24 months or until you unsubscribe.

Evidence-pack digests on a public blockchain (OpenTimestamps). When an evidence pack is generated, a derived digest of that pack — the SHA-256 hash of its custody hash and its public reference code — is submitted to public OpenTimestamps calendar servers and anchored into the Bitcoin blockchain, so that the pack's existence at that time can be verified independently of our servers. Only that derived digest is published: no documents, personal data, or other content are submitted, and the digest alone cannot be reversed to reconstruct them. A blockchain entry is public and irreversible — it cannot be edited or deleted by us or anyone else — so an anchored digest remains on the chain permanently even after the underlying evidence reaches the end of its retention period. We disclose this here precisely because it is a one-way publication. An erasure request cannot remove an anchored digest; it removes the underlying evidence at the end of its retention period.

10 — Publication of aggregated screening records.

We publish aggregated, owner-anonymous plot passports (public records addressed by a plot identity hash) and benchmark statistics. Plot passports are published only when at least 3 different operators have screened the plot; benchmark figures are published only in buckets of at least 5 different operators; public corroboration counts on verification pages publish only where at least 3 different operators in total — the record shown plus at least two others — have screened the plot (k-anonymity). Published records are derived from screening outputs — verdict classes, counts, and dates — and never identify the operator, supplier, or buyer behind a screening; plot geometry is reduced to a one-way hash. If you believe a published record about a plot is inaccurate, contact us via the contact form with the plot identity hash and we will correct or withdraw the record where the error can be verified. Screenings of plot and supplier data that we process as a Customer's processor are included only where that Customer has not withdrawn the publication authorisation in our Data Processing Agreement (clause 1.7).

Publication of these aggregates is our own purpose, carried out on the lawful basis of legitimate interests (Section 06). You may object to your screenings being included in future publications: use the contact form and choose "Privacy request". An objection applies from the date we confirm it — your future screenings are then excluded from new and updated plot passports, benchmarks, and corroboration counts; already-published aggregates are k-anonymised and are not rebuilt.

11 — Your rights.

You may request access, rectification, erasure, restriction, portability, and objection; you may withdraw consent for analytics or the newsletter at any time. Use the contact form and choose "Privacy request"; we respond within one month. You may lodge a complaint with your national supervisory authority, or, as applicable, with the UK Information Commissioner's Office (ICO) or the Swiss Federal Data Protection and Information Commissioner (FDPIC).

California residents: California law may apply to some personal information we process (for example, supplier locations or contacts in California). You may request access to or deletion of your personal information and will not be discriminated against for asking. Requests: use the contact form and choose "Privacy request". We do not sell personal information.

12 — Security.

Encryption in transit (TLS), reasonable technical measures, least-privilege admin access, and an append-only audit log of administrative actions. Screening records carry SHA-256 custody hashes so that later alteration is detectable. Custody digests are additionally timestamped on the Bitcoin blockchain via OpenTimestamps — an irreversible publication of the derived hash only, described in Section 09.

13 — Cookies.

The site sets one strictly necessary session cookie (kimi_sid) when you sign in with an email link, and, only with your consent, loads cookieless analytics. See the Cookie Policy.

14 — Children.

The service is B2B and not offered to anyone under 18.

15 — Changes and contact.

We update this policy as the service changes; material changes are announced on this page and by email where required. AdverseDays LLC (operator of the EUDR Clear product) · contact via the contact form.