Appraiser Machine relies on a small set of trusted third-party services to deliver the product. Each one processes customer data only for the purpose described below, under the terms of its own Data Processing Addendum (DPA).
Last updated: April 16, 2026. We provide at least 15 days' notice before adding a new subprocessor that processes customer PII.
AI Judgment Analysis on QC review (Step 2). Borrower name, lender name, loan number, and case number are tokenized before transmission. The full PDF is not sent when local extraction is sufficient. Step 1 (deterministic local QC) does not use Anthropic.
Public-records property lookup. When you click "Property Data" on an order, the property address is sent to Google's Gemini model with Search grounding to retrieve publicly-available records (county assessor, tax records, MLS listings, Zillow, etc.) and extract structured fields like year built, GLA, last sale price, and tax assessed value. No borrower info, loan number, or order metadata is sent — just the address, like typing it into Zillow yourself.
Primary database (PostgreSQL with Row-Level Security), object storage, and authentication primitives. All customer data lives here, scoped by company_id.
Authentication, session management, and organization membership.
Hosting platform for the web application. Customer data passes through Vercel's edge during request handling but is not persistently stored there.
Subscription billing and payment processing. Card data is collected and stored by Stripe directly — Appraiser Machine never sees raw card numbers.
Address autocomplete and geocoding for property records.
Transactional email delivery (order updates, invoices, drip campaigns).
SMS notifications when enabled by the company.
Error monitoring with PII fields scrubbed before transmission.
Email support@appraisermachine.com for AMC-style audit requests, written DPA copies, or to ask about a specific data flow.
See also our Privacy Policy and Security overview.
support@appraisermachine.com
APPRAISER MACHINE