A Privacy Policy Is Not a Chatbot Info Card

隐私政策不等同于聊天机器人信息卡

Decide what a customer needs to know before the first message, then put it beside the chat box. If the answer is buried in a privacy policy, the customer has to leave the conversation, find the right clause, and translate legal language before deciding whether to continue. That is too much work for a five-second decision. 在用户发送第一条消息之前，先确定他们需要了解什么，然后将其放在聊天框旁边。如果答案隐藏在隐私政策中，用户必须离开对话，找到相关条款，并解读法律术语，才能决定是否继续。对于一个五秒钟就能做出的决定来说，这太麻烦了。

A chatbot info card gives support leaders a practical alternative: one short reference for what the bot can do, where it may be wrong, what happens to conversation data, and how to report a problem. Singapore’s Infocomm Media Development Authority sets out this pattern in its Transparency Guidelines for Generative AI Chatbots. The guidelines are voluntary. They do not impose obligations or replace duties under other laws or sector rules. What they offer is an operator-friendly structure for telling people what matters at the moment it matters. 聊天机器人信息卡为支持团队负责人提供了一种实用的替代方案：一份简短的参考指南，说明机器人能做什么、哪里可能出错、对话数据如何处理以及如何报告问题。新加坡资讯通信媒体发展局（IMDA）在其《生成式人工智能聊天机器人透明度指南》中提出了这一模式。这些指南是自愿性质的，不强制要求，也不取代其他法律或行业规则下的义务。它们提供的是一种对运营者友好的结构，旨在让用户在关键时刻了解关键信息。

The Gap a Privacy Policy Cannot Close

隐私政策无法弥补的缺口

A privacy policy answers only part of the customer’s question. It may explain which data is collected, who receives it, and how long it is kept. It rarely says whether the bot can check current stock, whether it may give an incorrect answer, which questions need a human, or where to report a bad response. Those are operating decisions, not legal footnotes. A shopper deciding whether to trust a returns answer needs them in one scan. A support manager also needs one maintained source of truth instead of four different pages owned by legal, product, security, and customer service. The distinction: the privacy policy holds the full legal detail. The info card summarises the practical choices a user must make before and during the conversation, then links to the policy for more. 隐私政策只能回答用户部分问题。它可能解释了收集哪些数据、谁会接收数据以及保存多久。但它很少说明机器人是否能查询库存、是否可能给出错误答案、哪些问题需要人工介入，或在哪里报告糟糕的回复。这些是运营决策，而非法律脚注。购物者在决定是否信任退货答复时，需要一眼就能看到这些信息。支持经理也需要一个统一的“事实来源”，而不是由法务、产品、安全和客服部门分别维护的四个不同页面。区别在于：隐私政策包含完整的法律细节，而信息卡总结了用户在对话前和对话中必须做出的实际选择，并提供链接以供查阅详细政策。

Answer Four Questions, Not Every Question

回答四个核心问题，而非所有问题

IMDA encourages at least one substantive disclosure in each of four areas. For a customer-service chatbot, that becomes a manageable editorial checklist: IMDA 鼓励在四个领域中至少进行一次实质性披露。对于客服聊天机器人，这变成了一份可操作的编辑清单：

• What can this chatbot do? Name the tasks it handles and the boundaries that matter. “Answers questions from our published shipping and returns information” is useful. “Your intelligent shopping assistant” is not. 这个聊天机器人能做什么？ 列出它处理的任务及相关边界。“回答我们已发布的物流和退货信息相关问题”是有用的描述，而“您的智能购物助手”则不然。
• How reliable and safe is it? State the important limitation in plain language. If answers can be wrong or out of date, say so. If prices, stock, medical, legal, or financial decisions need verification, make the next step explicit. 它有多可靠和安全？ 用通俗易懂的语言说明重要限制。如果答案可能错误或过时，请直说。如果价格、库存、医疗、法律或财务决策需要核实，请明确告知后续步骤。
• How is conversation data used and protected? Summarise what is collected, who can access it, whether it is used for model training, and what controls the user has. Link to the privacy policy for retention periods and full terms. 对话数据如何使用和保护？ 总结收集的内容、谁可以访问、是否用于模型训练以及用户拥有哪些控制权。关于保留期限和完整条款，请链接至隐私政策。
• How can someone report a problem? Give a real channel and set an expectation. Explain what kinds of issues can be raised and what acknowledgement or follow-up the user should expect. 如何报告问题？ 提供真实的渠道并设定预期。解释可以提出哪些类型的问题，以及用户应期待什么样的确认或后续处理。

