Nightly backups in Stage 1

Your Board, your Brain, your replies and every message you've approved live in one database. If that database goes bad, months of work go with it.

So Stage 1 copies it every day.

What it does

Once a day, Stage 1 makes a complete copy of its database and saves it as a dated file. It keeps the last seven. When an eighth arrives, the oldest is deleted.

The copy is the whole database at a single moment. Every workspace's accounts, signals, people, research, drafts, replies, settings and learning. It's written as a clean, consistent file, not a half-copied one.

You don't do anything. There's no setting to turn on and no screen to visit. It runs inside the same loop that runs your plays and sends your messages, and it skips any day it has already run.

What a backup covers

A backup is there for two kinds of bad day.

The first is a bad update. If a change to Stage 1 ever damages data, there's a copy from before it to go back to.

The second is a corrupted file. Databases can break. A daily copy means the most you could lose is about a day.

If a backup ever fails, the failure goes straight to the Stage 1 team as an alert. A backup that fails quietly is worse than none, since everyone assumes it's there.

What it doesn't cover

The copies sit on the same server disk as the database. That protects against a bad update or a broken file. It doesn't protect against losing the disk itself.

We'd rather say that plainly than let you assume otherwise. Copies kept somewhere else are the next step.

How your connections are handled in a copy

The secrets and tokens that connect your LinkedIn, email and Slack are encrypted before they're stored, with AES-256-GCM. A backup copies them as they sit in the database, so they're encrypted in the backup too. Passwords are never stored at all, only scrypt hashes of them.

Every account, contact, message and setting belongs to one workspace. A backup doesn't change that. It's a copy of the same separated data, not a merged export. The security page has the rest of how Stage 1 protects your data and the people you reach.

Why it matters for a services firm

A services seller's pipeline is small and precious. Each account in it carries context you can't rebuild. Who you know there. What you passed on and why. Which hypothesis landed and which one got corrected. The learning that made your Board sharper over the months you ran it, which we wrote about in Stage 1 gets sharper the longer you run it.

Lose that and you don't just lose data. You lose the part of the product that took time to build.

Trust is the product in services, and that holds for the tools you sell with too. A tool that holds your pipeline owes you a plain answer about what happens when something breaks.

Seven days of copies, made every day. That's the floor, and it's in place.