ZoniShop

Privacy Policy

Last reviewed: November 4, 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 and description. Any logo/banner files uploaded before custom branding was disabled may remain in storage, but public shop pages use ZoniShop's standard branding and no longer display those seller images. 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 approximate country code when available. For account registration, successful sign-in, and online-presence country checks, a configured trusted Cloudflare country header is preferred. Otherwise, for a valid public IP address, the site may send that address over HTTPS to Country (country.is) to determine its country; Country states that it does not log API requests. Private or reserved addresses, blocked outbound requests, and unavailable lookup results remain unknown. Administrators can review the stored access 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. Without trusted proxy headers, the recorded address may be the web server or proxy connection address rather than the visitor's address.

Online presence

While signed in, site pages send a small status check about once a minute. A browser session is shown as online if a check arrived within the last 3 minutes. Administrators can see the account, IP address, approximate country, and last-seen time. Each browser session is tracked separately using a hashed session reference rather than the raw session ID. Logging out removes its live-status record, and older inactive records are cleared when the administrator opens the Online Users page. This indicates that a signed-in page is open, not that the person is actively typing or clicking. Anonymous visitors are not included.

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, cart state, and online-presence checks. 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.