Yaak
Day 17 after signup
Yaak security update: Railway incident
Why it works
- Explain the incident plainly before describing its possible impact on recipients.
- Pair specific security steps with a clear account of what may and may not have been affected.
- End with a direct statement about whether recipients need to act and a simple way to ask questions.
How it is built
- Personal greeting
- Incident explanation
- Security steps taken
- Customer impact clarification
Email copy
Hi [First name], On October 21 Railway, which hosts Yaak's website, disclosed a breach that exposed credentials for some of its customers, including Yaak. I've rotated every credential and checked accounts, licenses and plugins. Nothing was changed or tampered with. Your requests and workspaces live on your machine and were never at risk, and payment details are held by Stripe, so were not at risk. I found no sign that customer data was accessed but can't completely rule out that your name and email were exposed. There's nothing you need to do. If you have questions, please reply to this email. Greg --- Don't want security notices from Yaak? Unsubscribe