Spaces

Looking after user and account details in your support chats

This checklist helps a software company protect user details in chats: no passwords, minimal data, careful handling of screenshots and a clear route for deletion requests.

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

Before you start

Your users trust you with their work: documents, customer lists, sometimes payment details. A support chat can leak that trust in small ways, such as a pasted password or a screenshot with private data visible. You do not need a legal team to avoid most of it.

Use this list to set simple habits for your team and your AI agent. Tick what you already do, and add the rest to your written instructions. This is general guidance, so for legal questions about data rules, speak to a qualified adviser.

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

[ ] Never ask a user for their password, in any chat, for any reason.
[ ] Ask for the workspace name or email, not card numbers or full account data.
[ ] Tell users to cover private details before sending a screenshot.
[ ] Verify who someone is before discussing a specific account.
[ ] Send account changes only to the email already on the account.
[ ] Pass data export and deletion requests to a named person.
[ ] Tell your agent never to share one customer's data with another.
[ ] Remove private details from chats you copy into your bug tracker.
[ ] Limit which team members can read old conversations.
[ ] Write a short plan for what to do if a user's details are exposed.

Small habits that help most

The biggest wins are boring. Never ask for passwords. Ask for the least you need. Pass anything about identity or deletion to a person. Most privacy slips in software support come from helpfulness, such as a founder trying to be quick and asking for a login 'just to look'.

Tell users what you will do with what they share. One plain sentence, such as 'I only need the workspace name to find the problem', calms people and sets a good example.

  • Offer to look at a workspace from your side instead of asking for access.
  • Use a screen recording tool that hides private fields.
  • Delete test chats that contain real customer data.

FAQ

Can our AI agent look up a user's account?

Only if you have set that up on purpose, with a clear limit on what it can see. Many teams keep account lookups with a person, and let the agent answer general questions.

What should we do when a user pastes a password into chat?

Tell them kindly to change it right away, and remove the message from your records if you can. Remind them that you will never need it, then move on to solving their problem.

Is this checklist legal advice?

No. It covers everyday good habits. For questions about data protection law or contracts with your customers, ask a qualified adviser who knows the rules where you operate.

More free tools for software companies

Read the guide: Answer your users' messages with an AI agent.