

The chat window on a site: your colour, your logo, the operator's face beside each reply.
Chatdozo is a live chat plugin for WordPress: a chat window on your site and an inbox in your WordPress admin. A visitor writes, you answer from the inbox; if you are away, they write anyway and the chat reaches you by email, and your reply goes back to them by email.
Nothing leaves your server. Conversations are stored in your own database, the people who answer are your own WordPress users, and the widget loads with no outside calls: no chat service in the middle, no account to make, no data sent to Chatdozo or anyone else.
Everything in this plugin is free and complete:
Chatdozo Pro is a separate plugin from chatdozo.com that installs beside this one and adds: an AI receptionist that answers from your own website day and night and hands over to a person when it matters; a live globe of who is on your site with a Say hello button and automatic messages; Reports and a Monday email; and the inbox as an app on your phone with a ping when a visitor writes. It uses everything you have set up here.
This plugin works entirely on your own server. One optional connection exists:
Freemius (https://freemius.com), the licensing and update library bundled with the plugin. At activation it asks whether it may send a note when the plugin is activated, updated or removed, so you get security updates and we hear when something breaks. If you allow it, it sends your site address, the WordPress and plugin versions and, if you choose, your email address; never any chat content. If you skip it, nothing is sent and everything works the same. Terms: https://freemius.com/terms/ · Privacy: https://freemius.com/privacy/
Chatdozo Pro, the separate plugin, adds its own connections (an AI provider for the Assistant: OpenAI, or Chatdozo AI at ai.chatdozo.com; and the browser vendors’ push services for the phone app), and documents them in its own readme.
Chatdozo stores chat messages, the visitor’s name and email when they give them, the page they were on, their browser and a hash of their IP, in your site’s database, so you can answer them. It keeps one random token in the visitor’s browser (localStorage, with a cookie as fallback, a year) so a returning visitor sees their own conversation; the token identifies the browser, not the person. Delete any conversation from the inbox, or set an automatic retention period under Settings Privacy. Nothing is sent to any outside server; see External services for the one optional exception.