AI Investments v6.1.8

Release Date: August 26, 2026 Tags: COMPLIANCE, INVESTMENT, MOBILE, DISCLOSURE

Overview

This product now ships blocked in the US, the UK and the EU, and is refused to the mobile app outright. What is being sold is a fixed return over a fixed duration, paid from the operator's own funds — the plan carries a profit percentage and a settlement job pays it, and there is no strategy underneath. An advertised fixed return with no underlying strategy is the textbook shape of an unregistered collective investment scheme in those territories.

That does not make the product legal anywhere. What it does is move the decision to you, on the record: the default block is lifted only when a Super Admin accepts a versioned risk statement, and the accepting account, the timestamp and the exact wording are stored and appear in the audit trail. Adding territories never needs an acceptance — that makes the product more restricted, not less.

The purchase form also now states plainly where the return comes from. Read Upgrade Notes before updating. Requires Core v6.7.2.

Update Instructions

pnpm updator

Restart the backend and ship the frontend build. There is no database change.

Upgrade Notes

Plans are blocked in the US, the UK and the EU

• This applies to upgrades, not just fresh installs. If you sell to customers in those territories today, they will be refused after you update.
• The territory list and the acceptance live in core, at Finance → Investment → Compliance.
• A half-configured install is blocked, never open. Removing a default territory without the acceptance stores your list and does not apply it — the gate keeps blocking, and the screen tells you which entries are not taking effect.
• Revising the statement invalidates every acceptance of the old wording and the defaults come back until somebody accepts the new one. An operator must not be held to have accepted a statement that did not exist when they clicked.
• Existing investments are unaffected, and exits are never gated.

Changed

A territory gate at the point of purchase

• Added the residence check to opening an investment, placed with the other entry gates and before anything is debited.
• Residence comes from the KYC application you approved, from the customer's profile as a fallback, and from the CDN country header last. Any of the three matching blocks, rather than the strongest available signal — otherwise a VPN defeats a verified identity, or an edited profile defeats a header, depending on which happened to be present.

The mobile app does not carry this product

• Changed the plan and investment routes to refuse a native app client with a 403 that explains why. The mobile build has no screen for it either; this is the other half of that removal, because a removal whose endpoint still answers reads as concealment rather than as a removal.
• The refusal does not tell the customer where else to go. An in-app pointer to an outside mechanism is the offence itself, not a mitigation of one.
• Browsers are unaffected.