Your data is yours, by design
Forge makes one structural promise about data: it stays in the region it was collected in, by default. That is not a setting you configure and it is not something Forge revokes — it is how the platform is built. The same logic applies to ownership. The data your app collects is yours to keep, move, or hand over.
Where your data actually lives
Most apps on Forge store data in the managed databases that come with the plan — bookings, orders, form submissions, whatever your app tracks. On the TEAM plan, managed databases are included alongside multiple client projects, so each project's data stays separated under one account.
Getting your data out
Because Forge onboards from the waitlist in small batches, export is a conversation with a person, not a hunt through a settings menu. When you need your data, you ask, and it arrives in standard formats your tools already understand — SQL dumps or CSVs, the same shapes you would use to move data anywhere else.
A full export covers the three things a data export usually needs: the database contents, the app code you pushed (which was always yours — you brought it as a repository), and the configuration that ties them together.
What an export does and doesn't change
Exporting is not the same as leaving. Your app keeps running the whole time, and nothing you export changes your billing or your deploy. If what you actually want is to move the app itself somewhere else, that is a separate job — see How to Move an Existing App to Forge for the reverse direction, and the same steps work outbound.
When you'd want this
Three situations come up most: an agency handing a finished project to its client, a business pulling records for an accountant or auditor, and a team archiving a project they are winding down. All three are covered by the same export path — see Forge Support and Handover for how handover works in practice.
Related: Who Should Use Forge (and Who Shouldn't) and What Does It Cost to Run an App on Forge?