Skip to content
Moosewave
Demo
Menu

TransactionalAccount & security

Security incident notice email template

A plain account of a security incident affecting some customers.

See the full preview Use it with MCP

Illustrative example. Replace the fictional sender, dates, amounts, locations, and account details before use.

Responsive design preview

See the message before you make it yours.

Compare the desktop and mobile compositions, or unfold the full design. The complete starting copy remains readable below.

Security incident noticeIllustrative preview
Security incident notice email template preview

The complete design fits in this window.

Auto follows your screen width. The complete design is visible in this window.

A reviewed browser rendition of the security incident notice structure. It is not a send receipt or an inbox-placement claim.

Want to change the copy and style?

Try one of the editable browser templates.

This page is a read-only reference. The five hands-on studios let you edit a local preview, compare desktop and mobile, and review every change before continuing.

See editable templates

Message anatomy

A useful starting point, with the important parts named.

We are writing to everyone, including people who were not affected, because a notice sent only to the affected is a notice nobody trusts.

What you can change

  • Brand name
  • Subject line
  • Preheader
  • Eyebrow
  • Headline
  • Supporting copy
  • Primary action label
  • Primary action URL

What to keep clear

  1. State or event context
  2. Plain-language explanation
  3. Three labelled facts
  4. Primary and secondary action
  5. Support or privacy footer

Complete starting copy

Read it as text, not only as a picture.

Sample details are fictional. Replace them with reviewed customer and event data before use.
From
Snaithwood Notices
Subject
What happened, and whether it touched you
Preheader
Your account was not among those affected.

Incident notice

It did not reach your account, and here is what it was

We are writing to everyone, including people who were not affected, because a notice sent only to the affected is a notice nobody trusts.

Your account

Not affected

What was reached

Support ticket text

Passwords

Not involved

Read the full accountAsk us a question
We will publish a fuller technical write-up within thirty days, including what we got wrong and how long it took us to notice.

Moosewave MCP

Give an agent the structure, the job, and a stopping point.

A compatible MCP app can inspect this reference and create a separate workspace draft when it has permission. The brief cannot send.

The brief asks for a new draft and stops before send.

Read the complete brief

Connected work

Take the design beyond the canvas.

Transactional email APIConnect the message to a real product event and keep its outcome visible.IntegrationsCarry the right customer and event context into the draft.SecurityKeep account, access, and recovery boundaries explicit.MCP for agentsAdapt presentation without quietly changing the event being explained.

Keep exploring

Browse all 1405