Most chat security is administration, not cryptography
Your vendor encrypts the transport and documents its posture; what actually goes wrong at most companies is closer to home — a shared login, an ex-employee who still has access, a credit card number pasted into a transcript. Those live in YOUR settings, and they are all fixable on day one.
One human, one account — always
A shared "support@" agent login feels convenient and destroys three things at once: accountability (who said this?), coaching (whose transcript is this?), and offboarding (you cannot revoke one person from a shared credential without locking out everyone). Per-agent accounts are the single highest-value security setting in the product. There is no legitimate exception.
Least privilege, by role
- Agents answer chats — they do not need billing, deployment settings, or account administration.
- Admins configure — and there should be more than one (bus factor) but not many (audit surface).
- Departments as boundaries: routing scopes not just workload but visibility — the seasonal helper answering shipping questions has no business in billing conversations.
Offboarding is a same-day ritual
The day someone leaves the team, their agent account is disabled — not "soon," not "at the end of the sprint." Put it on the same checklist as email and VPN. Chat access is customer-facing: a forgotten account is not just data exposure, it is someone able to speak AS your company. Quarterly, list every active agent login and name its human; any orphan gets disabled the same day too.
Keep secrets out of the transcript
Transcripts persist — that is their value and their risk. Set the team rule and put it in the canned library: never ask for full card numbers, passwords, or government IDs in chat; move those flows to the systems built for them (your payment page, your password reset). When a customer pastes one unprompted, the polite script is honest: "I've noted the last four digits and I'd recommend not sharing the full number in chat — let me take care of this another way." Your data-retention and deletion duties (GDPR requests, the delete-visitor flow) get lighter with every secret that never entered the record.
Know your vendor's posture — from the source
Finally, read your chat vendor's actual trust documentation rather than assuming: transport encryption, data processing terms, permissions model, deletion paths, and deployment options. MyLiveChat's is published plainly on the trust & compliance page — including what is offered, what is not, and the self-hosted option for higher-control workloads. A vendor that states its boundaries honestly is telling you it knows where they are.