Security and compliance
Title files carry non-public personal information and money movement. Our controls are written to that standard, and we describe them without embellishment.
All traffic is encrypted in transit with TLS, and data at rest is encrypted with managed keys. We collect what an engagement needs to execute and nothing beyond it, and retention is set per tenant so records leave when your policy says they should.
Every record carries a tenant boundary that is enforced at the data layer, not in application logic. An operator working your files cannot read, reference, or learn from another tenant's data.
Every decision and every message is logged in sequence: the input received, the rule applied, the action taken, the outcome recorded. Engagements are replayable, so a question about a call placed six weeks ago has a factual answer rather than a reconstruction.
Consent is stored as an append-only ledger with source, scope, channel, and timestamp. Withdrawal is recorded the same way and takes effect across every channel and engagement immediately.
Access is role-scoped and least-privilege by default, with single sign-on available and administrative actions recorded. Credentials for connected systems are stored encrypted and scoped to the operations an engagement performs.
Deterministic guardrails sit outside the model. Contact windows, frequency limits, escalation, and stop conditions are structural, so they cannot be negotiated away inside a conversation. AI is a tool within the workflow, it drafts language within an approved plan; it does not choose the plan, and it is not the system of record.
SOC 2 is in progress. We will share the report and our current control documentation under NDA during a security review, and we will tell you plainly what is finished and what is not.
These controls are part of the runtime itself, so read how an engagement executes and records each decision, or how completed work is verified against that record before it is billed.
Request a security review