Privacy Policy

1. What we process

• Sign-in identity: the hosting sign-in service provides an account identifier, email address and name if available. The game uses the account identifier to associate your journey, rooms and wallet records. A creator name and profile you publish are separate from your sign-in identity.
• Your journey: current location and position, explored paths and traces, tools, difficulty, health and ammunition, story choices, journal discoveries, map labels, corridor notes, stock observations, memories you choose to save and your letter draft.
• Creator contributions: room title, creator name, messages, profile bio and optional social link, images and image links, external links, paid extras, publication settings, prices, coupon codes and campaign settings. Invitations include a message, inviter label, code and claim record.
• Wallet and game accounting: linked public wallet address, ownership challenge and verification state, balances, transfer requests, signatures, transaction data, amounts, fees, timestamps, status and recovery records; game charges, creator earnings, referral attribution, unlocks and coupon claims.
• Policy acknowledgments: your account identifier, the version and content hashes of the Terms and Privacy Policy you acknowledged, and the server-recorded time of confirmation. We use this record to establish which conditions you accepted before starting new deposits or paid actions.
• Operational information: upload ownership and quota records, request limits and errors used to keep the service working. Hosting and network providers may also process IP addresses, browser information, request times and security logs.
• Messages you send us: your contact details and the contents of support, content or privacy reports.

The game does not ask for your wallet recovery phrase or private key. Its medical imagery and memory prompts are fictional game elements; you do not need to provide medical records, legal identity documents or sensitive personal details to tell a story.

2. Why we use this information

We use account and journey data to save and restore your playthrough, display discoveries, protect account ownership and keep your notes with you. We use room information to publish and deliver contributions according to their available discovery and access settings.

We use financial records to verify deposits, record internal payments, calculate creator and referral shares, process withdrawals, recover interrupted requests and prevent duplicate or unsupported credits. Upload and rate-limit records help manage storage and abuse. Support messages help us respond to requests, investigate problems and resolve disputes.

The current game does not include an advertising-tracking or behavioral-advertising system. Future ideas for sponsored bots or an ad platform are not part of this release. External media and hosting services have their own data practices.

3. What other players can see

Your saved story, personal map notes, memories and letter draft are associated with your game account and are not automatically published as creator rooms. “Private” here means they are not deliberately shown to other players; it does not mean end-to-end encryption or that the operator and service providers cannot access stored data.

When you publish a room, its title, creator name, message, image, profile and other visible content are intended for visitors. Room metadata can be delivered to signed-in players even when the room is not listed in the directory. Discovery, direct-entry and visit requirements control game access, not confidentiality.

Paid-extra text and links are withheld from ineligible visitors by the game. This is not copy protection: someone who can view content may copy or share it. Uploaded images are served to signed-in users who know their image address; they are not private storage or protected by a room’s payment gate. External image links are governed by their host.

Invitation messages are available to people using the invitation link. Do not place confidential material in an invitation, a coupon code or a published room. A coupon receipt records that a code was shown to a particular account; the game does not verify what happens at the external merchant.

Archiving or using the current delete control hides a room from ordinary visitors while preserving its stored content and records. Previously downloaded copies and known image links may remain accessible. See retention and deletion.

4. Wallets, the vault and public transactions

A verified wallet link connects a public Solana address to your game account. Linking requires a signed ownership message. Deposits and withdrawals, when enabled, require separate transaction approval and create public blockchain records.

Solana transactions can reveal public addresses, token amounts, timing, fees and transaction memo or reference data. Blockchain records are not anonymous, and we cannot erase or modify finalized on-chain history. Dust’s internal game ledger also links transfers, creator activity and balances to game accounts.

The withdrawal service processes saved transfer identifiers, destination wallet addresses, exact transaction data and signing or refusal records. These records support safe retries and prevention of duplicate withdrawals. Only the service’s own vault signing key is used there; your personal wallet key remains with your wallet provider.

Network RPC services receive account queries and transaction submissions required to verify and send transfers. A blockchain explorer receives your visit if you follow a transaction link. Your wallet provider handles its connection and approval interface under its own policies.

5. What stays in your browser

Dust uses browser storage for preferences and tutorial reminders, local game state or cached progress, map bookmarks, room drafts, and saved requests. Some of that progress is also synchronized to your signed-in account. A draft saved only on this device is not published just because it appears in the editor.

Wallet storage can contain an account identifier, request identifier, wallet address and signed transaction bytes for a pending transfer. Funded game actions are also saved locally until their outcome is confirmed. These are recovery records, not your private key.

Local storage is specific to this site address, browser and device and has no general automatic expiry in the game. Clearing it may remove drafts, preferences and information needed to recover an unfinished request. Resolve pending transfers before clearing site data. Clearing your browser does not delete server records, sign-in provider records, published content or blockchain transactions.

Signing out, disconnecting a wallet, unlinking a wallet and restarting a story are different actions. Unlinking removes the active wallet association and challenge; it does not erase balances or transaction history. Restarting resets your journey and can retain earlier map summaries; it does not delete your published rooms.

6. Hosting, images, videos and links

Dust is hosted through OpenAI Sites and delivered using Cloudflare services, including game databases and image storage. The dedicated withdrawal service runs on separately operated server infrastructure. These providers process information to operate and protect their services. See the OpenAI Privacy Policy and Cloudflare Privacy Policy for their practices.

A creator’s external image can load from its host when displayed. That host may receive your IP address, browser details and a request associated with the page. Uploading an image to Dust instead stores its original image bytes and ownership metadata; do not assume embedded metadata has been removed.

The supported YouTube player is optional. Before you choose “Watch here,” Dust does not create that video’s iframe or request its thumbnail. Loading the player contacts youtube-nocookie.com; playing it may involve YouTube’s services and data collection. You can close the player or open the video directly on YouTube. See Google’s Privacy Policy.

Following links to pump.fun, other games, social profiles, shops or creator websites sends you to those services. Their policies govern your activity there. The Memecoin Arcade has its own directory privacy policy.

Support email is handled by the team’s email service. Service providers and the operator may process data in countries other than where you live; this release does not offer a choice of storage region.

7. Retention and deletion

We have not established a fixed deletion schedule for game accounts, journeys, uploads, financial records, support email or operational backups. The current application has no self-service full-account deletion or automatic expiry for these records. We do not promise that a story restart, wallet unlink or room archive erases them.

We keep game and financial records to operate saved worlds, retain ownership and access history, recover transactions, prevent duplicate payments, investigate disputes and meet applicable obligations. Financial and signing records may need to remain after a room is removed or an account stops playing. Blockchain records cannot be deleted by us.

You may request access, correction or deletion by emailing hi@rnnr.fun. We may need to verify the account or wallet you control to avoid disclosing or deleting someone else’s data. We will explain when a record must be retained or cannot be removed. Provider retention practices and copies made by other visitors are outside the game’s deletion controls.

8. Your choices and requests

You can choose what you publish, edit or archive your rooms, keep a memory in your personal journey, decline to load an embedded player, or stop using a linked service. Do not include more personal information than you want associated with your account or room.

Depending on applicable law, you may have rights to access, correct, delete or obtain a copy of personal information, restrict or object to some processing, or complain to a relevant privacy authority. Contact hi@rnnr.fun to make a request. These controls and this policy do not limit rights provided by law.

The game is not designed to solicit personal information from children. If you believe a child has supplied information that should not be held, contact us so we can review it. Real-token features also require compliance with the eligibility rules in the Terms of Service.

We will update this policy’s date and version when the game’s data handling changes. New social, advertising or other features may require additional disclosures and choices before use.