FAQ
Plain answers before someone asks for access.
These are the questions a compliance, operations, or IT reviewer is likely to ask before trusting a new tool with real workflow data.
Reviewer checklist
The FAQ is written for the person who has to say yes carefully.
Know whether the product is official or independent.
See what the report contains before creating an account.
Understand what data sources and privacy posture are used.
Is Compliance Platform an official EU service?
No. It is an independent product that maintains working databases and indexes derived from public official sources. Critical trade and regulatory decisions should be reviewed by qualified customs, legal, or trade compliance professionals and verified against official sources or competent authorities.
Where does the data come from?
The current product focuses on TARIC information, EUR-Lex legal references, restricted-goods review, and entity sanctions screening. Screening workflows use working data derived from public official sources and reference datasets such as EU FSF, OFAC SDN/Non-SDN, UN SC, LV FID, UK Sanctions List, CH SECO, US CSL, Canada SEMA, Australia DFAT, Ukraine NSDC, Japan MOF, and GLEIF LEI data. Reports keep source links visible where available.
Is this legal advice?
No. The platform helps organize checks, evidence, and review signals. It does not replace legal, customs, trade, or regulatory advice, or a final decision by a competent authority.
Why request access instead of instant signup?
The production launch is planned for summer 2026. Test access is available now, but we want to understand the workflow and expected volume so the pilot is useful instead of noisy.
Do you need a cookie banner?
Not for the current essential/auth/security cookie posture. If we add non-essential analytics, marketing pixels, heatmaps, or similar tracking later, we will add consent handling before those tools load where required.
Can the platform connect to internal tools?
Yes, API and MCP access are part of the planned team and integration path. During testing, access should be scoped to an organization and reviewed before use.
What should I include in a test access request?
A work email, company, country, expected volume, and a plain description of the workflow: for example trade and regulatory checks, RU/BY exposure review, report evidence, or API/MCP integration.
Can I upload confidential shipment data?
For the early test-access phase, avoid entering unnecessary confidential shipment data. Use representative CN/TARIC codes and operational scenarios unless a separate customer agreement says otherwise.
Have a specific pilot workflow?
Send the use case and expected volume. We will reply with the right test path.