Key Takeaways
Five AI Risks That Can Get You Fired—And How to Avoid Them

- Most AI assistants use your prompts to train future models by default
- 52% of workers have pasted sensitive company data into AI tools
- AI companies review flagged conversations with human moderators
That prompt you just typed into ChatGPT? It's probably sitting in a training dataset somewhere. And if you included customer emails, source code, or salary information, congratulations: you've just contributed to the next AI model's knowledge base. A Cyberhaven study found 52% of workers have pasted sensitive company data into AI tools, which explains why CISOs are losing sleep.
Fast Company recently catalogued eight ways AI assistants can backfire on users. The list reads like a postmortem of every AI-related HR incident from the past two years. Here's what product teams and AI builders need to internalize before their next deployment.
Your prompts are training data
By default, ChatGPT, Claude, and most other AI assistants ingest your conversations to train future models. They also store your chat history in that sidebar you keep meaning to clear. While these platforms claim to scrub personal information from training data, "claim" is doing heavy lifting in that sentence.
The fix is simple but buried. In ChatGPT, navigate to Settings > Data Controls > Improve the model for everyone. Turn it off. You can also use temporary chats that won't persist in your history. Claude and other assistants have similar toggles, though they're rarely surfaced during onboarding.
Humans are reading your "private" chats
Here's the part that surprises people: AI companies employ human reviewers who read flagged conversations. If your prompt veers into anything the system considers potentially dangerous, a moderator may see it. Even when you opt out of training, companies keep temporary records of all conversations for safety and legal reasons.
Bruce Schneier, the Harvard Kennedy School security technologist, frames it bluntly: "Users need to treat AI interfaces like public forums, not private conversations." If you wouldn't post it on LinkedIn, don't paste it into a chat window.
Some tools promise zero data retention. Proton Lumo, from the privacy-focused email company, explicitly commits to not storing chat data. But for mainstream tools like ChatGPT and Claude, assume someone could read your prompt.
The confidence problem
Gary Marcus, the NYU professor and persistent AI critic, nails the core issue: "AI assistants are incredibly confident even when they're completely wrong. That confidence is dangerous."
A Stanford and Yale study found that 19.5% of ChatGPT legal citations were hallucinated. Not slightly wrong. Completely fabricated cases. Lawyers have filed briefs citing nonexistent rulings. The same pattern shows up in medical queries, where GPT-4 generates inaccurate information 36% of the time according to a Nature study.
For product teams building on LLMs, this isn't a bug to fix later. It's a design constraint. Any AI-powered feature that touches compliance, legal, medical, or financial domains needs human verification baked into the workflow, not bolted on.
What this means for AI builders
If you're shipping AI features, you inherit these problems. Your users will paste sensitive data into your interface. They'll trust outputs that shouldn't be trusted. And if your product doesn't clearly communicate its limitations, the liability lands on you.
The 77% of employees using AI tools without employer knowledge (per Salesforce) represents both opportunity and risk. These users are desperate for productivity gains. They're also creating shadow IT nightmares that security teams haven't mapped.
Teams using automation platforms like Zapier, Make, or n8n to connect AI tools with production systems need to audit what data flows through those pipelines. An innocent "summarize this document" workflow might be sending customer contracts to an AI provider's training servers.
Disclosure
Some links in this post are affiliate links — Logicity earns a commission if you sign up, at no extra cost to you. We only link products we have used or actively recommend.
Practical guardrails
- Audit your AI providers' data retention policies quarterly. They change without notice.
- Create company-wide prompt guidelines that explicitly prohibit PII, customer data, and proprietary code.
- For production AI features, log prompts and outputs separately from user data to catch leakage.
- Consider enterprise tiers of AI tools that offer contractual data protection, not just settings toggles.
- Train teams on the difference between asking AI for help versus asking it to process sensitive information.
Logicity's Take
The real story here isn't that AI tools are dangerous. It's that the default settings are designed for engagement, not enterprise security. OpenAI's ChatGPT Team plan ($25/user/month) and Anthropic's Claude for Enterprise offer better data controls, but most users never see those tiers. Product teams building AI features should default to minimal data retention and make training opt-in, not opt-out. The companies that get this right will win enterprise contracts. The ones that don't will become case studies in procurement decks.
Frequently Asked Questions
Does ChatGPT save my conversations permanently?
By default, yes. ChatGPT stores your conversation history and may use it for training. You can disable training in Settings > Data Controls and use temporary chats to prevent history storage.
Can AI companies see what I type in prompts?
Yes. AI providers keep temporary records of all conversations and employ human reviewers who may read flagged chats. Treat every prompt as potentially visible to a stranger.
Which AI tools don't store user data?
Proton Lumo explicitly commits to zero data retention. Enterprise tiers of major AI platforms offer contractual data protections, but free and consumer tiers typically store data by default.
How often does AI generate false information?
Studies show GPT-4 produces inaccurate medical information 36% of the time and fabricated 19.5% of legal citations it generated. Verification is essential for any professional use.
Another example of AI security assumptions failing in practice
Need Help Implementing This?
Building AI features with proper data handling? Logicity offers technical strategy sessions for product teams navigating AI security and compliance. Contact us at hello@logicity.in to discuss your implementation.
Source: Fast Company / Jared Newman
Manaal Khan
Tech & Innovation Writer
Produced with AI assistance and reviewed by the Logicity editorial team. Learn more in our Editorial Policy.
Related Articles
More in Ai In Business
AI Search Trust Problem: Why 85% of Users Doubt Results
New research reveals a massive gap between AI search adoption and user trust. Two-thirds of Americans use AI search tools, but only 15% trust the results. For businesses relying on AI-powered discovery, this trust deficit represents both a risk and an opportunity.

INSIDER REVEAL: How the American Enterprise Institute Uncovered the AI Productivity Boom
The American Enterprise Institute has been searching for signs of an AI-driven productivity boom. According to McKinsey, AI can increase productivity by up to 40%. We dive into the details of this emerging trend and what it means for businesses.

Will AI Ethics Regulation Become the New Industry Standard?
The Vatican has emphasized the need for AI ethics regulation in a recent statement, sparking a global conversation about responsible AI development. We explore the implications of this call to action and what it means for businesses and individuals alike. As AI continues to shape our world, we must consider the ethical implications of its development and deployment.



