Snapshot 283894
Normalized text
Scripts and page chrome removed; this is what change detection compares.
Trust & security Enterprise-grade trust, built for regulated industries. Lippy handles real customer conversations for healthcare, home services, and other businesses where security isn’t optional. Here’s exactly how we protect your data and your callers. Get started→See compliance status ★★★★★Reviews on Google & Trustpilot How we protect your data Engineered in, not bolted on. These are the controls in place today. 01 HIPAA-compliant healthcare offering For healthcare customers, Lippy offers a HIPAA-enabled environment designed to process protected health information separately from standard customer workloads. 02 Encryption in transit and at rest All traffic to and from Lippy is encrypted in transit over TLS. Customer data is encrypted at rest. Third-party integration credentials are stored encrypted. 03 Access controls and least privilege Access to customer data is scoped by organization and role (owner, admin, member, viewer), enforced server-side. Internal access follows least privilege, with MFA required for administrative and infrastructure access. 04 AI transparency Callers are told they’re speaking with an AI assistant. We believe disclosure is the right default for conversational AI. 05 Data handling and retention Customer data is logically separated by organization and retained to operate the service, then deleted in line with our agreements. Subprocessors are vetted and published, and a DPA is available. 06 Credential and secret management Secrets and integration tokens live in a centralized secrets store with rotation procedures, never in source control. Production access is gated and audited. Compliance status Compliance you can verify. HIPAA✓ Compliant offering · BAA available Available to healthcare customers under an executed BAA with HIPAA features enabled. Continuous monitoring✓ Active Infrastructure, dependency, and vulnerability monitoring run continuously across our cloud accounts. DPA & subprocessors✓ Published A Data Processing Agreement and a current list of subprocessors are publicly available. Policies & documentation Read the fine print. Privacy Policy Data Processing Agreement Subprocessors Terms of Service Security question? Ask us. We’re happy to walk through our architecture, sign a BAA, or answer your security questionnaire. Get started→