Contact & data deletion
Operator and data controller: 何耀 (He Yao)
Email us to access, correct or delete data, or report privacy and security issues. No game login or registration with another service is required. See the request steps.
01 · Operator and scope
He Yao, an individual developer, operates Riichi Parlor VR (project name: VR Mahjong; application package: com.ludocove.riichi). This policy covers the game, its related online services and this privacy policy website.
Guest and Meta login use separate game identities; their match histories are not automatically merged. Meta-related processing occurs when the relevant features are available and you use them.
02 · Data we process and why
Login and authentication
Guest mode stores a randomly generated game identity and login credentials on your device. If you choose Meta login, we use the Meta platform to obtain your app-related Meta User ID, nickname/display name, profile image information and a temporary authentication proof to verify identity and app access, create or recover a game account and associate match history.
Our server stores the mapping between your Meta User ID and internal game ID. The temporary proof is sent to Meta for verification and is not persistently stored in its original form; we retain a hash to prevent replay. Login state, credentials and relevant identity/nickname caches are stored on the device. We do not collect your Meta password.
Profiles and table display
With Meta login, your nickname and profile image appear on your own profile and on player plaques at your table. Game clients use Meta platform identifiers to look up these profiles. Images are loaded into memory from Meta image services; the current implementation does not save image files in our game database or the app’s disk cache. Guests use a system-assigned guest-plus-digits nickname and a built-in avatar. Profile editing is currently unavailable. Nicknames are sent to players at the same table as part of room information.
Gameplay and match history
We process internal game IDs, rooms and seats, gameplay instructions, game state, and connection/reconnection information. We store completed-match times, scores, ranks, round outcomes and settlement statistics to provide multiplayer gameplay, session recovery, personal statistics, service security and fair play. Public game state, seats, scores, nicknames and images needed for play are shown to players at the same table.
Operations and analytics
We and our hosting providers process IP addresses, request times, connection status and errors to deliver network services. Game logs may include room, match and internal player identifiers. When basic operational measurement is enabled, we record first/most recent logins and active dates to produce user, activity, retention and match summaries.
Additional diagnostic analytics are currently disabled by default in release configuration. If enabled, they process app version, platform, device model, OS version, language, random session IDs, and login, room entry, match start/end, disconnection, reconnection and error events. Depending on configuration, these can be linked to an internal game ID to diagnose faults and assess gameplay. The current version has no player-facing diagnostics toggle; contact us by email about related requests. We will meet applicable notice and consent requirements before enabling or changing this processing.
Device interaction, this website and email
Headset/controller poses and hand tracking are used on the device for VR interaction; our current game server does not collect this raw tracking data. We do not actively collect microphone recordings, camera images, room scans, contacts or precise location.
This policy website has no ads, analytics scripts, forms or cookies set by us. Cloudflare still processes network requests to provide hosting and security. If you email us, we receive your email address, message and information you choose to provide to handle your inquiry or request.
04 · Retention and security
- Accounts, match history and basic activity records: retained as needed to maintain accounts, historical statistics and operations. There is currently no single automatic expiration period. You may request deletion at any time; after verification, we will handle data that is no longer needed.
- Additional diagnostic analytics: if enabled, the default retention configuration is 30 days. Linked records and cleanup backlogs may delay actual removal. This period does not apply to formal match history.
- Game server logs: production application logs normally use 14-day retention, and operations/game logs 30 days. Storage limits can remove them earlier. These periods do not describe all provider logs.
- Backups: existing routine database backups have a 7-day expiration lifecycle; actual removal may be delayed. Deletion requests also cover assessment of other operational snapshots, exports and identifiable copies. Backups awaiting expiry are not used for routine business, and completed deletions must be reapplied after restoration.
- Correspondence: retained only as needed to resolve and follow up requests and maintain necessary handling records, with periodic review.
We use measures including HTTPS, restricted service/database access, encrypted server storage and credential protection. No system can guarantee absolute security. Necessary legal or security retention must be limited in purpose and duration; we will explain if immediate deletion is not possible. Aggregates that can no longer identify or be linked to a person may be retained.
05 · Access, correction and deletion
Wherever you live, you may request deletion of your game account or related data by emailing yeah7437@gmail.com. Suggested subject: “Riichi Parlor VR data deletion”.
- Tell us whether you use guest or Meta login, your game nickname and what you want deleted. An approximate recent play time may help locate the records.
- We will reply and verify identity using only what is necessary to prevent unauthorized deletion. Do not send passwords, login credentials, temporary authentication proofs or identity documents.
- Once verified, we will delete or irreversibly de-identify relevant data without undue delay and within applicable legal deadlines, and explain completion and any necessary retention. We may remove identity links from match records to preserve other players’ records.
Deletion can permanently remove your account, history or recovery ability. Logging in again later may create a new game identity. Uninstalling the game or clearing device data does not automatically delete server records. Deleting data we hold does not delete your Meta account or Meta’s own records; those requests must be directed to Meta.
You may also request access or correction, or exercise applicable local rights to restrict processing, object, obtain a copy/portability or withdraw consent. Withdrawal does not affect the lawfulness of earlier consent-based processing. Online features may be unavailable if necessary game data cannot be processed. You may complain to a data protection authority with jurisdiction.
06 · Age, updates and contact
The game is intended for teenagers and adults aged 13 or older, or the applicable local minimum age. It is not directed at children below that age. If you believe we have collected data from a child below the applicable age, contact us so we can investigate and delete it.
We will update this policy and its effective date when our processing or services change. Material changes will be communicated through appropriate channels, with consent obtained where required. We retain historical policy versions. Send privacy questions, rights requests or security vulnerability reports to yeah7437@gmail.com.