Disaster Recovery Program

A platform ban is the one failure a community business cannot route around on its own. When the platform restricts the account you sign in with, the bot that serves your members, or a place that holds your content, everything you sell is suddenly unreachable — while your subscribers keep paying and keep asking where their community went.

The Disaster Recovery Program exists for exactly that day. It watches your connected accounts, your bots and your places around the clock, tells you the moment one of them stops answering its platform, and gives you a calm page from which you move to a new account, a new bot or a new place in a few clicks — with every paying member re-admitted automatically and your plans, subscriptions and payments untouched. Nobody else offers this, and it is included on every plan, including Free. On Growth it goes further: standby bots, standby places with a live mirror of every post, a backup account and automatic failover turn a recovery into one click, or no clicks at all. That is the peace of mind the program is built for.

The three things a platform can take away

Everything on the recovery page is organised around three kinds of loss, because each one is fixed differently and each one has its own allowance:

The page lives at Disaster Recovery in your profile menu and in the Settings side navigation, at /recovery. When an incident is open, a banner across the dashboard takes you straight there. If your projects run more than one connector, the recoveries appear once per connector, each group headed by the connector's name and worded in its own terms, and the prevention card of each project offers only the safeguards its connector performs.

Where to start

What never changes

Whatever kind of recovery you run:

• Your plans, subscriptions and payments are untouched. Recovery re-points the platform; it never touches billing. Nobody is charged again, nobody loses a day of access on paper.
• Your members keep their place. Every member with active access, and every pass holder inside an open access window, is re-admitted to the replacement automatically. Nobody has to buy again.
• Nothing is deleted. The old account, bot or place is left as it is. Access into a replaced place is revoked, but nobody is evicted from it.
• You can undo. An account relink is undone from the security email we send you; a channel swap is undone from the recovery page. Both stay open for 24 hours.
• You are told. Every incident, every recovery and every automatic failover reaches you by email and, where the platform still lets us, on your connected account.

Example: a Sunday afternoon

Say you run a sports-picks community. On Sunday at 14:07 the platform bans your main channel while forty holders of today's pass are inside it. Here is what the program does, and what you do:

1. 14:09 — a member's join request for the channel cannot be approved because the chat no longer exists. That failure triggers an immediate probe; the probe finds chat not found, marks the resource degraded and opens a Places incident. You receive an email and a message on your connected account with a one-tap link into the recovery page. If you have project.resource.status_changed webhooks, your automation hears it too.
2. 14:10 — your members who write to the bot are answered automatically: "We are restoring access to this community right now. You do not need to do anything." Your portal shows the same notice.
3. 14:12 — you open the page from the alert, see the incident named at the top, and press Recover on Places. Because you had already created a fresh channel and made the bot its administrator, the bot offers it to you on the platform with one button; you confirm. (Without that, you press Replace and the connector asks you to pick the new place instead.)
4. 14:13 — the resource points at the new channel. Every one of the forty pass holders receives personal access through the bot, taps it, and is admitted automatically. The page shows the roll call filling: Re-admitted 40 / 40 · Joined 33. Seven who missed the message are reminded an hour later with one click.
5. 14:28 — the closing report lands in your inbox with the counts. The swap can be undone until 14:13 tomorrow, and the channel recovery you just used is self-service again in 90 days; an account or bot recovery in between is unaffected.

On Growth with a standby channel, automatic failover and the live mirror switched on, steps 3 and 4 happen on their own the moment the incident opens — into a channel that already holds every post you ever published — and you read about it in the email.

Fair use and enforcement

The Disaster Recovery Program is not a way around any platform's Terms of Service, and Subscriby has zero tolerance for using it as one. Every surface that describes the program says the same four things, in the same order:

1. It exists for creators who were banned or restricted through no fault of their own. Platforms ban places in error, restrict accounts by pattern, and occasionally sweep up bots that broke nothing. That is who this is for.
2. Each kind of recovery is self-service once per rolling 90 days. Account, bot and channel recoveries are counted independently, so using one never reduces another; several channel swaps made within 24 hours of the first count as one use. Automatic failovers count. The on-demand Swap & Grant Resource does not, because a healthy channel you chose to move is not a recovery.
3. Anything beyond that goes through our support team. While the cooldown of a kind is still running, a similar issue is not self-service: you contact support from the recovery page, and they audit the account, the content of the channels involved and the history of the bans before releasing another recovery. They tell you what they found. See Allowances and support review.
4. A confirmed violation closes the account. If that audit finds you directly violating Subscriby's or the platform's terms — for example content the platform removes for breaking its rules, or a pattern of bans for the same reason — the recovery is refused and we take the necessary steps to restrict and, under our Terms of Service, close the Subscriby account. You are told by email why, and your members are told that the project has ended.

This is deliberate. A recovery tool that could be used to hop from one banned channel to the next would make every honest creator on Subscriby look like a bad actor to the platforms it runs on. Keeping the program tight is what keeps it available.