Security and data
Your book, your clients' details, and who can see them.
A brokerage holding ID numbers, banking details and FICA packs for a few thousand people carries a real obligation. Here is exactly how Meridian handles that, including the parts most vendors leave vague.
Hosted in South Africa
Client records and documents are stored in South African infrastructure. Where a copy is held elsewhere for resilience, it is stated plainly rather than buried.
Built for POPIA obligations
An access trail on every client document, role and group scoped visibility, and a defined retention position. The evidence exists before anyone asks for it.
Access is scoped, not assumed
A broker sees their own book. A manager sees their team. A brokerage admin sees the brokerage. Nobody is handed everything because it was easier to build.
Support access is visible and bounded
When our staff open a session on your account it is time limited, reason logged, shown on screen, and written to your own audit trail.
History that survives a bad day
Every change is written to an append only event log and archived independently, so a record can be reconstructed rather than merely restored.
Encrypted in transit and at rest
Documents are served through short lived signed links scoped to one brokerage, so a link that leaks expires rather than opening a door.
What we do not claim
Meridian is not certified against ISO 27001 or SOC 2 today. When that changes it will be stated here with the certificate, and not before.
Meridian is not a compliance product. It keeps the evidence your obligations require, which is the trail of who did what and when. It does not discharge those obligations for you and no software can.
Meridian does not give financial advice and is not an FSP. The advice stays yours, along with the record showing you gave it.
The operating system for insurance brokers.
Find your line.
Bring your book across, and by Friday you will know what your month is actually worth.
No card, no contract, and no insurer has to approve it.