Security
Finpilot is designed to protect institutional investment information—from connected sources and user access through model requests, review and audit.
The security boundary
Finpilot limits each request to the permitted task, context and provider policy—then returns the response to the institution for review.
Approved institutional information
Access, roles and permissions
Only the context required for the task
Applicable policy and contract terms
Sources, exceptions and human judgment
The questions security teams ask first
Customer data is used to deliver the contracted service and is not used for model training under Finpilot’s approved policy and applicable provider contracts.
Provider terms and platform policy govern model requests.
Each institution’s records, documents and retrieval index are kept within its own boundary.
Institutional boundaries are part of the platform architecture.
People see only what their roles and permissions allow. Workflow participation, review, approval and administration remain distinct.
Authentication, roles and permissions are checked on each request.
Sources remain linked where available. Missing, conflicting or consequential information becomes a review item, and qualified people retain judgment.
Configured workflows determine what requires review and who approves it.
Customer data is used to deliver the contracted service and is not used for model training under Finpilot’s approved policy and applicable provider contracts.
Provider terms and platform policy govern model requests.
Each institution’s records, documents and retrieval index are kept within its own boundary.
Institutional boundaries are part of the platform architecture.
People see only what their roles and permissions allow. Workflow participation, review, approval and administration remain distinct.
Authentication, roles and permissions are checked on each request.
Sources remain linked where available. Missing, conflicting or consequential information becomes a review item, and qualified people retain judgment.
Configured workflows determine what requires review and who approves it.
Security foundations
Independent assurance, institutional isolation, encryption and governed model use protect how information enters, moves through and leaves Finpilot.
SOC 2 Type II, with the report shared during diligence.
Each institution’s information is kept within its own boundary.
Information is protected as it moves between systems and while it is stored.
Customer data is not used for model training under Finpilot’s approved policy and applicable provider contracts.
When diligence begins, we’ll walk your team through the architecture, controls, data flow, provider terms and independent assurance—and share the appropriate documentation.