Your statements carry insured names, policy numbers and your agency's revenue. Here is what happens to them, in plain language — including the part most vendors leave off.
We do not take API keys, database credentials, or carrier portal logins. There is nowhere to enter them, because there is no part of this product that reads from another system. Every reconciliation runs on files you chose to upload.
That means the usual questions about a vendor integration — what it can write, what happens when it breaks, who at our end can trigger it — have the same answer. There is no integration. Your management system never learns we exist.
Statements and book exports are used for one thing: extracting the lines, matching them against your book, and producing your reconciliations and dispute packets. They are not sold, not shared, and not used to train anyone's models — the extraction providers we use are under contractual zero-retention terms for exactly this reason.
Deleting a statement removes its extracted rows immediately and purges the stored file on the next sweep. If you ask us to delete the whole organisation, everything is gone within thirty days, and we will tell you when it is done.
Every table in the database carries a tenant boundary enforced by the database itself, not by application code remembering to filter. A query that escaped our own checks would still return nothing, and that isolation is verified by an automated test that runs before anything ships — it is not a claim on a page, it is a test that fails the build.
Uploaded files live in private storage reached only through short-lived signed links. Data is encrypted in transit and at rest. Webhook signatures are verified before the payload is parsed. Secrets live in our hosting providers' environment settings, never in the code and never in anything shipped to a browser.
We are not SOC 2 certified. There is no audit report, no Type II attestation, and no badge on this site, because there is nothing to put behind one.
A SOC 2 Type II costs tens of thousands of dollars and months of auditor attention. This is a small company, and that money is currently going into reading carrier statements correctly. Claiming the certification anyway would be a lie, and implying it with a seal in the footer would be the same lie in a smaller font.
What we do instead is on this page: no credentials to steal, tenant isolation enforced by the database and proven by a test, private storage behind short-lived links, and deletion that actually deletes. Those are narrower than an audit, and they are checkable — you can ask us about any of them and get a specific answer.
And the honest part: none of that is a substitute for an audit. If your agency or your E&O carrier requires a SOC 2 report from every vendor, we will not pass that check, and we would rather you found that out on this page than three calls into a sales process.
Questions about retention, deletion, sub-processors, or anything above — write to support@insurancecommissionreconciliation.com. It reaches the person who wrote the code.