Spaces

Customer privacy checklist for hosting and data processing chats

This checklist helps hosting and data processing businesses protect customer details in chat, from passwords to account numbers. It shows what an AI agent should never ask for and when a person must check identity.

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

Before you start

Hosting and data customers trust you with their websites, their files and sometimes their own customers' records. A careless chat can expose all of it. People may also write from a new number, pretending to be a client, in the hope that someone will reset a password or hand over access.

Read each point and decide whether your agent and your team already follow it. Write the rules into your agent's notes in plain words. If a rule is unclear, the safest default is always to pass the chat to a person who can check who is writing.

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

[ ] Never ask a customer to type a password into the chat.
[ ] Do not share account details until a person has checked identity.
[ ] Do not discuss another customer's account in any form.
[ ] Ask only for what is needed to help, such as a domain name.
[ ] Pass any request to reset access or change contacts to a person.
[ ] Keep customer data out of notes and handover summaries.
[ ] Tell customers when a person has taken over the chat.
[ ] Limit who on your team can read the chats.
[ ] Keep a clear rule on how long you keep chat records.
[ ] Treat any suspected leak as an urgent handover.

What your agent can safely say

An agent can explain how to reset a password through your own login page, without handling the password itself. It can say that a person will check identity before any change. It cannot confirm who holds an account or reveal what a customer pays.

Write these lines into your notes. A plain sentence such as: For your security, a team member will verify your identity before we change anything, works well and does not insult the customer.

Warning signs in a chat

Pass the chat to a person if you notice any of these.

  • A sender who cannot name the domain but wants access to it.
  • Pressure to act quickly, with threats about a lost client.
  • A request to change the contact email on an account.
  • Questions about who else uses a service.

FAQ

Can the agent confirm that someone is a customer?

It should not. Whether a sender owns an account is a matter for a person who can check your records properly, so the agent hands that step over every time.

What if a customer pastes a password into the chat anyway?

Tell them kindly that it is best to change it, and pass the chat to a person. Do not repeat the password back, and do not copy it into any note.

Do these rules still matter for small customers?

Yes. A small shop's site can be used to send spam or steal visitors' details, which harms them and your own reputation. The same care applies to every account.

More free tools for hosting and data processing providers

Read the guide: Answer hosting and data processing customers in the chat they already use.