We classify. We don't keep.
AMDelete sits in the path of your answered calls, so it is built to hold as little as possible and to fail safely.
Call audio
The adapter on your dialer sends the called party's audio for the opening seconds of an answered call. The service scores it in memory and discards it. We do not record calls, and we do not receive phone numbers, lead fields or agent audio.
If you choose to help train the detector, you can opt in under Settings. That consent is recorded with its version and date, and you can withdraw it at any time.
What we store
- Per call: a one-way hash of an opaque reference, the decided class and the model version, for billing and analytics.
- Per call, once agents have dispositioned it (unless you turn this off): the disposition's VICIdial meaning, a call-length range and who hung up, under the same hash. Kept 180 days.
- Per hour: counts per installation and outcome, and VICIdial AMD counts on your campaigns still using it.
- Per dialer: its profile (hardware, versions, and campaign, carrier and AMD settings).
- Your account, team, installations, payments and audit log.
What your dialers report
Everything a dialer sends us is something you can print on the dialer first: amdelete-ctl profile shows its profile, and amdelete-ctl outcomes preview shows the next batch of call outcomes.
- Dialer profile, at install and daily: CPU, memory and load, OS, Asterisk and VICIdial versions, channel drivers, VICIdial AMD settings, counts of servers, agents logged in and campaigns, settings of campaigns on an AMD route, and carrier protocols and codecs. Carrier hosts, logins and secrets are read in memory for their codec lines and never sent.
- Call outcomes, about half an hour after each AMDelete call: our decision, whether an agent took the call, the disposition code if it is one of VICIdial's stock no-contact or machine codes (any other status is sent as
OTHER), its Human Answered, Customer Contact and Answering Machine flags, a call-length range and who hung up. No call id, lead, list, phone number, agent name, comments or recording. - VICIdial AMD counts, hourly, for your campaigns still on VICIdial AMD: how many calls it passed or closed, and what agents found on the ones it passed. Counts only, no calls.
Our console refuses any outcome record with a field outside that list. Outcome reporting is on unless an account owner turns it off in Settings, and a dialer's owner can turn it off on that dialer with amdelete-ctl outcomes off. Calls from a period when it was off are never sent later.
Keys and transport
Every dialer gets its own classify key and a separate test key, both limited to your account and by default to the dialer's public address. Keys are stored only as hashes and rotate automatically. All traffic uses TLS.
Code on your servers
The installer is a readable shell script and Python, with no compiled binaries. Releases are signed offline with an Ed25519 key, and amdelete-ctl update refuses anything that doesn't verify. Nothing updates itself: you decide when to install a release.
Accounts
Passwords are hashed with Argon2id or bcrypt. Two-factor authentication (TOTP) is available to every user and required for our own operators. Sessions are secure, HTTP-only cookies.
Reporting a problem
Email support@amdelete.com. Please include enough detail for us to reproduce the problem.
See it before we do
Run sudo amdelete-ctl profile or sudo amdelete-ctl outcomes preview on any dialer to print exactly what it will send. Nothing is sent that those commands don't show.
Fail-safe by design
- Unsure calls go to agents
- Service problems use your dialer's local fallback route
- Credit exhaustion never drops calls
- Local kill switch with no reload
Your obligations
You remain responsible for call-recording consent and for the abandonment and dead-air rules that apply to your campaigns (for example the US Telemarketing Sales Rule). AMDelete's listening window adds time before an agent joins; choose your campaign settings accordingly.