Animal control worries that a cloud vendor might retain municipal prompts containing address and case details. What risk does that concern highlight?
Select an answer to reveal the explanation.
Short Explanation
If the cloud keeps your prompts, it may keep addresses and case scraps too. That’s a privacy and contract problem—read the retention terms before the shelter’s notes become someone else’s training fuel.
Full Explanation
Worry that a cloud vendor might retain municipal prompts containing address and case details highlights privacy and contractual risk of cloud-hosted model prompt retention. Animal-control case text often includes locations and personal circumstances; if the provider stores prompts for training, safety review, or logs, civic data may leave intended custody unless contracts forbid it. Local disk failure modes on kiosk SD cards are a different reliability topic and do not capture the vendor-retention concern raised in the stem. Buying InfiniBand switches for every shelter is unrelated networking spend that does not mitigate prompt-retention risk. Claiming data processing agreements are irrelevant for civic data is the opposite of sound municipal practice. Exam caveat: cloud generative services require explicit review of prompt and output retention—not only encryption in transit or at rest. Operational check: read retention and training-use clauses before pilot expansion, prefer zero-retention or municipal-tenant isolation options, minimize addresses in prompts, redact before inference when feasible, involve procurement and legal before shelter staff paste case notes into a vendor chat, and verify deletion SLAs with a test prompt that can be audited.