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?
Access requests let us create the right organization workspace, plan, limits, roles, and API/MCP scope from the start. Existing users can sign in directly.
Do you need a cookie banner?
Yes, and it is already in place. The public site loads Google Analytics 4, so a consent banner asks first: accepting and rejecting analytics are equally available, and the choice can be changed at any time. Without consent the tag never loads. The platform application itself carries no analytics — only essential authentication, session and security cookies, which need no consent.
Can the platform connect to internal tools?
Yes. API and MCP access use scoped organization credentials and are available according to the workspace plan. Authorized users can review, rotate, and revoke credentials.
What should I include in an 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?
Enter only data your organization is authorized to process. Representative CN/TARIC codes and operational scenarios are suitable for a first evaluation; customer data is handled under the applicable agreement and Data Processing Terms.
Ready to start with a real workflow?
Send the use case and expected volume. We will reply with access details or one focused follow-up question.