Recovery archive
For God Mode holders: the Storage Explorer view that brings back deleted content and reads activity older than the live window. Back to Administering the system.
Recovery archive: bring back what was deleted
The fourth view of Storage Explorer. It exists so that nothing you delete, purge or lose is gone for good, and so that activity is never thrown away. It keeps three things in an encrypted archive outside the database: activity older than 90 days, every deleted or purged item (tasks, notes, OKRs, comments, events, boards and teams, with what belongs to them), and a daily copy of that content. Only a God Mode holder who has confirmed their second factor can open it or restore anything; no other role can, and the database refuses them even if they reach the page.
Why the archive is not the same as the “Archive” on a task or note
Archiving a task, a note or a topic is a state of something that still exists. The Recovery archive holds what was deleted. It is also not the database snapshot under Maintenance, which is a copy of the whole database restored by a written runbook; the archive restores one item or one team’s content, from this page.
The status strip, and when it says something is wrong
Across the top: the last run, how much is stored, this month’s estimated cost, the live window and the next run. A line under it tells you if the archive is not set up, has fallen behind (the last good run was more than 26 hours ago), or stopped at its daily cost cap, which is a limit written into the code so that a fault cannot run up a bill. Nothing is lost in any of these cases: activity stays in the live table until its archived copy has been read back and checked, and deleted items wait to be archived.
Deleted items
Filter by date, organization, type and title; Preview… a row to see the item and what comes back with it (a task with its comments, reminders and links; an objective with its key results and check-ins; a team with everything under it) and a check against live data. A deleted item appears within about two hours, kept for 12 months. If the item’s board, team or objective is gone too, the preview says so and offers to restore that parent from the newest daily copy in the same step; it never moves anything somewhere else silently. An item that exists again is marked Exists again and is left alone.
Deleting an account is final. Its personal tasks, notes and tags are not archived and are removed from the archive within 60 days, so they cannot be restored. Team and board content it touched is kept, so the team can still restore it.
Point in time
Choose an organization (or personal items), a daily copy, and the areas — Tasks and boards, Notes, OKRs, Events, Teams — and optionally one board or one objective. Compare with live shows three counts: missing in live, changed since and created since. Restore missing only is the default and never changes a row that exists now. Also overwrite what changed needs you to type restore, keeps today’s version of every row it replaces in Deleted items first (so the restore can itself be restored), and is refused above 5,000 rows at once. A restore never deletes anything, and a point-in-time restore brings back content only: who has access (team and board members, collaborators, group members) is left out unless you turn on Also restore who had access, and the dry run then lists the people it would add back.
Every restore is a dry run first
Dry run shows exactly what would be written, with counts and what is left out and why (for example, a row whose owner’s account no longer exists). Restore then applies that same plan. If anything changed since the dry run, it restores nothing and asks you to run it again; a plan expires after 30 minutes and can be applied only by the administrator who started it. A restore emails and notifies nobody, writes an activity record, and is recorded in the archive’s own audit log. It writes directly to the database, so it does not apply the usual per-person row rules: the protections are the God Mode and second-factor check, the dry run, the plan seal and the cap.
Activity history
Activity older than the live window (90 days, adjustable from 30 to 365 under Runs), read straight from the archive for up to 31 days at a time, by organization, feature and action, with a title search, and Export CSV. Nothing is put back into the live table. The most recent 90 days are in User traffic and audit trail. Archived activity keeps the action and the title but no longer links to a deleted account.
Runs, and what it costs
Every run with its objects, bytes and result; Run now starts one; Verify sample re-reads random archived objects and checks them; the live window and the daily caps are set here. The estimated bill uses the prices stored with the date they were read. At today’s volume it is inside Cloudflare’s free allowance, and the daily caps hold the worst case under about $1 a month; a Cloudflare billing notification on the account is the second guard. Archived activity and deleted items are kept to the published Terms (365 days of activity, 12 months of deleted items) until a newer Terms version lengthens them.
Run self-test (also on Runs, for a God Mode holder only) tries the archive on a test organization without touching the real archive. Enter the test organization’s id and press Run self-test (an ordinary organization is refused): its deletes and a snapshot are archived under a separate test prefix, so you can preview and restore them from Deleted items. The scope is cleared the next time Refresh shows the run finished, or straight away with Clear scope now. Point in time never offers a self-test snapshot.