Draft a crisis communication response

**SHORT (social):**
Earlier today, a configuration error exposed some Lumen account email addresses to other users for about 40 minutes. No passwords, payment details, or messages were affected. We've fixed it and notified everyone impacted directly. If you have questions, reach us at security@lumen.app. We're sorry — here's what happened and what we're doing: [link]

**MEDIUM (blog):**
**What happened with the June 2 data exposure**

This morning between 9:10 and 9:50 ET, a flawed deployment caused a settings page to display other users' email addresses. Roughly 4,200 accounts were affected. No passwords, payment information, message content, or files were exposed — only email addresses, and only to logged-in users who visited that specific page during the window.

We caught it through automated alerting, rolled back the deploy within 40 minutes, and confirmed the fix in staging and production. We're emailing every affected user individually today.

What we're doing now: a full review of our deployment checks, adding a pre-release scan that flags any page rendering another user's data, and a third-party review of the incident. We'll publish that review's summary by June 16.

If your account was affected, you'll hear from us directly. Questions: security@lumen.app.

We build Lumen to protect your information, and today we fell short of that. We're sorry.

**LONG (email):** [Same structure, opens with a direct "You're receiving this because your email address was among those exposed," includes the timeline, the explicit list of what was and wasn't affected, the remediation steps, the June 16 review-publication commitment, and a direct reply-to security contact.]