How does MiOpsAI protect customer account data at a waste hauling operation?

Customer account data at a waste operation (name, service address, contact info, service level, contract terms, service history) is treated as sensitive operational data and lives inside your isolated MiOpsAI tenant with per-tenant AES-256 encryption at rest and TLS 1.3 in transit. Other MiOpsAI customers cannot see any of your account data, and we do not train shared AI models on your tenant data.

Access controls are role-based: CSRs see the queue and accounts assigned to them, dispatchers see route-level and driver-level views, the operations manager sees everything, and outside vendors or municipal contacts see only what you explicitly scope them into. Every read and write is logged with user, timestamp, and action, so if a question ever comes up about who touched what, the answer is one query away.

Billing-sensitive data (bank account numbers, credit card numbers, payment methods) does not live in MiOpsAI. Your billing platform holds that data and MiOpsAI never touches it. When a customer sends a payment question through the operational channel, LizziAI routes them into the appropriate payment channel (customer portal, phone billing, mailed check) without exposing or storing payment credentials.

For commercial and municipal accounts, contract terms and pricing are competitively sensitive, and MiOpsAI treats them accordingly. Contract PDFs stored in MiOpsAI operational context are per-tenant encrypted, access-controlled, and logged. If you would rather keep contract documents in your existing document management or contract management system and just reference them from MiOpsAI operational threads, that works too.

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. See the security and compliance FAQ set for the full control list.