Questions we are actually asked.

No. Frodiq is not approved, certified, endorsed, sponsored or procured by the Central Bank of Bahrain, and no software vendor should tell you otherwise about themselves.

When we say Frodiq is built for CBB-regulated firms, that describes the firms it is built for — licensees who are supervised by the CBB and carry obligations under its rulebook. It says nothing about our own standing with the regulator, because there is nothing to say.

The obligation stays with you. What Frodiq does is make the evidence behind your decisions easier to produce when the CBB asks for it.

Days rather than months, and we do it with you rather than handing over a manual.

Standard onboarding covers one entity, a CSV of your customers and transactions, and mapping that data to the product's fields using a template. Custom integration or a migration from another system is scoped and quoted separately.

No. It supports the MLRO and the compliance team, and it is built on the assumption that a person decides.

Every consequential action — a disposition, a case closure, a filing — is taken and recorded by a named person in your organisation, and consequential closures require a second approver. Frodiq raises alerts, shows the evidence behind them, and keeps the record. It does not judge anything.

Four official authorities across five machine-readable files: the US Treasury's OFAC SDN list and OFAC Consolidated (non-SDN) list, the European Union's consolidated financial sanctions list, the UK government's UK Sanctions List (published by the FCDO), and the UN Security Council's consolidated list.

Each is downloaded from the publisher directly, versioned on import, and shown with its version and the publisher's own date where the file carries one. OFAC's files do not include a publication date, so those show the date they were imported.

A screening result records which lists it consulted and at which versions — that record is stored with the screening rather than reconstructed afterwards.

No. Frodiq does not screen politically-exposed-person databases or adverse-media sources, and the product says so wherever a user might otherwise assume it is included.

PEP status is a client-provided input: you flag it, and the flag affects alert priority and case handling. It is not something we look up for you.

Both would require licensing paid data. It is on the roadmap as a commercial decision rather than a technical one, and we would rather tell you it is missing than let you find out during an inspection.

Arabic is first-class in both directions, not a translation layer over an English product.

Every screen exists in Arabic and English, right-to-left is a genuine mirror rather than a flipped layout, and both languages are acceptance criteria for every change we ship — measured on the rendered page rather than in the string files.

Screening matches Arabic names in their own script as well as through transliteration and spelling variants, so an Arabic query and a Latin listing of the same party meet.

No. Your whole compliance team is included — analysts and read-only auditors alike — because charging per seat discourages exactly the thing a compliance function should do, which is give more people visibility.

Train has a learner allowance per band, since training touches staff beyond the compliance team.

Yes. Monitor, Screen and Train are sold separately, and the Suite bundles all three at less than their combined price.

Most firms start with the module covering their most immediate obligation and add the others later. Moving from a single module to the Suite does not require a migration.

A ninety-day scoped implementation: agreed data, agreed detection scenarios, and success criteria written down before it starts, so both sides can tell at the end whether it worked.

It is run with you rather than handed over. Pilot fees are credited toward an annual agreement if you continue.