The bar is specificity. “We take safety seriously” gives a customer nothing to act on. “This chatbot can make factual errors; verify important product, price, and policy information before relying on it” changes behaviour. 关键在于具体性。“我们非常重视安全”无法让用户采取任何行动。而“此聊天机器人可能会出现事实错误；在依赖重要产品、价格和政策信息前请务必核实”则能改变用户的行为。

Place the Decision Before the Conversation

在对话前做出决定

A perfect page that nobody sees is not useful disclosure. IMDA encourages a high-level safety statement and a clearly identifiable link to the info card at first use, before the customer starts chatting. The card should remain reachable from within the interface afterward. For most teams, that does not require a new consent flow or a long modal. A short sentence near the opening prompt and a persistent information link can do the job. The linked page can use headings, bullets, and expandable sections so customers see the essentials first and supporting detail when they want it. 一个没人看的完美页面不是有效的披露。IMDA 鼓励在用户首次使用、开始聊天之前，提供一份高层级的安全声明以及指向信息卡的清晰链接。此后，该卡片应在界面内保持可访问状态。对于大多数团队来说，这不需要新的同意流程或冗长的弹窗。在开场提示附近加一句简短的话和一个持久的信息链接即可。链接页面可以使用标题、项目符号和可折叠部分，以便用户先看到要点，并在需要时查看详细信息。

Use the same core card across web and mobile when the bot behaves the same way. If capabilities or data practices differ by channel, name the differences instead of making the customer guess which version they are using. 当机器人在网页和移动端表现一致时，请使用相同的核心卡片。如果功能或数据实践因渠道而异，请明确说明差异，而不是让用户去猜测他们正在使用哪个版本。

Give the Card an Owner and a Review Trigger

为卡片指定负责人并设定审查触发机制

The page becomes operational only when someone owns it. Put one support or product leader on the review, record the last-updated date, and define the changes that reopen it: a new model, a new capability, a material guardrail change, a new data use, or an unexpected customer use case. Do not wait for an annual policy review when a meaningful change happens in the meantime. Equally, do not create busywork for routine infrastructure changes that do not alter behaviour or safety. The question is simple: would this change affect how a reasonable customer decides to use the chatbot? 只有当有人负责时，该页面才能发挥作用。指定一名支持或产品负责人进行审查，记录最后更新日期，并定义触发重新审查的变更：如新模型、新功能、重大的安全护栏变更、新的数据用途或意料之外的用户用例。当发生重大变化时，不要等待年度政策审查。同样，也不要为不改变行为或安全性的常规基础设施变更增加额外工作。问题很简单：这种变化会影响理性用户决定如何使用聊天机器人吗？

A One-Hour Review for Support Leaders

支持负责人的“一小时审查”

Open the chatbot as a first-time customer and run this review with support, product, and whoever owns privacy: 以首次用户的身份打开聊天机器人，并与支持、产品及隐私负责人共同进行以下审查：

• Can a customer tell what the chatbot is for before sending a message? 用户在发送消息前能知道聊天机器人的用途吗？
• Can they find one concrete limitation or precaution? 他们能找到一个具体的限制或预防措施吗？
• Can they understand the main data practice without reading the full privacy policy? 他们能在不阅读完整隐私政策的情况下理解主要的数据处理方式吗？
• Can they reach a person or reporting channel when something goes wrong? 当出现问题时，他们能联系到人工或找到报告渠道吗？
• Can the team name who updates this information after a meaningful change? 团队能明确在发生重大变更后由谁来更新这些信息吗？

Any “no” is a drafting task, not a reason to add another generic disclaimer. Start with the four answers, write them in the language your support team already uses with customers, and cut every sentence that does not change a decision. 任何“否”的回答都是一项起草任务，而不是添加另一个通用免责声明的理由。从这四个答案开始，用你的支持团队与客户沟通时使用的语言编写，并删掉每一句不能改变用户决策的废话。

Where HoverBot Fits

HoverBot 的定位

HoverBot helps teams ground customer conversations in their own catalogue, policies, and documentation, while keeping a clear path to human support. The same operating discipline applies to transparency: define the answerable scope, make the limits visible, and keep the customer in control of what happens next. Review the first-use experience in your current chatbot, then request a demo to see how grounded answers and human handoff can fit your support workflow. HoverBot 帮助团队将客户对话建立在自身的目录、政策和文档基础上，同时保持通往人工支持的清晰路径。同样的运营准则也适用于透明度：定义可回答的范围，使限制可见，并让客户掌控后续流程。审查您当前聊天机器人的首次使用体验，然后申请演示，了解基于事实的回答和人工接管如何融入您的支持工作流。