Spaces

Customer privacy checklist for hosting and data processing chats

This checklist helps hosting and data processing companies look after customer details in chat, from passwords and server logs to files and account ownership. It is written for owners and support leads.

Runs in your browser. Nothing you enter is sent anywhere or saved.

Before you start

Hosting and data processing firms hold more of their customers secrets than most businesses: site files, databases, mailboxes, payroll and client records. A careless chat can leak a password or confirm account details to the wrong person, which is a bigger risk than a slow reply.

Go through each point and decide how your company handles it, then write the rule down for staff and for your AI agent. Revisit it when your tools change. Where a point touches legal or contract matters, ask your own adviser rather than relying on a general list.

Tick each one as you go. 0 of 10 done.

[ ] Ask customers never to paste passwords or keys into a chat.
[ ] Give a safe way to share a log or file instead.
[ ] Confirm who is writing before sharing any account detail.
[ ] Pass every owner change or login reset to a person.
[ ] Do not confirm which other customers share a server.
[ ] Limit who on your team can read customer chats.
[ ] Mask personal details when quoting a chat in a ticket.
[ ] Set how long you keep chats and say so in your policy.
[ ] Send data requests from customers or authorities to a person.
[ ] Test what your agent says when asked for another account detail.

What to tell customers

Customers will accept caution when you explain it in plain words. Something like: For your protection, we cannot share account details in chat until we confirm who you are. A colleague will check with you now.

That message is firm and polite. It protects the real owner and shows an impostor nothing at all.

Common slips to watch for

These are the leaks we hear about most from small providers.

  • A support person reading a temporary password aloud in a chat.
  • Confirming a customer plan, address or renewal date to anyone who asks.
  • Pasting a full customer record into a team thread to get quick help.
  • Keeping old chats that mention keys and logins for years.

FAQ

What should the agent say if someone asks for another customer details?

It should decline politely, say it cannot share account information in chat, and hand the request to a person. It should not confirm that the account exists or who owns it.

Is it safe for the agent to see site logs?

Only if you decide it should, and only logs without personal details where possible. Ask your own adviser about your legal duties, because they differ by country and by the kind of data.

How do I handle a customer who pastes a password anyway?

Ask them to change it straight away, explain why, and remove the message if your tools allow. Then tell them the safe way to share access next time.

More free tools for web hosting and data processing companies

Read the guide: Answer hosting and data processing questions without a ticket queue.