Cluely Data Breach (2025) — Is Your Interview AI Safe?

The Short Answer

According to public reports, Cluely experienced a security incident in 2025 that is said to have exposed account details and stored meeting transcripts for an estimated tens of thousands of users. If you used Cluely during that period, change your password and assume any meeting content you ran through the platform may have been exposed. For a forward-looking alternative, pick an interview AI that is built around BYOK (Bring Your Own Key) and does not store transcripts on its own servers — that is structurally how you avoid the same class of incident.

What Happened With Cluely (2025)

According to public reports, the Cluely incident is said to have exposed:

• Account credentials for tens of thousands of users
• Stored meeting transcripts (because Cluely retains them in the cloud by default)
• Associated metadata: meeting timestamps, participant emails, file uploads

The root cause was the architecture itself: by storing every meeting transcript centrally, Cluely created a high-value target. Once breached, every transcript was exposed at once.

What Categories Of Interview AI Are Affected

Any tool that meets both conditions below is structurally exposed to the same risk:

1. Stores meeting / interview transcripts on its own servers (vs your own cloud)
2. Runs LLM inference through its own account (vs BYOK)

This includes most of the premium category: Final Round AI, LockedIn AI, Parakeet AI, Cluely. Tools that use BYOK and do not retain transcripts (AissenceAI, Natively) are structurally less exposed.

How AissenceAI Is Built To Prevent This

• BYOK: All AI inference runs against your own OpenAI / Anthropic / Google account. We never see your prompts in our database.
• No cloud transcript storage by default: transcripts live on your local device unless you explicitly opt-in to cloud sync.
• Native desktop processing: audio is captured and processed locally; only the text prompt is sent to the LLM provider you chose.
• Minimum-data principle: account record contains email + plan only. No interview history is stored on AissenceAI servers without explicit opt-in.

Action Steps If You Used Cluely

1. Change your Cluely password and any reused passwords elsewhere
2. Enable 2FA on your email account (the breach included email addresses)
3. Review any sensitive interviews / meetings you ran through Cluely and assume the transcript may be public
4. Move to a privacy-first alternative: see our Cluely alternative comparison

Privacy-First Alternatives Compared

• AissenceAI — BYOK, no cloud transcripts, native desktop stealth, $20/mo. Compare »
• Natively (open source) — Self-hosted, BYOK, no managed transcripts. Compare »

Why This Matters Beyond Privacy

If you are interviewing under NDA (most senior tech and finance interviews are), uploading the interview content to a third-party cloud service may itself be a contract breach — independent of whether the tool gets breached later. BYOK + local-first is the only architecture that addresses both concerns.

Try AissenceAI Privacy-First

Sign up at /auth/signup. Free plan includes BYOK setup and the desktop overlay. No credit card.