Every figure sourced.
Every limit stated.

For a bank

The whole retail market on one screen: deposit, loan and card catalogues read from each bank's own published pages, the central bank's registry of 35 licensed banks, official FX and the interbank money-market curve. Rates are stored as the bank stated them, never computed to fill a gap, so a comparison desk sees what was published and what was not.

For an insurer

A market view of 51 products from ten insurers, the state register's participant roster, and a needs-analysis engine whose every multiplier is a named industry convention, disclosed in the response and overridable per call. An input it lacks returns “cannot assess” with the missing list, never a need of zero.

For a fund or brokerage

The exchange's own numbers in a queryable warehouse: prices, disclosures, corporate actions, fundamentals and 300+ named ratios per issuer. Shari'a screening to AAOIFI Standard 21 and Meezan's criteria across every listed ticker, and portfolio risk (volatility, VaR, drawdown, beta, concentration) computed in exact decimal.

For a regulator or auditor

A system built to be examined. Every figure carries its source and date; an unknown renders as “n/a” with a machine-readable reason; statutory parameters cannot be saved without citing their decree; and anything that can act on money writes an audit row with its reasoning before it acts.

Credentials encrypted, failing closed

Brokerage credentials are Fernet-encrypted with a key that exists only in the environment. There is no default key and no generated fallback: if the key is absent, every encrypt and decrypt raises, and the platform refuses to store the credential rather than persist plaintext (backend/apps/brokerage/crypto.py).

Entitlements enforced on the server

A feature grant is an API permission checked on the backend, not a hidden button. What a user has not bought, the API refuses; the interface merely reflects that refusal.

Every row has an owner

Portfolios, orders, messages and declarations are owner-scoped at the query level. One user's data is structurally invisible to another, not filtered out in the view layer.

Two-factor that proves delivery first

Optional Telegram two-factor login can only be enabled after a live code was actually delivered and verified, so no account can become gated on an undeliverable code. Codes are hashed, expiring, attempt-capped and single-use, and two-factor is deliberately not a paid feature.

Secrets masked by default

Anything secret-like renders masked and is revealed per item behind an explicit control; list views only ever hold the masked shape.

Money is exact, end to end

NUMERIC(38,2) in the database, decimal strings on the wire, integer minor-unit arithmetic in the browser. No money value touches a float anywhere, and the schema can prove it in one query.

A statutory number cannot be uncited

Tax and pension parameters are effective-dated rows naming the decree that set them, and the database CHECK constraint refuses a row without a source reference. Citation is schema, not habit.

What we do not hold: no ISO 27001, no SOC 2, no PCI DSS. Nobody has audited this platform but us, and a procurement page that implied otherwise would fail the first check you ran. The controls above are code; bring your security team and we will walk them through it, module by module.

Contact details read from the platform's own public settings as this page rendered.