Privacy policy

1. Information and purposes

Account services use your registration email, nickname, hashed store password, optionally bound mobile number, login and device records for registration, verification, account management and security. Store login passwords are not stored in a directly recoverable form.

Transactions and after-sales use product options, amounts, payment status, payment evidence, refund records, contact details and order notes to verify payment and fulfil orders. Hide unrelated bills, balances and personal information in screenshots.

Top-up details may include a game account, server, UID and sign-in method. Submit third-party passwords or verification responses only where necessary for the ordered service, through the order form. Change the third-party password afterward. Never provide bank or payment passwords or unrelated codes.

Support messages, images, conversation times and order links are kept for answers, after-sales and dispute review. Do not send passwords or verification codes in chat or email.

2. Access logs and browser storage

Page access logs contain IP address, browser or device details, time and page path for troubleshooting and abnormal-access review. They are separate from optional marketing analytics. Declining analytics does not stop these logs. Their current retention window is 30 days; the record limit may cause earlier cleanup.

After you allow analytics, this site stores a random browser visitor identifier and uses hashed account identifiers to count visitors and product clicks. Raw visitor identifiers are not stored in these records. These visitor and behavior records are retained for 30 days, up to 100,000 records per type. Turning analytics off stops visitor linkage; successful cart additions and new orders may still be counted from server results without visitor identifiers.

An approximate country or region may be inferred from IP for language, currency and sign-in options. This is not precise location. You can change language and display currency manually.

Cookies support sessions, sign-in and request security. Browser storage holds theme, language, currency and notification preferences. Clearing browser data may require signing in and choosing preferences again; it does not delete server accounts or orders.

3. Optional analytics and marketing email

After analytics consent, the store may record referral, campaign and creative labels, product views, cart and checkout steps and associated payment, refund and delivery events. Click labels and random visit identifiers may be used. Source attribution covers up to the preceding 30 days; this is not a deletion deadline for all analytics records.

If conversion reporting is enabled, configured adapters may receive event and order identifiers, campaign and click labels, amounts, currency and purchase or refund events. These events exclude top-up passwords and verification codes. Review the recipient and handling rules before using such channels.

Decline or disable later analytics in Data preferences without losing browsing, ordering or support. Withdrawal does not automatically delete earlier records or recall sent events. Contact support to request access or deletion.

Promotional and repeat-purchase emails require a separate subscription. Disable them in preferences or use the email unsubscribe link. Order email settings are in Devices and notifications. Verification email initiated by you, such as password recovery, is not marketing email.

4. Third-party services

Enabled email or SMS services handle the destination and verification or notification content. Enabled payment services handle order identifiers, payment amounts, currency and results. Available methods are shown at checkout.

Where Google sign-in is enabled, choosing it redirects to Google authorization. The store receives the account identifier, verified email and profile name to identify or create your store account; it does not receive your Google password.

Server, backup and service locations and possible cross-border processing depend on the services selected. Any separately required notice or consent must be provided before the relevant processing; accepting this notice does not replace it.

5. Retention and protection

Main business records use server-side encrypted storage and account ownership and staff permission checks. Support chats and images are stored separately with access controls and are not within that business-record encryption scope.

Automatic cleanup is disabled: completing an order does not automatically delete passwords or verification codes. Contact support to request cleanup.

Order, payment and refund records are separate from passwords and verification codes. Cleaning sensitive fulfilment details does not delete transaction records. Records needed for lawful obligations or unresolved orders and disputes are restricted to those purposes; other information can be requested for deletion.

There is currently no single automatic deletion deadline for accounts, support conversations, marketing analytics or backups. Historical backups are not immediately changed when current order details are cleaned. Support should explain what can be deleted, what must remain, why and the expected process; instant deletion of all copies is not promised.

6. Access, correction, deletion and account closure

Use account pages to edit details, change a verified email, end other sessions and adjust notification or marketing preferences.

Request access, a copy, correction, deletion or account closure through support, describing the request and related account and order. Do not provide a password or complete verification code as identity evidence.

Support must verify the account holder and explain the result. Open orders, wallet funds, refunds and disputes may require settlement and follow-up arrangements. Required retained information needs an explanation of scope and basis. Closing an account, clearing browser data and deleting all orders are different actions.

7. Minors and updates

Minors should use the service with guardian guidance. Information about children under fourteen may require guardian consent and additional protection under applicable rules. There is no dedicated guardian verification flow at present; guardians should contact support before submitting such details.

This notice shows its version date. Changes to purposes, methods or information types that require fresh consent must be separately notified and confirmed. Continued browsing does not imply consent to new processing.