Skip to content

LEGAL · DATA PROCESSING AGREEMENT · v0.2

Data Processing Agreement

LAST UPDATED: 25 October 2026 · VERSION 0.2

Parties and scope.

This Data Processing Agreement ("DPA") forms part of the EUDR Clear Terms of Service. It binds AdverseDays LLC (Wyoming, USA), operator of the EUDR Clear service ("Processor"), and each Customer ("Controller") for the plot and supplier data that the Controller enters or collects through EUDR Clear — the plots it registers itself and the plot locations its suppliers submit through its collection links (Privacy Policy Section 04). It takes effect when the Controller accepts the Terms of Service; no separate signature is required.

1 — Subject matter, duration, nature, purpose and categories (Art 28(3)).

1.1 Subject matter: processing of personal data contained in the plot and supplier data the Controller enters or collects through EUDR Clear, and in the screening records derived from it.

1.2 Duration: the term of the Controller's account, plus the switching, retrieval and erasure periods in Terms Section 15, plus the evidence-retention period in clause 7.

1.3 Nature: automated screening of plot geolocation against third-party geospatial datasets; storage of submissions, engine and provider versions, raw responses and custody hashes; monitoring re-screening of stored plots; alert and notification emails; append-only audit logging.

1.4 Purpose: for the Controller: its EUDR due-diligence preparation and the operation, security and reliability of the service for the Controller; Processor's own processing is limited to clause 1.7.

1.5 Categories of data subjects: suppliers who are natural persons (for example sole traders, smallholders, individual landowners).

1.6 Categories of personal data: plot coordinates and plot/supplier references relating to identifiable natural persons; submission metadata; user identifiers recorded in the audit trail of the Controller's data. No special-category data is knowingly processed; if the Controller knows a submission contains such data it must say so before submission.

1.7 Processor's own processing. Processor acts as an independent controller, not as processor, for (a) security and audit records of the service and (b) the derivation and publication of the k-anonymised aggregates described in Privacy Policy Section 10. The Controller authorises Processor to derive those aggregates from screenings of the Controller's data; the Controller may withdraw that authorisation at any time through the contact form, with effect for publications made after Processor confirms the withdrawal. Processor's lawful basis and the data subjects' right to object are stated in Privacy Policy Sections 06 and 10.

2 — Processor's obligations.

2.1 Documented instructions only (Art 28(3)(a)). Processor processes personal data only on the Controller's documented instructions — the Terms of Service, this DPA, the console configuration, and written directions — including with regard to transfers to a third country or an international organisation, unless required to do so by Union or Member State law; in that case Processor informs the Controller of that legal requirement before processing, unless that law prohibits such information on important grounds of public interest. Processor informs the Controller without delay if, in its opinion, an instruction infringes the GDPR or other Union or Member State data-protection provisions. Processor does not use Controller personal data to train any general-purpose AI model.

2.2 Confidentiality (Art 28(3)(b)). Persons authorised to process the data have committed themselves to confidentiality or are under an appropriate statutory obligation of confidentiality. Access is least-privilege and logged in an append-only audit log.

2.3 Security (Art 28(3)(c), Art 32). Processor maintains at least: TLS encryption in transit; encryption at rest for stored data volumes; least-privilege administrative access with an append-only audit log of administrative actions; SHA-256 custody hashes over screening inputs and outputs so later alteration is detectable; scoped API keys with console revocation; 15-minute HMAC-signed one-time sign-in links and no stored passwords; transient use of IP addresses for rate limiting without storage.

2.4 Subprocessors (Art 28(2), 28(3)(d), 28(4)). The Controller generally authorises the subprocessors listed below. Each is engaged under a written agreement imposing the same data-protection obligations as this DPA. Current subprocessors (as at 25 October 2026):

  • Amazon Web Services, Inc. — application hosting and managed MySQL; all application data and the screening database — EU region eu-central-1 (Frankfurt, Germany).
  • Cloudflare, Inc. — edge delivery and denial-of-service protection; request data at the edge — EU/US; Standard Contractual Clauses and the EU–US Data Privacy Framework.
  • Resend, Inc. — transactional email: monitoring alert emails and notifications about the Controller's plots — US; Standard Contractual Clauses and the EU–US Data Privacy Framework.

2.4A Disclosure to FAO for screening. Each screening sends plot coordinates only — no names or other fields — to the Whisp API of the Food and Agriculture Organization of the United Nations (FAO), an international organisation, which returns the analysis under its own terms. FAO is a recipient, not a subprocessor of Processor. The Controller instructs Processor to make that disclosure for each screening it requests or schedules. No adequacy decision covers FAO and no Standard Contractual Clauses are in place with it (Privacy Policy Section 08).

2.5 Notice and objection (subprocessor changes). Processor gives at least 30 days' advance notice (email to the account address or console notice) before adding or replacing a subprocessor. The Controller may object on reasonable data-protection grounds within that period; if Processor cannot resolve the objection, the Controller may terminate the affected part of the service without penalty and receives a pro-rata refund of prepaid unused fees.

