Skip to content

Ordellum AnalyticsLaunching

Regulatory coverage

Nine regulatory and assurance references, expressed as versioned policy rather than hard-coded thresholds.

Frameworks covered and the role Analytics plays

  • Framework: FATF Recommendations

    Jurisdiction
    Global
    Focus
    AML/CFT, risk-based approach
    Platform role
    Policy and decision support
  • Framework: EU MiCA

    Jurisdiction
    European Union
    Focus
    Crypto-asset regulation
    Platform role
    Classification and compliance analysis
  • Framework: EU AMLR / AMLA

    Jurisdiction
    European Union
    Focus
    Single rulebook and central supervision
    Platform role
    Policy, evidence and report preparation
  • Framework: GDPR

    Jurisdiction
    EU / EEA and UK
    Focus
    Personal data protection
    Platform role
    Direct data governance
  • Framework: OFAC

    Jurisdiction
    United States
    Focus
    Economic sanctions
    Platform role
    Screening, alerts and preparation
  • Framework: VARA

    Jurisdiction
    Dubai, UAE
    Focus
    Virtual asset regulation
    Platform role
    Regime and policy support
  • Framework: SOC 2 Type II

    Jurisdiction
    Global
    Focus
    Information security assurance
    Platform role
    Internal controls and evidence
  • Framework: 5AMLD / 6AMLD

    Jurisdiction
    European Union
    Focus
    Anti-money laundering
    Platform role
    KYC and AML infrastructure
  • Framework: CCPA / CPRA

    Jurisdiction
    California
    Focus
    Consumer privacy
    Platform role
    Direct data governance

Thresholds, retention periods and reporting flows are managed as versioned, auditable policy packages. When regulation changes, the policy changes — without a software release. Each decision records the policy version it used, so it can be replayed exactly for audit.

Analytics prepares Travel Rule data and signals for clients in scope; it does not execute the transfer.

Jurisdiction thresholds

FATF
Threshold: ≥ $1,000 / €1,000
United States (FinCEN)
Threshold: ≥ $3,000; currency transaction reports from $10,000
European Union (TFR)
Threshold: ≥ €1,000
Singapore (MAS)
Threshold: ≥ S$1,500
Japan
Threshold: All transfers
UAE (VARA)
Threshold: AED 3,500

What Analytics adds as amounts grow

Under $1,000
Platform response: Standard monitoring and sanctions screening
$1,000 – $2,999
Platform response: Adds a Travel Rule reference signal when the client is in scope
$3,000 – $9,999
Platform response: Adds the US FinCEN Travel Rule signal
$10,000 and above
Platform response: Real-time AML threshold rule and a currency-transaction report signal
$50,000 within 24 hours
Platform response: Enhanced due diligence signal
Over $1,000,000 in one transfer
Platform response: Whale alert and AI analysis

The right to erasure and mandatory AML record-keeping can conflict. Analytics resolves this with a decision matrix backed by legal references.

Conflict resolution

  • Situation: A clean user asks for deletion

    Outcome
    Deleted within 30 days
    Basis
    GDPR Art. 17(1)
  • Situation: An AML investigation is active

    Outcome
    Deletion refused
    Basis
    GDPR Art. 17(3)(e)
  • Situation: The AML retention period is running

    Outcome
    Partial deletion with pseudonymisation
    Basis
    5AMLD Art. 40
  • Situation: A suspicious-activity file is open

    Outcome
    Restricted access
    Basis
    GDPR Art. 23 exemption

Retention periods

Raw identity documents
Kept for: Not retained (0 days)
Identity verification metadata
Kept for: 5 years
AML risk scores
Kept for: 5 years
SAR / STR records and audit logs
Kept for: 7 years
Raw analytics data
Kept for: 2 years
Aggregated analytics
Kept for: 5 years
  1. Step 1: Collect signals

    Identity document country, VASP registration, phone code and IP location.

  2. Step 2: Apply priority

    Identity document first, then VASP, then phone, then IP.

  3. Step 3: Resolve conflicts

    When several jurisdictions apply, the most restrictive rule wins.

  4. Step 4: Route policy

    EU to MiCA, AML directives and GDPR; US to OFAC, FinCEN and CCPA; UAE to VARA and FATF; unknown to FATF and OFAC.

Preparation targets by report type

SAR / STR
Preparation target: Draft in under 60 seconds; internal alert within 48 hours; client filing target 30 days
Currency transaction report
Preparation target: 15 business days
Travel Rule
Preparation target: Near-real-time
GDPR breach package
Preparation target: 72 hours
MiCA
Preparation target: Quarterly, plus 30 days
OFAC incident
Preparation target: 10 business days
VARA
Preparation target: Monthly, plus 15 days
SOC 2
Preparation target: Annual, plus 90 days