# Krispy Kreme Data Breach Settlement

Page: https://stenobird.com/podcast/sacramento-news-today-2-min-news-the-daily-news-now-7564759/krispy-kreme-data-breach-settlement
Text version: https://stenobird.com/podcast/sacramento-news-today-2-min-news-the-daily-news-now-7564759/krispy-kreme-data-breach-settlement.md
Podcast: [Sacramento News Today | 2 Min News | The Daily News Now!](https://stenobird.com/podcast/sacramento-news-today-2-min-news-the-daily-news-now-7564759)
Published: 2026-06-21T20:32:20+00:00
Episode link: https://api.fastcast.ai/audio/f84c8bc7-c814-49d7-9ca1-f0bed7230e72.mp3
Audio file: https://api.fastcast.ai/audio/f84c8bc7-c814-49d7-9ca1-f0bed7230e72.mp3
Processing state: not_requested
JSON: https://stenobird.com/v1/public/podcasts/sacramento-news-today-2-min-news-the-daily-news-now-7564759/episodes/krispy-kreme-data-breach-settlement
Duration seconds: 90

## Resource

Krispy Kreme’s data breach exposed 161K employees’ info — and now you’ve got until June 22, 2026, to claim up to $3,500 or $75 if you suffered documented losses. The company’s paying $1.6M to settle, and if you’re affected, you’ll need your claim ID and PIN — or contact the Settlement Administrator. Final court approval is July 6, 2026 — don’t miss the deadline. Support the show: Get a discount at https://solipillow.com/discount/dnn. Advertise on DNN: advertise@thednn.ai This is an automated, high-level news summary based on public reporting. Report issues to feedback@thednn.ai. View sources & latest updates: https://sources.thednn.ai/ac74f45996e1f29e

## Actions

- request_transcript: `POST https://stenobird.com/v1/public/podcasts/sacramento-news-today-2-min-news-the-daily-news-now-7564759/episodes/krispy-kreme-data-breach-settlement/transcription-requests` — Idempotently request low-priority transcript generation for this episode.
- read_markdown: `GET https://stenobird.com/podcast/sacramento-news-today-2-min-news-the-daily-news-now-7564759/krispy-kreme-data-breach-settlement.md` — Read the agent-friendly Markdown representation of this episode resource.

A page view does not enqueue transcription. Agents should invoke `request_transcript` explicitly when they need this episode processed.

## Transcript

Full transcripts are not published on public pages unless there is a clear rights basis.