How is client PII protected inside MiOpsAI for a wealth management firm?

Client personally identifiable information that lives inside MiOpsAI (names, email addresses, phone numbers, mailing addresses, meeting notes, coordination context) is encrypted at rest with per-tenant AES-256 keys and in transit with TLS 1.3. Every tenant is fully isolated, other MiOpsAI customers cannot see your client data, and we do not train shared AI models on your tenant data.

What is explicitly not in MiOpsAI: Social Security numbers, account numbers, driver's license numbers, bank routing information, birth dates for verification purposes, and any of the sensitive identifiers your custodian or account opening platform holds. Those live where they belong. When a client sends any of those through an operational channel by mistake, LizziAI is trained to recognize the pattern, redirect the message into the appropriate secure channel, and flag the incident so the advisor can follow up appropriately.

Access controls are role-based. Advisors see their own client relationships, client service associates see the queue assigned to them, the firm principal sees everything, and outside professionals (accountants, estate attorneys, insurance agents) see only the specific threads you scope them into. Every read and write is logged with user, timestamp, and action.

For clients who prefer to keep certain communications encrypted end-to-end, MiOpsAI supports handoff into a secure client portal (yours, or one of the standard advisor portal providers) rather than continuing sensitive conversations in email. The operational thread records that the handoff happened, not the content of what was discussed in the portal.

On the certification side, MiOpsAI is working toward SOC 2 Type II on the 2026 roadmap. Our underlying AWS infrastructure is SOC 2 Type II certified today. Two-factor authentication is available for every user and required for principal and admin roles. See the security and compliance FAQ set for the full control list.