1. Service and contact
VocaRoom is provided by LXXStudio and offers invitation-based text chats and automatic translation. Registration is not required to use the app or buy credits. Contact msfc136@163.com for privacy, safety, data requests and order support. This document describes the current version.
2. Installation and anti-abuse identifiers
The app generates a random installation identifier for membership, credits and purchase ownership. To limit repeated welcome and referral rewards, it also reads Android ANDROID_ID and computes a purpose-prefixed SHA-256 digest on the device before sending that digest to our server. The raw ANDROID_ID is not uploaded in this request. The digest can still link device risk and reward eligibility; it is not fully anonymous. This feature does not read IMEI or a hardware serial number. Reinstalling or changing devices may prevent recovery of the original installation identity, consumed purchase credits and local history. The risk digest is not an account recovery mechanism.
The same device digest also supports group safety, including restricting a removed device from rejoining the same group. It does not reliably identify every cloned or reinstalled app. Contact support for human review of restrictions or reward eligibility.
3. Messages, drafts and translation
The server processes display names, chat codes, membership, selected display languages, message text, translations, timestamps and delivery state. Text requiring language detection or translation is sent to Google Cloud Translation. Your actual input language may differ from your selected display language. To avoid failed sends when credits are insufficient, the app may submit the current draft to our server after a typing pause and before you press Send. Ambiguous drafts may also be sent to Google for language detection. An unsent draft is not delivered to the other participant as a chat message. The short-lived detection cache stores a text digest and language result; this does not mean Google or infrastructure providers do not process the request text.
International groups also involve group names, group display names, member roles, membership status, invitation links and expiry, removal and blocking records, message references, withdrawal markers and read progress. Messages are made available to eligible group recipients; a translation into the same target language may serve multiple members. Relevant members can see group display names and messages.
4. Purchases, refunds and referrals
We process Google Play product identifiers, order numbers, purchase times, prices and currencies where available, purchase/consumption/refund states, test-purchase flags, installation-related obfuscated identifiers, and purchase-token digests and necessary encrypted token copies for verification, delivery, consumption retries and refund synchronization. Refund reasons, explanations, review notes and audit events support request handling. We do not receive or store full payment-card numbers or security codes. Referral relationships, campaign snapshots, deadlines, qualifying character counts, device reward markers and credit-ledger records support rewards and abuse prevention. They are not deleted with chat caches.
5. Analytics, logs and infrastructure
Servers and network providers process IP addresses, access times, request metadata and errors for operation, security and troubleshooting. Builds with Firebase Analytics enabled also process product events, app-instance identifiers and related technical information. We do not intentionally include message or draft text, display names, chat codes, purchase tokens or free-form report text in Analytics event parameters. Google Play Billing and install attribution services process purchase and attribution information for their functions. Background Firebase push is disabled in the current version; relevant disclosures will be updated if enabled later. Our server is hosted in Hong Kong; Google and other providers may process data in other regions.
6. Retention and security
Downloaded two-person and group history is stored on your device and may remain until relevant local records are deleted, app data is cleared or the app is uninstalled. Expiry of server caches does not automatically erase copies on all devices. Local storage is not an account cloud backup and does not guarantee recovery after reinstalling or changing devices.
Message bodies are encrypted at the application layer in our server database and transmitted over HTTPS/WSS. Our server can decrypt messages for translation and delivery, so this is not end-to-end encryption. Reliably delivered and read two-person messages become eligible for cleanup after approximately 24 hours; other reliable-delivery caches after approximately 72 hours. Group messages become eligible for server cleanup after 72 hours from creation. Periodic jobs perform cleanup and failures may delay it.
Group details, memberships, removal and anti-abuse records, purchases, balances, refunds and safety records are not all deleted with message bodies. They are retained as needed for processing and applicable obligations. Backups, access logs and providers have different retention periods. Contact support to request data handling information or deletion and learn what must be retained.
7. Purposes and disclosure
We use data for chat, language detection, translation, payments, rewards, support, security and troubleshooting. Google Cloud Translation, Google Play, Firebase when enabled, and hosting/network providers process necessary data within their service functions. Chat messages are shared with your selected chat participant. We do not sell personal or chat data for advertising. Necessary information may be disclosed to handle reports, protect rights or comply with legal obligations.
8. Your choices and requests
You can block, report, leave chats and delete local history. Deleting local history does not automatically delete the other participant’s copy or server purchase ledgers. Email us to request access, correction or deletion. We verify your relationship to the data and explain any information that must be retained for applicable obligations, fraud prevention or financial records. Keep access to the device and visible order numbers to help verification; do not send passwords, full payment-card details or purchase tokens. Users must meet applicable age requirements; the service is not directed to children. Material changes will be reflected in an updated policy and notices where required.
Local deletion differs from withdrawal. Withdrawal updates message presentation in supported clients; it cannot guarantee removal of content already seen, copied or captured, and does not immediately physically erase every server record. Leaving or dissolving a group does not automatically delete members’ saved copies.
9. Region-specific privacy rights
Subject to applicable law and its conditions, you may also have rights to obtain a copy of your data, restrict or object to processing, request data portability, and withdraw consent for processing based on consent. Withdrawal does not affect the lawfulness of earlier processing. You may complain to the competent data protection authority in your region. Specific rights, exceptions and response periods in the EU/EEA, the UK and other regions depend on applicable law. We request only necessary verification information and respond within applicable periods, explaining any refusal or partial fulfillment. Contact support for human review of questions about automated anti-abuse restrictions or reward review.