Trust
FirmOps builds and manages a firm brain inside a live practice. This page says what we host, what stays in your systems, who can see it, and what we will not claim without proof.
Case files, email, documents, billing, and phones stay in the systems the firm already runs: Clio, Filevine, SmartAdvocate, Gmail or Microsoft 365, Dropbox, QuickBooks, and the rest of that stack. FirmOps does not become the system of record. The brain reads from those systems and writes back to them when a person at the firm approves. Matter content is not copied into a FirmOps case file.
FirmOps hosts the marketing site (firmops.io), the firm-brain connection (mcp.firmops.io), and the credentials needed to call the firm's APIs. Demo and contact notes you send to FirmOps live with FirmOps. Files you upload into Demand from the File stay in that vendor workspace. See Privacy for that plugin.
Each attorney and staff member signs in as themselves, so the AI sees only what that person may see. FirmOps people get the access required to build and run the brain for that firm. Access is per person, not a shared firm login that bypasses the firm's own permissions.
The brain drafts and stages. A named person at the firm releases. Emails, texts, filings, portal messages, and public pages do not go out on their own. Read-only is the default until that person says otherwise. This is the same operating rule as Ethics.
firmops.io is hosted on Vercel. The firm-brain connection at mcp.firmops.io is hosted on Railway. Both are reached over HTTPS. We do not name other cloud vendors here because we cannot verify them from the public site and deploy config.
Client data and conflicts come first. We do not treat a new connection as a green light to read or write across the stack. The brain does not replace attorney judgment. Phones stay human. The full operating rules live on Ethics.
Public FirmOps URLs use HTTPS, so data moving between your browser and firmops.io, and between connected tools and mcp.firmops.io, is encrypted in transit. This page does not claim encryption at rest. We have not published that proof here.
On the marketing site: Vercel hosts the pages; Google Analytics 4 and Vercel Analytics load after the page to count visits; Zoom Scheduler handles demo booking; Stripe handles subscription payments. On the firm brain: Railway hosts mcp.firmops.io. The firm's own vendors (Clio, Google, Microsoft, Dropbox, Intuit, and others) stay the firm's vendors. We do not list a longer subprocessor roster we cannot verify.
We do not currently claim SOC 2, ISO 27001, a HIPAA BAA, or similar certifications. If that changes, this page will say so. MCP is a connection protocol, not a security guarantee. Scoped permissions, logging, and a person at the firm on every send are how the work is run.
Not legal advice. Operating rules: Ethics. Legal pages: Privacy and Terms. To see the model on a live bottleneck, book a 30-minute live demo.