Trust

Compliance

Last updated 25 October 2026

This page collects what a due-diligence review usually asks for. The same content is available as a downloadable PDF pack for your compliance file, and a signed data processing agreement is available on request through the contact page.

How the methodology maps to COBS 9A

Revela is an evidence engine for the suitability assessment; the advising firm retains the regulatory responsibility for its advice.

Risk the client is willing to takeMeasured from revealed behaviour under simulated pressure (behavioural simulations and video scenarios), not self-report. The stated figure is captured separately and tested against behaviour; the gap is flagged.
Risk the client is able to takeCapacity for loss recorded in the adviser fact-find (income, wealth, horizon, liquidity) and reconciled against willingness. The recommendation is held at the lower of the two, never raised to chase a goal.
Knowledge and experienceCaptured in the fact-find and carried on the record alongside the behavioural result.
Record keepingEvery sitting stores its raw inputs, the engine version that scored it, the full output and a SHA-256 seal. Adviser overrides carry who, when and why. Any figure in any report is reconstructable.
Periodic reviewPer-firm review cadence, due flags on the client book, re-sit reassessments that measure drift between sittings on the record.

How the method maps to SEC Nigeria's suitability rules

For a Nigerian firm, every product is checked against the client in two stages: the SEC’s rules first, then the behavioural fit. A product that fails a rule goes no further. The firm retains the regulatory responsibility for its advice; Revela records how each check was made.

Investor classificationEach investor is classified from the facts recorded, under the rule set in force: retail, high net worth or institutional. An institution is never treated as retail. The reasons are kept with the classification.
Retail permitted list (rule 5(a))For a retail client under a discretionary mandate, the product must be in a permitted category, with its evidence checked by Revela before the product can be used.
Related parties (rules 5(b), 5(c))For a retail client, no underlying asset issued by or co-invested with a related party of the manager, and no related-party custodian.
Signed mandate (rule 6(a))For high net worth and institutional discretionary mandates, a signed mandate stating the objective and risk tolerance must be on file. Clients sign by link.
Offshore cap (rule 6(c))For high net worth and institutional money, offshore holdings stay within the cap of assets under management. Where a proposal goes over, the check gives the amount that fits.
Mandate restrictions (rule 3(b)(iv))No asset class, sector or industry the mandate excludes.
Behavioural fitHard stops on the client’s horizon, capacity for loss and need for income. Each product is read against the client by its passport, a record built from SEC Nigeria’s fund reports under one published rule, and sized to the loss the client is likely to sell at. An institution is read from its policy, its record and its officers’ decisions.
Risk consentEach check or portfolio that fits is acknowledged by the client by link. The wording shown is versioned and its SHA-256 hash is kept with the signature.
Record keepingEvery check is sealed with the rule set, the client’s profile and the product’s record behind it, and none can be changed afterwards. The SEC file for a client collects the classification, profile, mandate, every check with each rule’s result, any override and every signed consent.

Data processing roles

The advising firm is the data controller for its clients; Revela Behavioural Technologies processes that data on the firm’s documented instructions. Clients never create accounts: single-use, hash-stored assessment links are the entire client-facing surface, and no camera or microphone access is ever requested.

Security posture

Scoring runs entirely server-side; behavioural weights never reach a browser. Multi-tenant isolation is enforced with row-level security plus firm scoping on every query. Staff accounts support two-step sign-in (an authenticator app or an emailed code, checked by the database as well as the app), one-time passwords are rotated at first sign-in, and every administrative action lands on the audit trail with source IP. Full detail is on the security page.