cd /news/ai-safety/i-wrote-about-the-notion-ai-incident… · home › topics › ai-safety › article
[ARTICLE · art-169093] src=dev.to ↗ pub= topic=ai-safety verified=true sentiment=↓ negative

I wrote about the Notion AI incident: a vendor promised not to retain chat data, but it was stored and exposed. Read the article:

A developer published an analysis of a Notion AI incident in which a vendor contractually promised zero data retention of chat data, yet chats were stored and subsequently exposed. The writeup examines how the retention guarantee failed in practice despite being written into the agreement.

by read1 min views1 publishedNov 13, 2026

Zero Data Retention Was in the Contract. Why Did Notion AI Chats Remain Stored? inclinq_Founder inclinq_Founder inclinq_Founder Follow Nov 13 Zero Data Retention Was in the Contract. Why Did Notion AI Chats Remain Stored?

#

cybersecurity

#

dataprivacy

#

notion

#

softwareengineering Add Comment 5 min read

source & further reading
dev.to — original article I built a CLI harness that strips JS/TS function bodies with Babel AST to save 80% context tokens Rolling Out Passkeys Without Locking Users Out The Prediction Succeeded. The CLI Still Failed.
── more in #ai-safety 4 stories · sorted by recency
── more on @notion 3 stories trending now
sponsored brought to you by zahid.host 4,200+ EU-deployed projects
reading about agents? ship yours in a single git push.

Run your AI side-project on zahid.host

EU-based hosting, git-push deploys, automatic HTTPS, no cold starts. Free tier with a custom domain — perfect for shipping the agent you just read about.

$git push zahid main
→ Live at https://your-agent.zahid.host ✓
Get free account → Pricing
from €0/mo · no card required
LIVE [news/i-wrote-about-the-no…] indexed:0 read:1min 2026-11-13 · —