Skip to main content
Security & Data Architecture Zero External AI Model Providers RFC 9116 /.well-known/security.txt Active

Security, Data Provenance & On-Server Governance for General Partners

General Partners, IR heads, and compliance officers require strict confidentiality around active fundraises, target investor shortlists, and anchor relationships. Prilago LLC executes all investor search, document Q&A, and suitability scoring deterministically on its own servers without sending user queries or pipeline data to third-party AI model providers.

1. Deterministic On-Server Execution

Prilago LLC executes all search, document Q&A, and investor matching deterministically on its own servers. Your fund parameters, target check sizes, anchor investor inputs, and saved pipeline lists are never transmitted to third-party AI model providers and never shared across workspaces.

2. 100% Statutory & Public LP Provenance

All 44,130 public disclosure records across 3,520 direct institutional LPs and 1,926 SEC Form ADV advisers are sourced exclusively from lawful public disclosures: state FOIA/OPRA responses, public pension ACFRs and board packets, IRS Form 990-PF/Schedule D, SEC Form ADV, DOL Form 5500, and NAIC Schedule BA filings (/coverage). Zero personal emails or phone numbers are stored.

3. Strict Tenant Isolation & Read-Only MCP

Every GP workspace and fundraising pipeline is isolated at the PostgreSQL row level by authenticated user_id. Our Model Context Protocol (/mcp) server executes strictly read-only parameterized queries with scoped API keys (prilago_mcp_pro_* / prilago_mcp_free_*) that can be revoked in one click.

Technical Security & Compliance Controls

Control Domain Implementation on Prilago Verification Status
Transport & Archive Integrity TLS 1.2/1.3 (HSTS enforced) across all web & MCP traffic; SHA-256 byte-integrity hashes verified on archived statutory filings. Enforced
Session, Cookie & 2FA Hardening Signed HS256 JWT session cookies stored exclusively in server-only secure browser cookies over HTTPS (never exposed to client scripts or localStorage); RFC 6238 TOTP two-factor authentication, bcrypt password hashing & per-IP rate-limited authentication endpoints. Enforced
Webhook & SSRF Protection Fail-closed HMAC token verification on inbound webhooks; strict outbound URL allowlisting blocking RFC-1918, loopback, and cloud metadata IPs (169.254.169.254). Enforced
Cryptographic Source Audit Trails Every public source verification page (/public-source/[token]) is signed with an HMAC-SHA256 token tied to the exact commitment ID and field-level provenance record. Enforced
Vulnerability Disclosure RFC 9116 compliant /.well-known/security.txt published; security reports triaged within 24 hours at security@prilago.com. Active