Security & HIPAA
Last updated November 9, 2026
CallVetted analyses phone calls, and some of those calls contain private information. This page explains, without marketing language, what we do to protect them and what you need to do before using CallVetted with health information.
1. HIPAA: where we stand, plainly
There is no official “HIPAA certification”. No government body certifies software, and any company that says otherwise is using a marketing phrase. What HIPAA asks of a service like CallVetted, when it handles health information for a customer, is that it signs a Business Associate Agreement (BAA), protects the data with specific safeguards, and tells the customer promptly if something goes wrong.
If your calls contain protected health information (Medicare and health-insurance calls, for example), please do not upload real calls until we have signed a BAA and confirmed in writing how your data is hosted. Request a BAA and we will send our agreement and answer your security questions.
If your calls contain no health information, no BAA is needed and you can use CallVetted as normal.
2. How we protect calls today
- Encrypted files. Recordings, imported files and evidence are encrypted with AES-256 by CallVetted before they are stored, and travel over HTTPS. Saved logins for connected phone systems are encrypted too.
- Your data stays separate. Every customer's data is kept apart, and every request is checked against the signed-in company.
- Two-factor sign-in. People can add a code from an authenticator app. An owner can require it for everyone in the workspace.
- Lockout and automatic sign-out. Accounts lock for a few minutes after repeated wrong passwords or codes, and people are signed out after 30 minutes of inactivity.
- An access record. Every recording played and every transcript opened is written to the audit log with who and when. Owners and admins can read it in Settings.
- Sensitive numbers removed. Medicare numbers, Social Security numbers and card numbers are removed from transcripts as they are saved, and from our logs.
- No outside AI hears your calls. Transcription runs on our own servers. The AI-written background-check briefs use public findings about businesses, never call recordings or transcripts.
- Your data is not used to train models unless you switch that on.
- You control retention from 30 days up to 10 years, and can delete calls at any time.
- Roles. People only see what their role allows (owner, admin, analyst, viewer).
3. What to know about the limits
- Removing numbers from transcripts is automatic and best-effort. It does not detect names, birthdays or health conditions, and it does not edit the audio. Treat transcripts and recordings as sensitive.
- We have not yet had an independent audit such as SOC 2 or HITRUST. We will pursue one as customers ask for it, and we will say so here when it is done.
- Where your data is stored and which providers handle it is set out in the BAA we sign with you. We confirm those arrangements before you send health information.
4. If something goes wrong
If we find that your data was exposed, we tell you without unreasonable delay, with what we know, what was affected and what we are doing about it. Your BAA sets the exact timeframe; the HIPAA outer limit is 60 days and we aim to be far faster.
To report a security problem or ask how we handle something, write to info@realtalk-ai.com. Please don't include call content in the email.
5. What you are responsible for
HIPAA is a shared job. As the business that owns the calls, you decide who in your team can sign in, you set the retention period that fits your rules, and you make sure callers have been told their calls may be recorded. Turn on two-factor sign-in for everyone, and use Settings → Privacy & compliance → Apply healthcare settings as a starting point.