Share the context first.
Agree evidence access next.

Who operates MarketPass

MarketPass is a product and service operated by ENCODE INFO - FZCO. For privacy or data requests, contact privacy@marketpass.encodeinfo.com.

What the website collects

The readiness form asks for business contact details, importing context, source countries and a high-level view of your current EUDR position. It also sends the referring page, campaign parameters and submission time to help us understand and respond to the enquiry.

Do not enter plot coordinates, supplier documents, personal identity records, contracts or commercially sensitive shipment details in the free-text field.

Where an enquiry goes

The form is processed by the website’s server and forwarded to the MarketPass account in Encode CRM, using GoHighLevel infrastructure. The existing booking service is also provided through that infrastructure. Relevant service providers may process technical request information such as IP addresses.

The public site uses no advertising pixels and sets no analytics or advertising cookies. Third-party booking pages have their own service behaviour and privacy terms. Read the privacy notice for the enquiry-processing details.

Operational evidence is a separate step

Before receiving supplier documents or geolocation files, we agree the engagement, the evidence-sharing channel, permitted users and responsibilities. The method should suit the sensitivity of the records and any restrictions imposed by the supplier.

We do not ask a supplier to make commercially sensitive information publicly accessible. Where disclosure restrictions exist, they need a workable agreement; they do not remove the operator’s need for sufficient information.

Partner enquiries

Use the partner enquiry form for business-level context only. Customer introductions, contact permissions, confidentiality, evidence access and any data-processing requirements are agreed before operational records are shared.

Access, purpose and retention

Operational arrangements should identify who can upload, review, approve and retrieve evidence; which service providers will process it; and how access ends when the engagement closes. The agreed record-retention schedule must account for applicable regulatory obligations and the purpose for which personal information is held.

A public enquiry is not the same thing as an EUDR compliance record. Avoid applying a blanket regulatory retention period to every contact field simply because it sits in the same business process.

No unverified assurances

This page does not claim exclusive EU hosting, a particular information-security certification or that all operational processing happens in one jurisdiction. Specific hosting, processor, transfer and contractual requirements should be reviewed before operational evidence is shared.

Practical preparation

• Nominate an internal evidence owner.
• Identify supplier confidentiality restrictions early.
• Separate general product information from personal or commercially sensitive records.
• Agree access and retention requirements in the engagement.
• Keep approval and evidence histories retrievable.