Backups the app cannot reach, and one restore you have actually done
The free plan has no backups. The paid plan has seven daily and none of your storage files. Point-in-time recovery is a paid add-on. A backup on the same account the agent can delete from is not a backup, which is the PocketOS story in one line.
Where it bit
The video pipeline, in a different shape: nothing is deleted locally until the archive copy has been verified by checksum, and we still found two "archived" exports that were not on the drive at all during the storage sweep. Same rule, same failure mode, different files.
The practice
A scheduled supabase db dump to a bucket the app's credentials cannot write to or delete from. Storage files included. One restore drill, timed, so the number "how long until we are back" exists.
Check it
Ask: which credential can delete the newest backup? If the answer is any credential the app or an agent holds, there is no backup.
Get this check as a script you can run tonight
What to do with this
If you run a business on something AI built and the checks came back with more than you expected, that is worth a conversation.
We do a free 30-minute Health Check for service businesses that want to know exactly where their biggest leaks are. No slide deck. No pitch. We ask questions, find the gaps, and tell you what we see. If there is no obvious fix, we will tell you that too.
Blinkz finds what is broken in how a business runs, then fixes it. AI only where it earns its place.