This provision establishes that the applicable Terms of Service agreement is determined by the user's country of residence, with the Global Terms of Service serving as the default for users not residing in Canada, the EEA, or Brazil.
This analysis describes what Kraken's agreement states, permits, or reserves. It does not constitute a legal determination about enforceability. Regulatory applicability and practical outcomes may vary by jurisdiction, enforcement context, and individual circumstances. Read our methodology
This provision establishes the contractual architecture through which Kraken assigns different operative terms, including data handling, dispute resolution, and liability provisions, to different user populations based on geography. The operative substantive obligations for any given user cannot be assessed from this gateway document alone.
Interpretive note: The document does not specify the mechanism by which country of residence is determined or verified, creating ambiguity about which terms apply to users whose residence is disputed or changes over time.
Under this provision, the specific contractual terms governing a user's Kraken account, including any dispute resolution requirements, data processing authorizations, and fee structures, are contained in the regionally designated document rather than this page. Users must access and review the applicable regional agreement to understand the terms that govern their account.
Cross-platform context
See how other platforms handle Residence-Based Terms Routing and similar clauses.
Compare across platforms →"Because laws and regulations vary by country and region, different Terms of Service may apply depending on where you reside. Our Global Terms of Service are available here. Our Global Terms of Service will apply to you unless you reside in Canada, the European Economic Area, or Brazil.Excerpt from Kraken's Terms and Conditions
(1) REGULATORY LANDSCAPE: This provision implicates multiple regulatory frameworks simultaneously depending on user geography, including GDPR for EEA users, PIPEDA for Canadian users, and LGPD for Brazilian users.
Enforcement risk, jurisdiction flags, contract triggers, and due diligence action items.
Get the research letter
Companies change their terms quietly. We read every version and catch what actually changed. One email a week on the changes that matter and what they mean.
This provision establishes the contractual architecture through which Kraken assigns different operative terms, including data handling, dispute resolution, and liability provisions, to different user populations based on geography. The operative substantive obligations for any given user cannot be assessed from this gateway document alone.
Under this provision, the specific contractual terms governing a user's Kraken account, including any dispute resolution requirements, data processing authorizations, and fee structures, are contained in the regionally designated document rather than this page. Users must access and review the applicable regional agreement to understand the terms that govern their account.
No. ConductAtlas is an independent monitoring service. We are not affiliated with, endorsed by, or sponsored by Kraken.