Tenant isolation
Every customer record is tied to its own workspace. Server authorization and database policies are designed to keep one customer’s data from another.
Security and privacy approach
Protect the context. Respect the boundary.
MairyAI is designed to keep data purposeful, customer workspaces separate and critical boundaries fail-safe when a permission or connection is not in place. This page is not a certification or legal promise.
Minimum necessary data
Clear call outcomes are the default. Complete transcripts and recordings stay separately disabled unless an approved workflow enables them.
Encrypted boundaries
Events, customer connections and optional call content use separate protections. Secrets stay on the server.
Audited access
Sensitive reads, exports, deletion and support access require explicit permission and leave an audit trail.
Bounded retention
Identifiable operational records have a 90-day default. Optional redacted transcripts and recordings have a separate 30-day default and maximum.
Independent calls
The telephone service is designed to keep operating if the portal, CRM or another business system is unavailable.
Optional call content
Optional call content is a deliberate choice.
Audio and redacted transcript controls are separate for each customer and remain unavailable until the required policy and technical controls are in place.
Requires an approved disclosure and consent policy, redaction, encryption, access controls and a clear deletion process.
Requires its own consent decision, policy review, encryption and access controls. It is not described as automatically redacted.
A considered starting point
Review the exact customer workflow, not a generic promise.
We help you shape the standards, handoffs and follow-through that make every first conversation feel considered from the outset.