Cancelling Sakupa: what the official docs say happens to your site and your data

First, a clear statement: I'm not a Sakupa developer. I found this MCP server while researching, and this article only organises public information from the official site and the official manual. It is not a hands-on review.

Sakupa is an MCP server that lets an AI agent publish and operate a static website, with no account registration. Most introductions, including my earlier ones, focus on starting. This one looks at the other end: what happens when you cancel. I have limited myself to what the official information actually says, and I say so explicitly where it says nothing.

How does a contract end?

Sakupa's contracts are per site, not per account, and paid plans start at ¥200 a month. The free preview usually lasts 30 days.

Ending a contract is not something the agent does for you. Plan changes and end-of-term cancellation are done by the site owner on a Stripe management page, reached through a link created by the change tool. Payment itself also goes through Stripe's hosted pages, and the agent never handles card numbers. Before cancelling, the current contract, renewal schedule, and usage can be checked with billing, against the public plan catalogue shown by plans.

The shape of this matters: the decision to end a contract stays with the person, on a page the person operates, rather than being another instruction the agent carries out in conversation.

What happens to the published site?

This is where the official information I checked stops short. The docs describe how a contract is ended through Stripe, and they describe site deletion as a separate action — one that goes through a preview and a confirmation, and is explicitly irreversible for a free site. But they do not, in the material I read, spell out what happens to a published site's display, or when, after a contract ends.

That gap is worth stating plainly rather than filling in. Cancelling a contract and deleting a site are described as different things, and the docs do not connect them with a timeline. If the fate of a published site after cancellation matters to you, that is a question for Sakupa's official channel, not something to guess from the docs.

What happens to stored data?

One piece of stored data does have a stated retention period. Submissions through the mail-form app — the only app in Sakupa's catalogue so far — are kept for 30 days. That is the documented window during which a submission is not lost even if the notification email does not arrive.

Beyond that, the same caution applies as above. The official material I read gives the 30-day figure for form submissions, but does not state a general deletion schedule for other stored data after cancellation. I am not going to invent one.

What do locally stored credentials mean after cancellation?

Sakupa has no user accounts, so credentials are stored on your own machine. That design has a consequence people often miss: ending a contract on Stripe's page does not by itself erase anything on your machine.

What the docs do say is that rotate invalidates previously issued credentials, all at once — there is no picking which ones to keep. And recover exists to restore access when the machine holding the credentials is gone, through a device path or a DNS path. Whether old credentials are revoked is always the person's own choice, shown before the step runs.

So the end of a contract and the end of access are two separate things to think about. One is handled on Stripe's page; the other is handled with the tools that manage credentials.

What to check before cancelling

• Check the current contract and usage with billing, against the public plan catalogue in plans.
• Remember that the free preview usually lasts 30 days, and a free site's expiry can be extended with refresh.
• Remember that form submissions are kept for 30 days.
• Keep in mind that the docs do not state what happens to a published site's display after cancellation, or a general data-deletion schedule — those need confirming through official channels.

The short version

Cancelling is a deliberate, owner-operated step on a Stripe page, not an agent action. The contract is per site, the state of it can be checked before you act, and credentials live on your machine, where rotate can invalidate them all at once. What the docs do not say — what happens to the published site itself, and when stored data is deleted — is left unsaid, and that silence is itself part of the answer.

Links

• Official site: https://sakupa.com/
• Product page: https://sakupa.com/product/
• Manual: https://sakupa.com/manual/
• npm: @sakupa/mcp