An EU resident may see a global crypto brand, a local-language page, and several legal entities at once. The useful question is not “Is this platform famous?” but “Which entity contracts with me, for which product, under which terms?” This evergreen framework helps compare disclosures and preserve evidence. It deliberately avoids current licensing conclusions; those require the official register and the reader’s facts on the date of use.
Map brand to legal entity
Open the customer agreement, privacy notice, and regulatory disclosures from the official domain. Record the legal name, registered address, governing law, and service entity shown for the intended country. A logo or app name can cover multiple subsidiaries. If the account onboarding screen assigns a different entity than the marketing page, save both and ask support through the authenticated channel.
Define the product boundary
List the exact services: spot custody, derivatives, staking, lending, payments, card, or transfer. Authorization and consumer protections can differ by product and entity. Do not use a platform’s general statement to cover a feature it does not name. Capture eligibility, minimums, and restrictions in the same comparison table so a later product update does not erase the original scope.
Check official registers yourself
Use the relevant EU authority or register linked by official guidance and record the query date, name searched, status wording, and scope. A registry entry may concern an entity, a service, or a transitional arrangement; it is not a universal safety rating. Avoid relying on a third-party badge, social post, or search snippet. If no clear match appears, mark the result unresolved rather than inferring approval.
Review custody and complaint paths
Read how assets are held, whether customer assets are segregated, what insolvency language says, and where complaints are submitted. These terms are contractual facts, not guarantees. Note the support entity, escalation timeline, and required records. A page that explains technology does not replace the account agreement. Keep a PDF or stable link and a date because terms can change.
Compare fees and execution conditions
Capture maker/taker fees, spread disclosures, withdrawal minimums, network fees, conversion rates, and settlement times for the exact product. A low headline fee may omit spread or a fee on the quote currency. Check whether a transfer is on-chain or internal. Build a small example using the published units, but label it as an estimate and preserve the assumptions.
Consider data and access controls
Record KYC requirements, data retention, supported residence, account recovery, and two-factor options. A language selector does not prove that a resident is eligible. Do not bypass a restriction with a VPN or a different address. If the provider requests more data than the product requires, ask for its privacy explanation and store only the minimum needed for the comparison.
Write a dated decision note
End the comparison with facts, open questions, and a recheck date. Include official links, screenshots with sensitive data redacted, and the exact entity and product considered. Do not write “regulated” as a conclusion unless an official register supports that wording for the precise service. The framework is valuable because it keeps uncertainty visible and prevents brand familiarity from becoming due diligence.
Worked example: brand versus entity
A global app displays a European-language interface, while its customer agreement names a different subsidiary than the marketing footer. Save the agreement, onboarding entity, product page, and register search result with dates. Compare only the specific service—spot custody, staking, or derivatives—and mark any absent register match as unresolved. If the provider changes entities after onboarding, preserve both versions and ask which agreement governs existing assets. The file should never use a broad “EU regulated” label to cover an unexamined product.
Frequently asked question
Does an EU language page prove that a service accepts my residence?
No. Eligibility, entity, product, and local restrictions must be confirmed in the current account terms and official disclosures. Language support is a usability feature, not an authorization decision.