Privacy Policy

Last reviewed: October 22, 2026

This page describes the current site setup. The site operator still needs to set the applicable legal contact, retention period, and jurisdiction before launch.

Information collected

When you create an account, the site processes your username, email address, and password verifier. The login code expects the password to be stored as a one-way hash. The cart is stored in a PHP session. Wallet credits, debits, order records, and their reasons/references are saved in the database. Wallet top-up requests store the amount, external payment method, receipt/reference, optional buyer note, and review status/note. Seller shop profiles store the shop name, description, and uploaded logo/banner files. Verification requests store the requested badge level, fee, decision, and review note. Seller withdrawal requests also store the payout method and destination provided by the seller, plus admin payout references and notes. If you use Contact Support, your name, email address, and message are saved in the site's contact_messages table for manual review.

Account access records

When an account is created or successfully signs in, the site records the event time, account, IP address, and (when available from a configured trusted proxy) country code. Administrators can review these records for account security and support. The site does not currently enforce an automatic deletion schedule for access records; the operator must define and apply an appropriate retention period. If trusted-proxy headers are not configured, the recorded address is the web server's connection address and country is left unknown.

How information is used

Account details are used to sign you in. Session data is used to keep your cart and login active. Shop profile and verification details are displayed to marketplace visitors or used for admin review. Wallet and withdrawal records are used to display balances, record wallet purchases, review submitted top-up receipts, and let the administrator arrange seller payouts. Top-up details are reviewed by an administrator; they are not sent to an automatic payment provider. The seller can see their own withdrawal details and status; site administrators can see the payout destination to arrange payment. Support messages are not emailed automatically; a site operator must review them in the database.

Orders, payments, and escrow

NOWPayments and other automatic payment processing are not connected. Buyers can submit a wallet top-up request with an external payment method and receipt/reference; this is only a request, not proof of payment or a wallet credit. An administrator must independently confirm receipt before approving the request and adding funds. Wallet purchases update balances and order records. Seller payout details are entered for manual payment processing. Do not enter passwords, PINs, or one-time codes in wallet or payout fields.

Service providers and page assets

The site requires a hosting/database provider to operate. Pages also load Bootstrap and font assets from third-party CDNs, which may receive technical request information such as your IP address and browser details. The site operator should review and list any additional providers used in production.

Retention and your requests

Contact messages and account access records do not currently have an automatic deletion schedule. They remain in the database until the site operator removes them under a retention policy. To ask about, correct, or request deletion of information, use Contact Support. Email notifications are not configured, so requests are reviewed manually.

Cookies and security

PHP session cookies support sign-in and cart state. Do not send passwords, recovery codes, or payment credentials through the support form. This page does not claim a security certification or guarantee that data can never be accessed improperly; the operator must maintain suitable access controls, backups, and retention practices.