When we update NewsletterScriv
We put new versions out overnight, between 2 and 4 a.m. Eastern. That's the quietest stretch for our authors, so it's when you're least likely to be mid-sentence when something changes.
What an update looks like from your side
Nothing goes down. Updates roll out without taking the app offline, so anything you load afterwards works normally.
What you may see, if you had a tab open through one, is a small note in the corner: "NewsletterScriv just got an update—this tab is running the previous version." It offers Refresh now or Later.
Take that one seriously rather than dismissing it for long. A tab loaded before an update is talking to the version that's gone, so saving from it can fail—that's the actual problem the note exists to prevent, not a cosmetic nag. Save if you can, then refresh. If a save has already started failing with an unhelpful error, refreshing is the fix.
Your unsaved writing is protected
This is the part worth knowing, because it's the question everyone actually has.
The campaign editor, the book editor, and the sequence editor all keep a private copy of what you're typing in your own browser, separately from what's saved on our side. If you refresh—during an update or at any other time—and that local copy is newer than the saved one, you're offered it back before anything is replaced. Nothing is ever silently overwritten:
- If your local copy is the newer one, you'll be asked whether to restore it.
- If the saved version is newer (say you edited from another device), we say so plainly and let you keep the newer save instead.
So refreshing is safe—which is exactly why it's the right response to that note. You don't need to paste your draft somewhere else first as insurance.
If something looks wrong after an update
Try a hard refresh first (Ctrl+Shift+R, or Cmd+Shift+R on a Mac)—that clears a stale copy your browser is holding, which explains most oddities right after a release.
If it persists, email [support@newsletterscriv.com](mailto:support@newsletterscriv.com) and say what you were doing. A human reads it—usually the founder, usually the same day.
Urgent fixes are the exception
If something is actively broken for authors, we fix it as soon as it's ready rather than waiting for 2 a.m. Those are rare, and the protections above apply exactly the same.