Borrower data, handled like it matters.
The assistant sits between borrowers, an AI model and your loan system. Each hop is locked down, and sensitive digits never travel further than they must.
Safeguards
SSN checked by the server
Keyed digits are consumed by our server and checked against Lendisoft. They are not passed to the AI, written to logs or stored in the call record. On the phone line, we confirm that keypad tones in the call audio do not reach the AI before any live calls.
Recordings muted during entry
On the phone line, the caller’s audio is muted in the stored recording while the zip read-back and SSN are entered, with a safety margin either side.
Encrypted at rest
Lendisoft tokens, provider keys, voice messages and call audio are sealed with AES-256-GCM, each bound to its own record. Keys can be rotated without downtime.
Controlled Lendisoft access
Staff sign in to Lendisoft as themselves, including two-factor codes. Phone calls use a dedicated service login per lender. Passwords are never stored; tokens are kept sealed.
Roles and permissions
Who can make test calls, see loan details, manage agents or review messages is set per role, and enforced by the server.
Audit and redaction
Sign-ins, Lendisoft requests and tool actions are recorded. Raw and redacted transcripts are kept apart, and only redacted text is ever exported.
Signed phone traffic
Every telephony webhook and stream handshake must carry a valid signature, and each call gets a one-time token. No customer data is placed in call parameters.
Only the verified loan
After verification, every action works on that one loan. The assistant never accepts an account number from the AI.
Safe by configuration
Production refuses to start on unsafe settings: plain http, example secrets, or unencrypted storage. Payment posting by voice is removed entirely.
Your script’s rules, enforced on every call.
These behaviours come straight from the lender’s script and are built into the call flow, not left to the AI’s judgement. Your compliance counsel reviews the script and its Spanish lines before launch.
- AI disclosure up front. The caller hears that it is a virtual assistant before anything else.
- Recording notice in every greeting, as the script requires.
- Debt disclosure only to the right party, after verification and name confirmation.
- No card or bank numbers by voice. A caller who starts reading one out is stopped.
- Promise and extension terms read word for word, and a promise is never presented as stopping collection.
- Consent captured for a new mobile number before it is saved.
Frequently asked questions
Where is call data stored?
Loan data stays in Lendisoft. Call records, transcripts and voice messages are kept in the assistant’s own database, separate from Lendisoft, with audio sealed on disk or in S3 with KMS encryption in production.
Which certifications do you hold?
We don’t claim any third-party certification today. We’re happy to walk your security team through the design, configuration guards and data handling described here, and to answer your vendor questionnaire.
Can we choose how long recordings are kept?
How long recordings and transcripts are kept, and whether recordings may ever be used for training, are decisions we agree with you and your counsel before launch.
Have a security review to run?
Send us your questions with a demo request and we’ll bring the right answers.