LOCAL BY DEFAULT
Your saves, blueprints, settings, mods, and private Community signing key stay on your device unless you choose to publish or report content.
Rocket Foundry
Effective and last updated: 22 July 2026
This policy explains how Rocket Foundry handles information in the Rocket Foundry game, at rocketfoundry.net, and in the optional Community Hangar. Rocket Foundry is the developer and controller responsible for these services.
Your saves, blueprints, settings, mods, and private Community signing key stay on your device unless you choose to publish or report content.
We do not sell personal data, show behavioural advertising, use advertising IDs, or include third-party analytics or crash-reporting SDKs.
Online Community features transmit only the data needed to browse, publish, moderate, protect, and operate that service.
This Privacy Policy applies to the Rocket Foundry game on supported platforms, the Rocket Foundry website, the Community Hangar, and related support communications. In this policy, “we”, “us”, and “Rocket Foundry” mean the developer and operator of those services.
Privacy contact: [email protected].
The game stores gameplay data locally, including settings, savegames, rocket blueprints, installed mods, and user-created scripts. If you use Community publishing, the game also creates a pseudonymous creator identifier and a cryptographic signing key. The private key remains on your device and is used to prove that later publishing actions came from the same installation.
This local information is not transmitted to us merely because it exists. You can remove it by deleting the relevant game data or by clearing the app's storage. Uninstall behaviour varies by operating system and backup settings.
When your browser or the game connects to our website or Community service, our hosting and security provider processes ordinary request information such as IP address, request time, requested page or API route, browser or app user agent, and security signals. This is necessary to deliver the service, prevent abuse, and maintain security. Our Community database does not store raw IP addresses.
If you open My Uploads or begin publishing, we register a pseudonymous creator profile. We process an assigned creator ID, the public half of your signing key, your chosen public display name, app version, operating-system family, country code inferred by our network provider, account status, and acceptance of the current Community terms. You do not need to provide a real name, email address, or password.
When you choose to publish, we receive the information you submit: rocket title, public author name, category, blueprint file, a generated rocket preview image, part and size metadata, app/catalog/schema versions, and verification information. We also create operational records such as submission time, review status, moderation history, review reasons, appeals, download counts, and daily aggregate statistics.
Your public author name, rocket title, category, blueprint, preview, basic rocket metadata, and download count are made public after approval. Do not include personal information or content you do not want others to download.
If you report a Community rocket, we receive the rocket identifier, report reason, and a pseudonymous installation or creator identifier. We combine that identifier with a short-lived keyed network token to prevent duplicate reports and abuse. We keep the reporter pseudonymous from other users and do not publish the reporter's identity.
Before publishing, Cloudflare Turnstile may process network, browser, and interaction signals to determine whether a request is made by a person rather than an automated system. We receive the verification result and ticket state, not a Turnstile advertising profile.
If you contact us, we process your email address and the information you include so we can answer, investigate, and keep an appropriate support record.
Rocket Foundry does not request access to your contacts, precise location, camera, microphone, photo library, advertising identifier, payment-card details, or health information. The game has no advertising SDK, third-party analytics SDK, or third-party crash-reporting SDK. We do not sell personal data or use it for cross-service behavioural advertising.
A rocket preview is rendered by the game from your blueprint; it is not selected from your personal photos. External services you choose to visit, such as Discord or an app store, operate under their own privacy policies.
Where applicable law requires a legal basis, we rely on performance of the service you request, our legitimate interests in operating and securing it, your consent or deliberate choice to publish public content, and compliance with legal obligations. You may withdraw consent for future processing, but this does not affect processing already lawfully performed.
We may retain information longer when required by law, necessary to protect users or the service, or needed to establish, exercise, or defend legal claims.
You can use the single-player game without publishing to the Community. You can change your public display name for future actions and unpublish your own rockets from My Uploads. Unpublishing stops new public distribution, although people who already downloaded a blueprint may retain their copies.
Depending on where you live, you may have rights to access, correct, delete, restrict, object to, or receive a portable copy of personal data, and to withdraw consent. You may also complain to your local data-protection authority.
To request access or deletion: email [email protected] with the subject “Rocket Foundry privacy request”. If your request concerns Community uploads, include the creator ID shown in My Uploads so we can locate the pseudonymous profile. We may ask for a signed in-app action or other proportionate proof that you control it.
A deletion request will remove or de-identify data that we are not required or permitted to retain. Public content is unlisted as part of handling a verified deletion request, and associated stored objects are normally purged within 30 days.
We use safeguards designed for the nature of this service, including encrypted HTTPS transport, cryptographically signed creator requests, replay protection, pseudonymous identifiers, rate limits, restricted administrator access, and separation of the private signing key from our servers. No system is completely secure, so we cannot guarantee absolute security.
We do not knowingly collect personal information from children in violation of applicable law. Community users should never place personal information in an author name, rocket title, blueprint, or preview. If you are a parent or guardian and believe a child submitted personal information, contact us so we can investigate and delete it where appropriate.
Rocket Foundry and its service provider may process information in countries other than the one where you live. Where required, we use legally recognised safeguards for international transfers and apply the protections described in this policy.
We may update this policy as the game or law changes. We will publish the updated policy at this permanent URL and change the effective date above. If a change materially affects how Community data is used, we will provide an additional notice where reasonably practicable.
Rocket Foundry
Email: [email protected]
Website: rocketfoundry.net