For Marketing

Is this a marketing moment?

No — and that's fine. This is an invisible reliability/security fix, not a feature. There's no new screen, no new setting, nothing to demo. Don't build a launch moment around it.

If it comes up anyway

It's a legitimate, small data point for the "we take security seriously" narrative, alongside things like two-factor authentication and permission groups. If you're ever writing broader security or trust-and-safety copy (a trust page, a security FAQ, a sales one-pager), you can fold in a line like:

"When an account is locked, its password is reset, or its permissions change, Dentolize immediately stops sending that device push notifications — not just at the next login."

Keep it general. Don't name internal mutation names, don't imply this was a vulnerability that exposed clinical or patient data — it didn't. The fix is about a stale phone continuing to receive notifications after its session ended, not about anyone gaining unauthorized access to anything.

What not to say

• Don't call this a "new feature" — it's a correctness fix to existing behavior.
• Don't say push notifications were "hacked" or "leaked" — no notification content was exposed to the wrong person; the issue was that a signed-out device kept getting notifications meant for the account it used to be logged into.
• Don't promise this retroactively fixes anything for currently-active sessions before the fix ships — it only changes behavior going forward, for actions taken after deploy.