Privacy
Collect less. Keep private work private.
This product notice describes the data boundaries implemented by this GameFoundry release. Last updated July 23, 2026.
Account and project data
GameFoundry stores the account information needed to authenticate you, private project files, version history, generation jobs, usage receipts, team permissions, and publication settings. Project access is checked server-side.
Public games
Publishing exposes the title, description, tags, creator profile, validated game specification, chosen thumbnail, exact deployment files, version metadata, remix permission, and lineage you selected for that publication. Private prompts and chat history are not part of the public game response.
Play metrics
A page view is not counted as a play. The player records an aggregate qualified play only after runtime readiness and first input, plus bounded session duration, completion, and share signals. Anonymous actors use a random local identifier that is hashed server-side. GameFoundry does not store an IP address in the game engagement tables.
Remixes and reports
Remix lineage is public when the remix is published. Reports store the reporting account, selected reason, optional detail, and moderation status so abuse can be reviewed and duplicate reports controlled.
Deletion and exports
Project deletion removes project-owned records and schedules cleanup for external objects. Some security, billing, audit, or attribution records may need bounded retention. Source projects can be exported from the studio.