Backups & recovery

Your Context Engine is backed up automatically, and those backups are protected so that only your engine can unlock them.

How it works

• Backups run on a regular schedule (typically nightly), with no action needed from you.
• Each backup is encrypted on your server before it leaves, using your engine's own key.
• The encrypted backup is stored in a location your hosting partner controls. Because it's locked with your engine's key, neither the storage provider nor the operator can read it.

The hosting platform also keeps checking that a recent backup exists, and flags it to your partner if one falls behind — so gaps get noticed.

Recovering from a problem

If something goes wrong, there are two ways your engine can be brought back:

• Roll back your engine to an earlier backup of itself (for example, to undo a bad change).
• Rebuild your engine from a backup onto a fresh server if the original server fails. Your web address moves to the new engine, so you keep using the same link.

Your partner performs these recoveries for you.

Your recovery key

There's a recovery key that can unlock your engine's backups. It's the master secret behind your data's safety, so:

• If you were given a copy, store it somewhere very safe (a password manager is ideal).
• Treat it like the key to a safe deposit box — anyone who has it can open your backups.
• If you weren't given one, your hosting partner keeps it protected on your behalf and can use it to recover your engine.

If you're ever unsure about your backups or recovery, ask your partner — they can confirm your most recent backup and walk you through recovery.