Protect your wallet and your peace
Player Safety
Use official access routes, review wallet and trade prompts, protect personal information, and respond safely to suspicious behavior.
On this pageWallet safety
Wallet safety
Verify that you are using an official Starville route before connecting. Check the full domain, avoid links from unsolicited direct messages, and review every wallet prompt. Ordinary access asks for a human-readable ownership signature and eligibility check; it does not require sending tokens or approving a token transfer.
Never share a seed phrase, recovery phrase, private key, wallet password, authentication token, or copied browser session. Legitimate Starville support does not need them. A person who receives this information can take control of accounts or assets even if they claim they are only diagnosing a problem.
Disconnect suspicious sessions from the wallet’s own trusted interface and close unfamiliar tabs. If a prompt describes a transfer, approval, stake, claim, swap, bridge, or NFT action during ordinary access, reject it. Starville does not currently use those flows.
Gift and trade safety
Keep the full exchange inside Starville’s official item trade panel. Review every item and quantity after the latest change. When either side changes an offer, confirmations clear so that both players must approve the new version.
Only eligible ordinary items can move. DUST, STAR, SOL, NFTs, cash, protected items, permanent starter items, and temporary activity items are not supported trade content. Do not trust an external promise to pay after a Starville item is delivered.
Cancel if the other player pressures you, changes an offer repeatedly, asks you to move to an unofficial site, or requests private account information. Blocking prevents incompatible new social interactions; a cancelled or expired exchange releases its item reservations.
Chat and personal privacy
Treat Nearby, Channel, and Party chat as shared spaces. Do not post an email address, home address, legal identity, school, workplace, financial information, wallet recovery information, or private authentication data. A public display name should not contain those details either.
Mute reduces what you see. Block prevents incompatible social contact. Report preserves the selected message and review context for moderation. System messages are game-authored and visually identified; an ordinary player cannot legitimately impersonate that scope.
Public player inspection is intentionally narrow. It may show a display name, level, appearance, safe world or channel context, and permitted party state. It does not show email, wallet address, private inventory, DUST balance, token holdings, session information, moderation details, block reasons, or staff notes.
Account and session safety
Use one active play tab for the same player when possible. Multiple tabs can replace a realtime connection or create confusion about which interface holds the current state. If a session is interrupted, refresh from an official route and retrieve authoritative state rather than copying credentials between tabs.
Maintenance notices can temporarily prevent entry or a gameplay operation without changing wallet ownership or saved data. Read the notice, expected return information, and safe public action. No genuine maintenance page needs private wallet recovery material.
If you report a technical problem, include the public route, visible message, device and browser type, approximate time, and safe receipt reference where applicable. Remove wallet signatures, full authentication data, and private user information from screenshots.
Respond to suspicious behavior
Leave an unsafe interaction, mute or block the player, and report the relevant message through the official control. For a suspicious wallet prompt, reject it first; do not continue merely to collect evidence. Preserve only safe context that does not reveal credentials.
Starville can use risk signals and moderation review, but heuristics alone should not automatically determine guilt. Reports, evidence, review states, and account actions follow controlled staff workflows. Exact anti-abuse thresholds and internal evidence are not public.