Regulatory information
Regulatory framing, partner model and operational boundaries
This draft page prepares the public regulatory framing for Cemperium Nordic AB. It is intentionally conservative and focuses on structure, partner roles and control architecture rather than promises about live authorization scope.
Last updated: May 2, 2026
Regulatory highlights
- Cemperium is aligning with applicable European regulatory frameworks, including MiCA readiness where relevant.
- Certain regulated services may be facilitated through licensed third-party providers during early phases.
- The platform is being prepared around auditability, role-based access control and structured oversight rather than informal trust assumptions.
- Regulated expansion should happen in stages, with partner-based infrastructure early and stronger internal capability later if justified.
AML / KYC model
The prepared operating model assumes that certain onboarding, KYC and AML procedures may be handled by regulated partners rather than directly by the public website itself. This maintains a clear separation between website access, platform logic and regulated financial onboarding responsibilities.
Control architecture
Public-facing functionality is being prepared around access controls, auditable actions, role-based permissions and phased enablement. The goal is to make future expansion easier to supervise and safer to operate.
AI assistant regulatory boundary
- Advisory only: the AI assistant may provide insights, explanations and suggestions, but it must never execute transactions or take control away from the user.
- Explainability: tips and insights should be understandable, contextual and traceable to meaningful user-relevant signals.
- Privacy first: data handling should stay segmented, controlled and transparent, with clear user visibility into what is stored and why.
- Timing over noise: insights should appear at useful moments instead of becoming constant interruptions.
- User control: recommendations support decision-making, but the final action should always remain with the user.