What happens if I stop paying?

It stays where it is. A Flockbay project is an ordinary Godot project in a folder on your own machine, and Godot is open source and free to download. Opening that folder does not depend on a payment, on us, or on anything staying online.

That is not a policy we could quietly change later. It is a consequence of where the files live and what format they are in. The project lives on your own disk, and there is no proprietary container that needs a key to unlock. Flockbay keeps no copy of it unless you invite a team member to that game, and that copy is a spare, not the original.

The game you have already built is in the same position. It runs locally on Godot and it is ordinary Godot code rather than something that checks in with us before it starts.

If a plan is already on the account and you cancel it, it runs to the end of the month you paid for, and then that charge stops. Demo is still free each day. If you build on your own AI (your Claude or ChatGPT plan, your own agent, or an API key) and the plan or key behind it stops, Flockbay stops writing code until you connect one again. Either way, a game you already have on disk still opens and still plays.

Flockbay itself does not stop. It is free on your own AI, so cancelling a plan that is already on the account leaves you on Demo, not out. The engine, the builder and the manual controls stay.

Driving the app with your own agent over MCP stays too. Connecting your own agent over MCP is free.

Flockbay has no paid plans. If a plan is already on the account, you cancel it on Billing, and cancelling stops the next payment. There is no team plan, no per-seat pricing and no enterprise tier.

If a charge looks wrong, write to ed@flockbay.com with what happened and roughly when. The refunds page says the same. Specifics let us look at the actual account, which is more use to both of us than an argument about a policy line.

The binding version of all this lives on the terms page. This page describes how the product is shaped. The terms are the agreement, and where the two ever disagree, the terms are the answer.

A data retention period or a grace period made up on a marketing page would be worth nothing to you, so there is not one here. If a specific number matters to your decision, read the terms rather than this.

What is safe to say is the structural part, because it is a property of the design and not a promise anyone has to keep: the project is yours, on your disk, in an open format, running on an engine that is free software you can download from somebody else entirely.

That is usually the part people are actually worried about when they ask this question, and it is the part that does not depend on us behaving well.

Spend time with it before you rely on it. The trade-offs worth discovering are not billing ones. Flockbay is a desktop app for Windows rather than a browser tool, it needs an internet connection while you are building, and your game runs locally on the copy of Godot that ships inside it.

If any of that is a problem for you, you find out before you have put a month into it. If none of it is, a week of use tells you whether it suits the project you have in mind.

Flockbay does not expire and it is not a trial with a clock running on it.

A tool that keeps your project has a different set of incentives than one that does not. It can afford for the export to be awkward and for cancelling to feel frightening, because the fear does work for it.

Files on your own disk, in a documented format, on an engine anyone can download, removes that lever. It also removes an excuse. If people leave, it has to be because the tool was not good enough, which is the correct reason for anyone to leave.