Security
You trust us with your calls, your customers and your payments. Here's how we protect them.
NeverMiss is in early access. This page describes how the service is built and the commitments we make to every customer. If anything changes, we will update this page and tell customers before the change takes effect.
Data protection
- Encryption: all traffic uses TLS (HTTPS), and stored data is encrypted at rest.
- Isolation: each business's data is kept separate, and staff access is limited to support you request.
- Payments: handled by Stripe. NeverMiss never sees or stores card numbers.
- Your data, your call: export it any time. It's deleted within 30 days of cancellation.
- No training on your data: conversations are never used to train public AI models.
Accounts and access
- Two-factor authentication on every login
- Separate accounts for each staff member, with roles
- An activity log of who viewed or changed what
Calls and texts
- Calls and texts run on providers that hold SOC 2 reports.
- Business-texting registration (A2P 10DLC), automatic STOP and HELP handling, and quiet hours.
- Call recording is optional. When it's on, the assistant announces it at the start of each call, because several states require every party's consent.
- The assistant says it's an AI assistant when asked, and hands off to a person on request.
Website
This website is served only over HTTPS with HSTS, a strict Content Security Policy and other protective browser headers. It uses no advertising cookies or third-party trackers.
Certifications
NeverMiss itself is not yet SOC 2 certified. We'll publish our status here as that work progresses.
Report a vulnerability
If you believe you've found a security issue, please tell us through the contact form and choose "Security report". Please give us a reasonable time to fix it before sharing it publicly. We won't take action against good-faith research.