AI Pulse · AI Trends Pulse

Last week Google’s index turned up something uncomfortable: Claude’s public Share links and Artifacts, the ones users assumed were unlisted but not searchable, sitting right there in search results. VentureBeat reported that exposed items included API keys, cap tables, resumes full of personal information, and client dashboards. Most links have since been scrubbed, but the damage is a reminder that “unlisted” and “private” are not the same thing.

If you run a business and your team uses AI tools to draft, share, or collaborate on anything sensitive, this matters. A share link feels convenient. It looks harmless. But if it is not explicitly protected, search engines can and will crawl it. That means confidential data can end up in front of anyone who types the right query. The fix is straightforward but not automatic: treat share links like you would a public URL. Do not put anything in them you would not want a competitor, a journalist, or a regulator to read.

This is the kind of exposure risk we build guardrails for inside an AI command centre, where access controls and audit trails are not optional extras. The broader lesson is simpler. If your workflow involves pasting sensitive information into a tool and hitting “share”, pause. Check the privacy settings. Ask whether the link is truly private or just hard to guess. Hard to guess is not the same as secure, and Google just proved it.