Cancelling Basecamp Ends Your Access Immediately

Across every subscription we have documented, one piece of advice has been close to universal: cancel whenever you like, because you keep working until the end of the period you have already paid for. Trello says it explicitly. ClickUp, Pipedrive, FreshBooks, Apple and Asana all behave that way.

Basecamp does not.

"you won't be able to access your account once you cancel."

Why that one sentence changes your sequencing

If cancelling ends access immediately, then the usual plan — cancel now so you do not forget, export during the remaining weeks — produces exactly the disaster it was meant to avoid.

You would be locked out of a system you have already paid for, with your projects on the other side of the door and a 30-day recovery clock running.

So on Basecamp, cancellation is the last step rather than the first. Export everything, confirm it is readable, tell everyone who needs telling, and only then cancel — ideally on or near the renewal date, since unused time is not automatically prorated.

That is the opposite of the habit most people have built from every other subscription they own.

Thirty days, then sixty

The retention is clearly documented and reasonable:

• 30 days: content is removed from servers. Recovery is possible within this window.
• 60 days: content is removed from backups.
• After that, in 37signals' wording, it "can't be recovered".

The 30-day recovery window is a genuine safety net, and it is the thing that makes the immediate lockout survivable rather than catastrophic. Cancel by mistake, or cancel and change your mind, and there is a month in which that is fixable.

What it is not is an export window, because you cannot get into the account to export from it. Recovery means reinstating the account, not retrieving a copy.

No export is offered

The cancellation policy does not describe an export product. It says to save your own copies before cancelling.

That is worth planning properly, because Basecamp holds an unusual mix of things:

• Message boards — long-form discussion that is often the only record of why a decision was made.
• To-dos, with their assignments and completion history.
• Docs & Files, including documents written inside Basecamp that exist nowhere else.
• Campfire chats, which accumulate informal decisions nobody wrote down properly.
• Schedules and the dates attached to them.

The files are the easy part. The writing — message threads, comments, chat — is what people forget, and it is the part with institutional memory in it.

In fairness to 37signals

Two things are worth saying, because this page could read as harsher than the reality.

The policy is short, plain and honest. It tells you access ends, when data is removed from servers, when it goes from backups, and that there is a recovery window. No euphemisms, no burying it in a terms-of-service PDF. Compare that with the several vendors in this series whose deletion behaviour we could not establish at all.

The refund stance is unusually decent. Offering to refund someone who has not used the account in months is not standard industry behaviour, and 37signals volunteers it.

So this is not a company being slippery. It is a company with a different default from everyone else, clearly stated — and the risk is entirely that you apply a habit formed elsewhere.

The checklist

1. Export and save everything first — files, documents, message threads, to-do history, chat.
2. Open what you saved and confirm the writing came with it, not just the attachments.
3. Tell your collaborators and clients, since their access ends when yours does.
4. Note the renewal date and cancel near it rather than early.
5. Diarise day 25 after cancelling, as a last check before the 30-day recovery window closes.

For how the rest of the category behaves at the same moment — and most of them let you keep working — see what each project tool does when you stop paying, and which products still let you export afterwards.