Privacy Policy

Version date: November 10, 2026

Applicable website: demin (domain: demin.men), including its local test version.

Operator and data controller for processing covered by this policy: Zhu Xingwang, an individual operator. Support and privacy contact email: pfrzjw666@qq.com.

1. Scope

This policy describes data handling in the current test version. Real account registration, payments, automatic delivery, official email receipt and subscription-processing services are not connected. Product descriptions of future or third-party processes do not mean this website already collects account information or establish that a third party automatically destroys it.

The verified environment is the local test website. Public hosting and live business integrations may introduce different data flows. Their actual configuration must be checked and this policy updated before those features are enabled. Local test results are not proof of privacy practices on a publicly hosted website.

2. Data currently processed and why

Browsing and interface actions

Your browser requests the on-site files needed to display pages. Product selections, quantities, filters and interface inputs support current-page interactions. The current version has no integrated advertising tracking, third-party traffic analytics or analytics SDK. Accounts, messages and fixed orders in the static examples are demonstration material, not retrieved private email or working account credentials.

Simulated sign-in, pending checkout and demonstration orders

Selecting “Enter local demo” stores a simulated sign-in marker in this browser. When you create a demonstration order, the browser stores its product name, product identifier, quantity, unit price, currency, total, order reference, time and demonstration status. This keeps the storefront, orders page and dashboard consistent. Pending product selections and quantities are temporarily held in browser session storage to restore checkout after simulated sign-in.

These records do not establish real payments, genuine authentication or cloud orders available across devices. They are not currently submitted to the reference website or a live transaction backend. The simulated sign-in marker is only an interface demonstration and is not a security mechanism for real accounts.

Sign-in forms and other inputs

The current sign-in, registration and password-reset pages do not submit information to an authentication service. They display local notices instead. Password-field contents are not saved as real login credentials. Other demonstration forms also do not perform real account operations or send email. Use sample information rather than real passwords, one-time codes, 2FA secrets, session keys or payment-card information.

Invoice drafts and exported files

If you use the Invoice draft tool, the name, email address, tax identifier, address and invoice contents you enter are used for local calculations and printing. Corresponding billing details are saved in the current browser only if you select the option to remember them. Exported or printed PDFs are handled by your browser and device. Clearing website data does not delete downloaded files. A draft does not establish official invoicing or payment.

Support and copying

“Copy WeChat ID”, “Copy WhatsApp account” and “Copy email address” request permission to write the public support identifier to your clipboard. This feature does not read clipboard contents. If you open Telegram or independently contact the store using WeChat or WhatsApp, the relevant platform and the store receive the messages, identifiers and attachments you choose to send. Their respective data practices apply.

For support, provide only what is necessary, such as an order reference, time of the problem and a redacted screenshot. Do not send passwords, verification codes, 2FA secrets or session keys. The store should not request unrelated personal information for an ordinary support issue.

3. Browser storage, retention and deletion

The current version uses browser local storage for simulated sign-in, demonstration orders and billing information you choose to remember. Session storage holds temporary state such as pending checkout selections. The current application does not actively set identity or advertising-tracking cookies. Browser storage and cookies are different mechanisms.

Local storage generally persists until you clear the site's data or your browser removes it. There is no mechanism that automatically destroys all data when a task finishes. Session storage follows your browser's session-management rules, including possible restoration; closing a window is not guaranteed to erase it permanently. Signing out of the demo removes the sign-in marker but does not automatically delete demonstration orders, remembered billing details or downloaded files.

To remove stored records, open your browser settings and clear the site data or site storage for the relevant website address. This removes the simulated sign-in, orders and billing details saved for that address. Record anything you want to keep first. Different addresses have separate storage: clearing the local test address does not clear data for demin.men. Delete unwanted exported files separately.

The store cannot remotely remove records that exist only in your browser on another device. For information already sent to support, you may contact the store to request access, correction or deletion. The scope depends on what is actually held, verification of the request and records that must legally be retained. This policy does not invent a fixed deletion deadline.

4. Servers, hosting and network records

The current local preview server supplies site pages and resources and does not accept form or order submissions. The verified application code does not configure request access logs. This does not mean your device, browser or other infrastructure never records network activity or errors.

The owner has stated that the domain was purchased through Cloudflare. Domain registration alone does not establish that Cloudflare proxying, analytics, CDN or hosting is enabled. This policy does not describe those services as active. If public hosting, proxying, CAPTCHA or payments are enabled later, the actual providers, data processed (such as IP addresses, request times and security logs), purposes and retention arrangements must be disclosed based on the real configuration.

5. Third-party websites and sensitive information

Product instructions may link to subscription services, email services, browser extensions, 2FA conversion tools or a provider's subscription-management page. These are independently operated. Once you open one, its operator may receive your IP address, browser information and anything you choose to submit, subject to its actual practices and policies. Merely displaying a link does not automatically submit demonstration orders or account information to that site.

Passwords, 2FA seeds and session keys may allow another person to access an account. Do not enter working credentials into an untrusted page or extension. Statements in product instructions that information is used only for temporary verification or destroyed when a task finishes were supplied by the processing provider; demin has not verified that provider's backend. They are not a guarantee by demin that third parties retain no data.

The current test version has no live payment data flow, does not collect full bank-card details and does not identify an integrated payment provider. Before introducing live payments, account delivery or another feature requiring personal information, the necessary fields, purposes, recipients, retention rules and choices must be explained. This test policy is not blanket authorization for future collection.

6. Security, choices and changes

Avoid saving personal billing information on a shared device. Sign out and clear the relevant site's data when appropriate. Demonstration accounts and local browser storage do not provide the identity protection of a live transaction system and must not hold real account credentials. No protection can guarantee absolute security. If something appears wrong, stop submitting sensitive information and contact support.

Depending on applicable law, you may have rights to information, access and a copy, rectification, erasure, restriction, portability, objection and withdrawal of consent, as well as a right to complain to the competent data protection authority. Explain your request through the contact channels below. Requests must be handled subject to the conditions and deadlines of applicable law. Withdrawing consent does not affect processing lawfully carried out beforehand. Manage browser-only records as explained in Section 3; the store does not claim it can retrieve data it does not hold or remotely delete local records. Marketing messages, the sale of data for advertising and advertising tracking are not currently integrated. Before adding those uses, they must be disclosed and legally required choices and opt-out methods provided.

This policy will be revised, with an updated version date, as actual features change. New purposes, recipients or processing practices must be explained before implementation, and any legally required authorization obtained. Reading this policy does not replace a necessary choice or consent.

7. Contact

Support and privacy contact email: pfrzjw666@qq.com.

For privacy or data questions, contact Telegram @demin18, WhatsApp @yingladin or WeChat deminnb. Specify the website address and type of data involved. Use redacted information initially; do not include passwords, verification codes, 2FA secrets or session keys in messages.

For services, product-specific warranties and refunds, see the Terms of Service.