Keep track of clients
Langford · built by us
Your clients, their policies and documents in one place, with a renewals board that shows what has been done about each renewal.
Tested by Langford on Oct 20, 2026: Published to our hosting and checked: 12 of 12 hosting checks passed. Signed-in use was tested on a local copy, not on the hosted one. Read the test report
Built for sensitive data with setup. Has its own sign-in with authenticator codes, an activity log of sign-ins, changes and downloads, and documents that only signed-in people can open.
Published to our hosting and checked: 12 of 12 hosting checks passed. Signed-in use was tested on a local copy, not on the hosted one. Testing shows the app starts and signs in. It is not a security audit.
You hold policyholder and client nonpublic personal information (NPI), so your information security program has to cover where it lives. This hosting helps you meet parts of your state's insurance data security law (based on the NAIC model law) and, in New York, the DFS cybersecurity rule (23 NYCRR 500). Below are the questions you get from a market conduct examiner, a carrier or your E&O questionnaire, answered for Langford Agency.
Yes. The database and file storage are encrypted at rest, and every connection uses TLS 1.2 or later. A setting that would weaken this is refused.
No. The database and file storage have no public address; only this app, inside a private network, can reach them. Producers and CSRs get in only through the app's sign-in.
Yes. This app asks every user for an authenticator code at sign-in, producers and CSRs included.
Yes, two of them. The app keeps its own activity log of sign-ins, changes and downloads, and our hosting logs every database and storage access to a separate archive kept 6 years.
Backed up: yes, point-in-time restore for 35 days. Restore drills: designed, not run yet, so we cannot show you a restore receipt today.
Checked on our test setup on Oct 20, 2026. After your launch we run them again on yours.
Tested is not an audit. We check our hosting and test that the app starts and signs in; meeting these rules is still your program's job.
Published to our hosting and checked: 12 of 12 hosting checks passed. Signed-in use was tested on a local copy, not on the hosted one.
The result file is under Technical details.
Customer reviews appear here once offices are using it.
From our last PostgreSQL hosting check run: runs/crm-test-2026-10-20/verify.txt. 12 of 12 passed. Control ids are defined in docs/CONTROLS.md.
| Result | Check | What was checked |
|---|---|---|
| Pass | NET-PRIVATE | postgres public network: Disabled |
| Pass | NET-PRIVATE | storage public network: Disabled |
| Pass | IAM-WORKLOAD | storage shared key: false |
| Pass | ENC-TRANSIT | postgres require_secure_transport: on |
| Pass | ENC-TRANSIT | container app allowInsecure: false |
| Pass | AUDIT-LOG | pgaudit loaded: pg_stat_statements,pgaudit |
| Pass | BACKUP | postgres PITR days: 35 |
| Pass | GUARDRAILS | deny assignments on rg: 7 |
| Pass | POSTURE | audit initiatives on rg: 2 |
| Pass | ENC-TRANSIT | GET <your app address> 200 |
| Pass | AUTH-UNIQUE | document download without a session: 401 |
| Pass | NET-PRIVATE | anonymous blob read from the internet: 403 |