Certova
ENES
Request a demo
Security

An agency’s book is the whole business.

Accounts, carrier relationships, commission history, every document ever issued — that is what an agency management system holds. These are the controls that protect it, described specifically enough to hand to your E&O carrier.

The mechanisms, not the badges
ISOLATION

One agency cannot see another’s data

Tenant isolation is enforced in the database with row-level ownership. The application account has no override, and the isolation is adversarially tested before every deploy — not assumed.

AUDIT

An append-only audit log

Every change records who, what, when, and the before-and-after values, appended in the same atomic transaction as the change itself. The log cannot lose an entry the change kept.

EVIDENCE

Frozen evidence, stored write-once

What a certificate or policy document said on the day it was issued is snapshotted and stored under object lock. When a dispute arrives in year three, the evidence is the original — not a reconstruction.

IDENTITY

Identity, roles and MFA

Seven roles with least-privilege defaults, multi-factor authentication required for every user, SSO supported, and no shared logins — the audit trail stays attributable to a person.

Questions we get asked

No. Client data never trains models, and the restriction is written into the contract, not just the marketing site. Model calls pass through a gateway that strips tax IDs, bank details and licence numbers before anything leaves.

Yes — a complete export, free, any day you want it, including the day you close the account. Exit cost is part of the price, and ours is zero.

In progress — the observation window is running. Until the report exists we would rather show you mechanisms than badges, and after it exists we will show you both.

Ask us the hard version of any of these.