Data
Your data on Forge64
Last reviewed
You own the app you generate and the data your users put in it. You can export the source code, database rows, file metadata and a manifest at any time, and you can delete an app or your whole account. A deletion drops the app's database and containers; a standard delete exports the data first and keeps the export for 30 days, and a GDPR erasure skips the export and deletes immediately.
Ownership
- BuiltThe generated source code and the data in your app's database belong to you. Forge64 hosts them on your behalf.
- BuiltForge64 sends your prompts to third-party AI model providers to generate the app. The list of third parties that process data is published for legal purposes and is available from the legal pages.
Export
The export is a runnable repository, not only source files: every version, the app's database rows as a logical dump, uploaded-object and domain metadata, deployment metadata, secret names and a manifest that marks each category as included, partial or unavailable, with the reason. Secret values are never included.
- BuiltSelf-service export of source, database rows and metadata, available to project admins.
- BuiltThe export taken before a deletion is capped at 48 MiB; a larger database fails closed (the database is not dropped) instead of being silently truncated. A queue-based export for large databases is not built.
Deletion and teardown
Deleting an app runs a resumable teardown saga. In soft mode it takes a final export, stops the containers and removes routes and domains, drops the app's database and roles after the retention period (14 days by default), and purges the export after 30 days by default. Each step is verified, and a failed or oversized export blocks the drop so data is never destroyed without a copy.
- BuiltSoft delete: export first, database dropped after the retention period, export purged later.
- BuiltErase mode for GDPR requests: no export, immediate database drop, export purge. Available per app and for a whole account.
- BuiltA deletion is refused while the seller has a non-zero payment balance or an open dispute.
- Rolling outThe teardown is wired to the delete endpoints, but the full saga has not been verified against live infrastructure.
- Rolling outBackups made before a deletion age out with the backup retention period (see Security).
GDPR
Forge64's erase mode implements the right to erasure for app data and account data. A standard data processing agreement and customer-selectable data residency are not available today.
- BuiltRight to erasure for an app or an account, with a tombstone record so the erasure can be completed and verified.
- RoadmapA standard data processing agreement (DPA) for customers.
- RoadmapCustomer-selectable data residency.
Frequently asked questions
- Who owns the app Forge64 generates for me?
- You do. You can export the source code and your database at any time, and nothing in the export is locked to Forge64.
- Can I export my data from Forge64?
- Yes. The export includes the source, every version, database rows as a logical dump, uploaded-object, domain and deployment metadata, secret names (never values) and a manifest of what was included.
- What happens to my data when I delete an app?
- In the standard mode Forge64 exports the data, stops the app, drops the database after a retention period (14 days by default) and deletes the export after 30 days by default. A failed export blocks the drop.
- Does Forge64 support GDPR erasure?
- Yes. Erase mode deletes the app's database immediately without taking an export, and an account-level erase removes all of an account's apps. Backups age out with the backup retention period.
- Does Forge64 offer a data processing agreement or EU data residency?
- Not today. A DPA and customer-selectable data residency are on the Roadmap.