Security: SOC 2 Type II, SOX-aligned, built to the ASOPs
Your book stays yours.
A number you can’t trace isn’t a slightly worse number. It’s one nobody can sign.
Audited against the standards a filer is held to.
AICPA SOC 2 Type II
Book time with us.
Send the questionnaire over if you have one. If you’d rather just ask us the one thing you actually want to know, do that instead.
SOC 2 Type II
Monitored continuously by Rippling against the AICPA trust services criteria. The current report is on the trust center.
Penetration testing
Somebody outside the company does the testing. You read their summary under NDA rather than our account of it.
SOX aligned
Aligned rather than certified, because SOX attaches to the filer and not the tool. Every promotion carries its own walkthrough.
Built to the ASOPs
Written for actuaries working under the Code of Professional Conduct and the US Qualification Standards.
For security and IT
Insurance-grade security.
Controls are tested continuously, not once a year and never again.
SOC 2 Type II
Watched continuously against the AICPA trust services criteria: security, availability, processing integrity and confidentiality. It runs on Rippling’s compliance platform, which watches the whole company and not one team of it. The current report is on the trust center.
Penetration testing
Somebody outside the company does the testing, and you can read their summary under NDA through the trust center.
SOX
SOX attaches to the filer and not to the tool, so there is nothing here for anybody to certify us against. What we can do is hand your auditor the walkthrough: every rate-plan change carries its reviewer, its timestamp, the model version and where the number came from.
Actuarial standards
Built for actuaries working under the ASOPs, the AAA/CAS/SOA Code of Professional Conduct, the US Qualification Standards and the CAS Statements of Principles. A licensed actuary still signs. Nothing here signs anything, and nothing we hand back is an actuarial opinion until a qualified actuary decides it is one.
No training on your data
Your rate plans, filings, books and submissions never go into training a shared model. Not under any contract, and not at any tier.
Per-tenant isolation
Every customer gets a tenant of their own. Nothing runs across them, and there is no shared embedding or vector store sitting underneath.
Encryption
AES-256 at rest and TLS 1.3 in transit, with a KMS key that is yours alone. We write the logs without plaintext PII, which matters most on the day somebody outside the team has to go and read them.
Retention and deletion
How long we keep things is set in your contract. Ask us to delete and that covers the analysis trail too, not just the documents you sent. The privacy policy has the whole list rather than our summary of it.
SSO and SAML
Okta, Azure AD and Google Workspace, so who gets an account stays a question for your own directory.
Roles
Author, reviewer and approver are three different people, and an actuary cannot push their own work to production.
Audit log
Every promotion is logged with who moved what, and when. The record outlives the people in it.
Your own private VPC
Every customer runs in a private VPC of their own. There is no route out to the public internet from it, so nothing you put in can leave on its own. Model calls go out through a guarded path that is the only door in the wall.
Hosted
We run and watch that VPC for you. Most carriers pick this one, and usually for procurement rather than security, because a tenant we run clears review faster than a deployment their own team has to keep patching.
On-prem or your own account
The same code, on your own infrastructure, for the books that are not allowed to leave the building.
Subprocessors
Every model provider and vendor that touches customer data is on the trust center, with what each one is there to do. The model providers are all on zero-retention agreements.