1. Scope and contact
This notice describes information used by the Space Junker website, Unit 402 landing game and related email features, operated by MIM Robotics LLC. Contact us at [email protected] or the mailing address below.
2. Playing and pilot accounts
You can play the landing game without creating an account. A verified email address and a unique three-character callsign are required to save a verified pilot record across devices. We store your email privately, your callsign, account and verification timestamps, validated flight results, and your preference history. Verification emails are sent when you request registration or sign-in.
Before a flight, the server can issue an anonymous flight ticket. The browser submits its thruster-input sequence and timing so the server can replay and calculate the result. Input traces are processed for validation; the registry retains a digest, result, timing and ticket ownership rather than the full trace. Client-supplied scores do not determine the leaderboard.
3. What is public
If you choose public-score sharing, qualifying results may appear with your callsign, rank, score and landing rating. Your email is not displayed on the public board. Public sharing is separate from permission to send optional emails. Turn public sharing off in your pilot preferences to remove your results from current boards.
Older device-only records cannot be verified because they lack control-input evidence. If you choose to import them, they are stored as private, unverified history, separate from ranked results.
4. Cookies and local storage
An essential session cookie keeps your pilot session available for up to 30 days. Production pilot cookies are Secure, HttpOnly and SameSite=Lax. If you choose “Save on this device,” your local record remains in that browser’s local storage until you clear it or the browser removes it. Private browsing and clearing site data can erase local history.
5. Optional communications
The pilot form has three independent choices: leaderboard alerts; stories and clips; and Space Junker news and events. They start unchecked. Each saved choice records its time, source and version. Creating or recovering an account does not itself subscribe you to optional communications. Automated pilot notifications are not enabled in the current release.
Pilot emails contain an unsubscribe link. It turns off optional pilot notifications without deleting your account, changing public-score sharing, or preventing sign-in emails you request.
The separate “Join the channel” form collects the email address or mobile number you provide, your selected channels, consent, signup date, signup page and campaign source. It has its own consent and unsubscribe settings; pilot preferences do not silently alter those subscriptions. The signup form states that your data is not sold. Follow the unsubscribe instructions in the relevant message or contact us for help.
6. Website measurement and infrastructure
Where enabled, first-party measurement records page visits, referrers, campaign labels and engagement signals using anonymous browser-tab/session identifiers. It does not establish a person’s identity. That script respects Do Not Track, Global Privacy Control and its local opt-out setting. Coverage is incomplete, and blocked scripts or opted-out visits are not counted.
Cloudflare provides website delivery and protection, and Gmail is used to send pilot account emails. Providers receive information needed to deliver and protect those services, including relevant technical connection data. No advertising tracking pixel is added to the pilot email template.
7. Storage and security
Emails and pending verification payloads are encrypted in the pilot registry database. Verification links expire after 30 minutes and can be redeemed once. Session credentials and encryption keys are not placed on public boards. Access controls and backups reduce risk, but no system can guarantee absolute security.
Anonymous server flight records expire after 30 days unless attached to a verified pilot. Expired sessions and verification tokens are removed by periodic cleanup. Verified pilot records and consent history do not currently have an automatic deletion schedule. Backups are maintained separately and may retain earlier records. Contact us to request deletion and to understand the treatment of backup copies.
8. Your choices and requests
Use pilot preferences to change optional communications or public sharing, sign out to end this browser’s pilot session, and use the local-record control to clear device-only history. For an account-data copy, correction or deletion request, email [email protected]. We may need to verify control of the account before acting.
9. Bob and other information you share
When you ask Bob a question, the text you enter is sent to the MIM service at mim.mimtod.com to generate a reply. Do not include passwords, financial account details or other sensitive information in a character conversation. The pilot registry’s specific encryption and retention periods described above should not be read as promises about Bob conversations, correspondence or separate newsletter systems.
Pilot registration does not ask for a date of birth. If you have a concern about a child’s information submitted through the site, please contact us.
10. Changes
This page shows its effective date and will be updated when the described data practices change. Changes to this notice do not by themselves provide new consent for optional communications.