Weshachin privacy policy
Updated 20 October 2026. Applies to the Weshachin multilingual word game and its online services.
Publisher: Hiwa Studio. Contact: support@hiwa.studio.
Information processed
Accounts use a username, public display name, a salted password hash and random account/session identifiers. The app does not ask for a phone number, email, date of birth or location. Online features store game progress and claims, tutorial state, submitted words, match scores and times, ranking totals, virtual-coin balances and transactions, recharge-code redemption records, and word suggestions including their meaning and source. Play-credit synchronization uses a random app installation identifier. The shared wallet records earned and restricted coin sources so the iOS app can use game-earned rewards and transfers of those rewards, while externally purchased or unproven legacy coins remain available to Android. Signed earned play-credit receipts bind the amount to the game account and installation to prevent duplicate credits. Administrator account edits are audited. When App Store purchases are enabled, Apple-signed transaction data is verified, and purchase product/amount/environment plus minimal transaction hashes and receipts are stored; payment-card data is never received. Community-rule acceptance/version/time, player block lists and abuse reports/review decisions are stored to provide moderation and safer interactions.
We use these records to provide accounts, multiplayer games, rankings, synchronization, virtual-coin accounting, word moderation, abuse prevention and support. Usernames/display names, ranking points and game results are visible to other players where the game requires them. Recipient lookup shows public player identity so transfers can be checked. Do not use a private real name as your public display name if you do not want it shown.
Network and device data
The service receives IP addresses to deliver requests and limit abuse. Current API request logs omit IP addresses, query strings, account IDs and installation IDs. Older operational logs may contain request paths and identifiers and require operator retention cleanup. The game has no advertising, analytics or crash-reporting SDK, does not sell personal data and does not request contacts, camera, microphone or precise location. Network providers and the hosting provider process connection data to deliver the service. Credentials and online requests use HTTPS. Passwords are stored as salted hashes, not plaintext.
Retention and deletion
Account data is kept while the account exists. Use Delete account on the web or inside the app. Correct username/password confirmation is required, including for blocked accounts. Deletion removes your account, password, sessions, profile, progress, wallet/device receipts, suggestions, block lists, community-rule acceptance, abuse reports made by or targeting your account, and linked administrator profile snapshots. Active games end. Coins and points are lost; deletion is irreversible.
Other players retain anonymous match results and transfer amounts/times without your name or original account ID. Approved ordinary dictionary words remain without attribution. Used recharge codes remain redeemed without user linkage, preventing double redemption. A minimal deletion receipt retains the old random account ID and request-specific identity binding for up to 30 days to resolve interrupted requests. Former usernames are reserved for up to 30 days to prevent impersonation or misdirected transfers, then released. Only an unlinked hash of the spent random request identifier remains afterward to prevent unsafe reuse. App Store purchase records keep transaction hashes, product/amount/environment and per-transaction account-binding hashes to prevent duplicate credits; deletion removes the account link and retry request records. Signed App Store payloads and app-account tokens are not stored. Verified refund notifications are retained as minimal transaction hashes and review status. A restore-protection journal retains hashes of random deleted account IDs without names, credentials or gameplay so old backups cannot reactivate deleted accounts.
The daily game backup job removes snapshots older than 14 days at its next successful scheduled purge and retains at most 14 snapshots. Outages or failed scheduling can delay a purge and require operator correction. They are access-restricted; encryption at rest is not claimed. The operator must apply the same 14-day limit to any manually exported backup and remove copies when no longer needed. A restored backup must be reconciled with the deletion journal before service resumes. Legacy logs and manual backup cleanup must be confirmed by the operator before store publication; publication readiness remains incomplete until those operational checks and publisher contact details are configured.
Your choices
Offline introductory play does not require an account. Online features and later progression require registration. You may delete an account through the web without reinstalling the game. Clearing app storage removes local data on that device but does not by itself delete the online account. The deletion flow in the app clears the matching local account after confirmed server deletion. Copies on other offline devices are cleared when you remove their app data.