DEMO PRIVACY NOTICE · UPDATED NOVEMBER 2, 2026
Privacy Policy
This notice explains the current demo's data flow. A locally opened site can still connect to hosted services when configured.
1. Information used by the demo
Checkout uses your selected game and package, player and Zone IDs, payment method and order amount. An optional email address may be sent to the order service. Orders can include timestamps, payment and supplier references, status and internal error details. Backend webhook logs can contain the payment or supplier callback payload; authorized operators may record reconciliation evidence.
2. Why this information is used
Information is used to test account validation, create and track orders, match payment callbacks, investigate errors and avoid duplicate processing. Do not submit unnecessary personal information. The demo does not require your game password, wallet PIN or OTP.
3. Browser storage
The frontend uses localStorage to cache the game catalog, save up to ten recent order IDs with game, date and last-known status, and, in offline/mock flows, save simulated orders. Someone using the same browser profile can access this history. Clear History on Track Order removes only the recent list, not hosted orders or offline receipts. Clearing all site data can also remove offline receipts. Neither action deletes hosted database records.
4. Connected services
When configured, Supabase hosts database records and backend functions. PayMongo or Xendit handles its checkout and payment notifications. A configured supplier can receive game account identifiers and product information for verification and delivery; the current default supplier is simulated. These services may process request metadata under their own privacy notices. Do not enter real payment credentials during demo testing.
5. Receipt access and security
The full random order ID acts as a guest receipt access key; anyone holding it may look up the associated receipt fields. Keep it private and avoid public screenshots containing the full ID. Updated lookup code limits public receipt fields; server credentials and internal review evidence are not intended for public access. No system can promise absolute security.
6. Retention and requests
A fixed automatic deletion schedule is not implemented yet. Local records can be cleared through browser settings; hosted orders, webhook logs and review records require administrator handling. If you need a hosted record reviewed, corrected or removed, contact the person operating this demo. A public privacy contact has not been published yet; do not assume a request was submitted through this page.
7. Before public launch
This demo notice must be updated with the operator's identity, working contact channel, actual service providers and retention practices before a commercial launch. See Terms of Service and Help & FAQs for current limitations.