2.6 Data-subject assistance (Art 28(3)(e)). Processor assists the Controller, taking into account the nature of the processing, with its obligations to respond to data-subject requests under Arts 15–22: requests arriving through collection pages or the service are forwarded to the Controller without delay; Processor supplies exports and rectifications of data the Controller directs, within the response window the Controller must meet. The collection page carries the notice described in Privacy Policy Section 04.

2.7 Assistance with Arts 32–36 (Art 28(3)(f)). Processor assists the Controller with security of processing, breach notification, data-protection impact assessments and prior consultation, using the information it holds about the processing (including this DPA).

2.8 Deletion or return (Art 28(3)(g)) — see clause 7.

2.9 Audits (Art 28(3)(h)) — see clause 8.

3 — Personal-data breach (Art 33(2)).

Processor notifies the Controller of a personal-data breach affecting the Controller's personal data without undue delay after becoming aware of it. Processor aims to notify within 24 hours, and in any event notifies within 72 hours. Where not all information is available at once, Processor gives it in phases without further undue delay. The notification states, where known: the nature of the breach; the categories and approximate number of data subjects and records concerned; the likely consequences; the measures taken or proposed; and a contact point. Processor updates the Controller as information develops and does not publicly name the Controller without the Controller's prior direction.

4 — International transfers.

4.1 The Standard Contractual Clauses in the Annex to Commission Implementing Decision (EU) 2021/914, Module Two (controller to processor), are incorporated into this DPA and apply to the transfer of Controller personal data to Processor, with the Controller as data exporter and Processor as data importer. Clause 7 (docking) applies. Clause 9 Option 2 (general written authorisation) applies, with the 30-day notice in clause 2.5. The optional wording in Clause 11 does not apply. For Clause 13, the competent supervisory authority is the one Clause 13(a) designates for the Controller; where the Controller is established outside the EU and has no representative in it, the Data Protection Commission (Ireland). Under Clauses 17 and 18, the Clauses are governed by Irish law and disputes under them are resolved by the courts of Ireland. Annex I is clause 1 of this DPA, with the places of processing Germany (AWS eu-central-1), the United States and Costa Rica (Processor's personnel). Annex II is clause 2.3. Annex III is clause 2.4.

4.2 For transfers subject to the UK GDPR, the International Data Transfer Addendum to the EU Commission Standard Contractual Clauses issued by the UK Information Commissioner (version B1.0, the "UK Addendum") applies: Table 1 names the parties as in this DPA, Tables 2 and 3 are completed by clauses 1, 2.3, 2.4 and 4.1, and for Table 4 neither party may end the Addendum when the Approved Addendum changes.

4.3 Onward transfers to subprocessors follow Clause 8.8 of the Standard Contractual Clauses and clause 2.4. The disclosure in clause 2.4A is made on the Controller's instruction. Transfer-impact-assessment support is available on request.

5 — Liability and claims.

Nothing in this DPA limits Terms of Service Section 13 (limitation of liability), which governs claims between the parties, including claims under Art 82 GDPR to the extent the mandatory law allows. The Controller remains responsible for the lawfulness of its instructions and of the collection notices it gives its suppliers; Processor is responsible for processing carried out in breach of this DPA that is attributable to it.

6 — Term and termination.

This DPA takes effect on acceptance of the Terms of Service and ends when the Controller's account terminates and the return, deletion and retention in clause 7 are complete. Obligations in clauses 2.2, 2.3, 3, 7 and 8 survive.

7 — Deletion or return on termination.

On termination of the service the Controller may retrieve its data for the retrieval period in Terms §15(d). At the Controller's election, Processor then deletes or returns all personal data, except: (a) screening evidence, which the Controller instructs Processor to keep for 5 years from each screening for the Controller's record-keeping under Regulation (EU) 2023/1115, as a continuing documented instruction that survives termination; (b) custody hashes and audit records, which Processor keeps as an independent controller (clause 1.7) to establish, exercise or defend legal claims; and (c) records Processor must keep under Union or Member State law. Data within (a) and (b) is deleted within 90 days after its 5-year window ends.

8 — Audit rights.

Processor makes available to the Controller all information reasonably necessary to demonstrate compliance with this DPA. On 30 days' written notice, not more than once in any 12-month period (and additionally for cause where the Controller reasonably suspects a breach), the Controller — itself or through a mandated auditor bound by professional secrecy — may inspect Processor's relevant facilities, systems and records during business hours, under confidentiality, on Processor's premises or remotely. Processor contributes to audits and may satisfy an inspection demand by providing current independent audit or certification reports where they cover the requested scope. The Controller bears its own audit costs.

9 — Order of precedence and changes.

The GDPR and UK GDPR prevail; then the Standard Contractual Clauses incorporated by clause 4; then the rest of this DPA; then the Terms of Service, over which this DPA prevails on data-protection matters. Processor may update the subprocessor list under clause 2.5; other changes follow Terms Section 16.

Contact.

AdverseDays LLC (operator of the EUDR Clear product) · c/o Registered Agents Inc., 30 N Gould St Ste R, Sheridan, WY 82801, USA · contact via the contact form