Trust Center
Last reviewed: August 29, 2026
This page summarizes how My Loan Pipeline approaches security and privacy for mortgage pipeline operations. It describes controls we actually run today. It is not a SOC 2, ISO 27001, HIPAA, or PCI certification claim.
Legal terms live in our Privacy Policy and Terms of Use.
1. Security overview
- Authentication & MFA: Sign-in is handled by Clerk, with multi-factor authentication available for production access.
- Tenant isolation: Customer data is scoped by organization at the application layer. APIs require org-aware authorization before reading or writing tenant records.
- Role-based access: Org admins, processors, and loan officers see only what their role and team assignments allow.
- Secrets at rest: Arive organization credentials are stored as AES-256-GCM ciphertext. Plaintext secrets are not logged or returned to clients after save.
- Data minimization (LOS): Arive search and prefill responses expose mapped fields only; full LOS payloads stay server-side.
- Transport: The application is served over HTTPS.
- Access & privileged-action logging: We record signed-in access events (who, org, path, IP) and privileged actions (for example view-as, role changes, disables, org suspend) for platform operators. Org admins can review change history in Settings → Audit logs.
2. Subprocessors
We use the following vendors to operate the Service. This list describes each vendor's role and the kinds of data involved — it is not a certification or assurance claim.
| Vendor | Service | Data shared |
|---|---|---|
| Clerk | Authentication, MFA, sessions | User identity, email, session metadata |
| Vercel | Application hosting | Request logs, application telemetry |
| Neon | Postgres database | Tenant operational data (loans, forms, settings) |
| Stripe | Seat / subscription billing | Billing contact, subscription metadata (no card PAN in MLP) |
| Resend | Transactional email | Recipient addresses and notification content |
| UploadThing | File / document uploads | Uploaded files and related metadata |
| Sentry | Error monitoring | Stack traces and diagnostic context (may include limited PII) |
| Arive | LOS integration (customer-enabled) | Loan fields via API; org API credentials stored encrypted |
3. Privacy & DSAR requests
Depending on your location, you may have rights to access, correct, delete, or export certain personal information. How to proceed:
- Email intake: Send requests to admin@myloanpipeline.com with your name, organization, and the type of request (access / export / delete).
- In-product (organization admins): Signed-in org admins can open Settings → Privacy requests to log a request, export account-oriented data My Loan Pipeline holds for a user in the same organization, and disable that user's access when appropriate.
Important scope note: For loan and borrower records, your organization is typically the controller and My Loan Pipeline acts as a processor. Account-oriented exports cover membership and profile fields we store for the signed-in user. Borrower / pipeline operational data is owned by the customer organization and should be handled under that organization's policies (our in-product tools document this limitation).
4. Customer offboarding
Organization suspension and offboarding are handled by platform operators using an in-product runbook (suspend tenant, checklist for retention/deletion, Stripe seats, Clerk users, and uploads). Hard delete of an entire organization remains a controlled / manual step and is not self-serve from the marketing site.
5. Contact
Security or privacy questions: admin@myloanpipeline.com