← Table of Contents · Page 435 of 868
RESPONSIBLE AI, COMPLIANCE, AND RISK
Part 6 of 10
RETENTION AND DELETION
Responsible systems keep data only as long as there is a good reason.
Decide how long conversation records, traces, and stored memories should be kept, and delete them automatically when that time ends.
Give people a way to ask what is stored about them and to have it removed where the rules allow.
Test the deletion process, since a promise to delete is only worth something if it really works.
ACCOUNTABILITY IN PRACTICE
Every agent needs named humans who answer for it.
Decide who owns the agent, who approves changes, who reviews incidents, and who can switch it off.
Write the names and the roles down, and make sure the people know.
When something goes wrong, a clear owner is the difference between a fix that happens today and a problem that nobody feels responsible for.
TALKING TO USERS ABOUT LIMITS
Be open with users about what the agent is and what it cannot do.
Tell them they are talking to an automated system, explain what kinds of mistakes it can make, and show how to reach a person.
Honest framing sets realistic expectations and builds trust, which protects both the users and your organization.
REPORTING PROBLEMS
Make it easy for staff and users to report concerns about the agent's behavior, and take every report seriously.
Give each report a number, record what was decided, and tell the person what happened.
A visible, respectful reporting path often surfaces problems long before any audit would.
Advertisement
Read Aloud:
0:00 / 0:00