Undo a deleted row or a bad day
Someone deletes the wrong table, a spreadsheet import overwrites good records, or a Tuesday just goes badly. Every app's database is backed up every night, and you can ask Claude to take a backup right now or to bring an earlier one back, on any plan. Claude can see 7 days of nightly backups on Free and 30 days on paid plans, where weekly copies reach back 90 days. A restore saves a copy of today's data first, so you can go back if it was the wrong copy.
What is in a backup
The backup is of the app's Postgres database: the records the app keeps. Your code and app settings are not in it: the code stays in your project and can be deployed again, and settings stay on the app. Nightly backups run at 03:00 server time. A new app has no backup until after its first deploy, because the database is created then.
Two different undos: the code and the data
Haechy keeps two kinds of history, and they answer two different problems.
Something you changed in the app went wrong. Every time a change goes live it becomes a numbered version. Ask Claude to put the app back how it was yesterday and the code goes back, usually in seconds for the three newest versions. Haechy keeps the newest 20 versions, and a rollback is itself a new version, so you can undo the undo. Safe changes, in full
Records were lost or overwritten. That is a restore, described below. It brings back the database from the backup you choose.
A rollback moves the code only. The database, stored files and settings stay as they are. A restore moves the database only. If a bad change also damaged records, you may want both, and you can ask Claude for both in one request.
Asking Claude
Say what happened and what you need. Claude lists the backups, tells you which one it would use, and asks you to confirm the app by name before it restores anything. To take a backup yourself, ask for one: it appears in the list within a minute.
- You
Someone deleted the supplier table by mistake. Can you get yesterday's data back?
- Tool
list_backupsexpense-trackerDone7 backups, newest first: id, time, kind (daily) and size.
- Claude
There is one from 03:00 yesterday. Restoring replaces the app's current data with it. I'll save a copy of today's data first. Shall I restore it for expense-tracker?
- You
Yes, expense-tracker.
- Tool
restore_backupexpense-trackerDoneSafety backup taken. Database restored. The app is restarting.
What a restore does
A restore replaces the app's current database with the backup you pick. Before it does that, Haechy saves today's data as a safety backup, so if the copy turns out to be the wrong one, you can restore the safety backup and be back where you started. When it finishes the app restarts. Anything people entered after the chosen backup was made is not in the restored data, so pick the latest copy from before the problem, not simply the oldest one.
How far back can you go?
The plan decides which backups list_backups shows, and Claude can restore any backup in that list:
- Free: nightly backups from the last 7 days, plus backups you asked for and safety backups from the same 7 days.
- Pro, Team and Business: nightly backups from the last 30 days. Beyond that, for 90 days, there is one copy a week (Sunday's nightly), plus backups you asked for and safety backups. So on a paid plan you can usually find a copy from before a problem that went unnoticed for a few weeks.
Stored files (receipts, photos and PDFs) are not in a database backup. If someone deletes files, tell us quickly: support can recover deleted or overwritten files for 30 days. See file storage.
In storage, nightly backups are deleted after 35 days and every other kind after 90 days, whatever the plan. On Free that means copies older than 7 days still exist for a while but can't be restored; there is no way to reach them through Claude.
Backups are encrypted and stored in the same region as the app. What lives where.
Some services we use to send email, verify phone numbers and take payments process data outside your chosen region. See our sub-processors.
Take a backup before you ask for a risky change
Asking Claude to change data with execute_database_sql (inserting, updating, deleting, dropping a table) can't be taken back by the query itself. Ask for a backup first, or tell Claude to always take one before it runs changes like that. Reading data with query_database is read-only and needs no backup.
If you delete an app
Deleting removes the app, its address, its database and its settings, after taking a final backup. That backup is kept for 90 days and then goes. Claude asks you to confirm the app name first.
The retention windows by plan are in plan limits. For the other controls around an app, see security.