LoanPilot

Security & privacy

How teams, roles, data and paid enquiries are protected.

Security & privacy

Teams & roles

Data is scoped to a team. Every analysis, credit check and rule belongs to a team, and every endpoint enforces team-scoping — one team can never read or act on another's data. Only a team admin can change the rules; any member may read. Platform owners can view and tune any team's rules from the admin app, versioned exactly like the team's own edits.

A credit-bureau pull is a real, billable enquiry on a real person's file. It runs only when the account is entitled and the bureau is enabled, requires the applicant's consent, reuses a recent report within the re-pull window, and is rate-limited per user. Uploads are rate-limited too, to cap runaway AI cost.

Data handling

  • Statement page images are served no-store (not left in the browser cache).
  • The audit log records what changed, not counterparty/UPI identifiers.
  • Money and per-token pricing are admin-only.
  • AI sees statement text only as untrusted data; secrets live in the environment and are never logged or returned.

Decisions assist a human

Document-integrity flags, mule patterns, name mismatches and derogatory bureau marks are always routed to manual review. LoanPilot supports the underwriter; it does not replace them.

On this page