Security and data boundaries
Know how agency data is handled before you share it.
One agency context supports financial, book and team review, with different access for different responsibilities. Before records are shared, understand where they live, who can access them and the written terms governing their use.
REVIEWED · CURRENT PILOT DEPLOYMENT MODEL
Agency data and access
Know where records live and who can use them.
These four boundaries describe the current deployment model. Your agency's sources, roles and requirements are reviewed before onboarding.
Your agency’s records stay separate
Keelridge keeps each agency’s customer, policy, employee and reporting records isolated from other agencies. In the current pilot deployment, each agency is provisioned with separate application and database resources.
The right context for each role
Access starts with an approved identity and defined agency role. Owners can review whole-agency management evidence; managers work within authorized assigned-team views; account managers work within their own-book scope. Commission, payout and profitability remain restricted to authorized executive or finance views.
Source files stay controlled
Supported agency reports are handled through controlled databases or private storage, then validated and confirmed before they update the review. Privileged application credentials remain server-side. Your AMS and accounting records remain authoritative.
Sensitive activity is recorded for review
Keelridge records defined classes of sensitive access and consequential changes, including identity and role changes, exports, source intake and configuration changes, so those events can be reviewed.
Public demo boundary
A real product surface with fictional records.
The public demo is deliberately separate from every client agency. It does not ask visitors to upload files or enter agency information.
Explore the fictional demoBefore onboarding
Agree the scope before records are shared.
- Sources, roles and implementationReview source fit, security readiness, agreed access and supported workflows before accepting the agency for a pilot.
- Written data-handling scopeBefore intake, the written pilot scope identifies supported sources, responsibilities, any AI provider involved, applicable retention terms and expectations for data return or deletion.
- Your agency’s requirementsKeelridge does not currently have a SOC 2 report. We review each agency’s legal, regulatory, vendor and insurance requirements during pilot readiness and do not claim compliance attestations we have not obtained.
- A conversation before confidential filesStart with the management question and the types of reports involved. Do not send customer records, policy documents or credentials during the initial inquiry.
Security questions
Straight answers before an owner walkthrough.
How is one agency’s data kept separate from another’s?
Keelridge keeps each agency’s customer, policy, employee and reporting records isolated from other agencies. In the current pilot deployment, each agency is provisioned with separate application and database resources.
Does the public Keelridge demo contain real client-agency data?
No. The public demo is a separate fictional agency built from synthetic customers, employees, policies, opportunities, documents, and financial figures. Business-changing actions are disabled.
Does Keelridge currently have a SOC 2 report?
No. Keelridge does not currently have a SOC 2 report. We review each agency’s legal, regulatory, vendor and insurance requirements during pilot readiness and do not claim compliance attestations we have not obtained.
Should an agency email policy files during the first conversation?
No. An initial owner walkthrough needs the management question and a description of the available report types. Do not attach customer records, policy documents, credentials or other confidential agency data.
Does Keelridge use agency data to train AI models?
No. Agency data is not used to train AI models. Keelridge uses a third-party AI provider for defined tasks: reading uploaded commission statements and accounting reports, checking uploads for likely errors, routing uploaded documents, and answering staff questions in the read-only Keelridge Assistant from figures they are authorized to see. The provider's terms prohibit training on that data. Before an agency shares records, the written pilot data-handling scope names the provider and its retention terms. Document-grounded Q&A is not currently offered in the pilot.
Before sharing records
Start with the management question.
Book a 30-minute owner walkthrough using fictional agency data. Describe the review you want to improve and the report types available, then discuss the appropriate security and implementation scope. Do not send customer data with an initial inquiry.
Ask about security and data handling →