Privacy

Anonymous visitors and access logs

On a first home-page load, the browser receives a random ob_vid cookie for one year so repeat visits from the same browser can be deduplicated in visitor statistics. It is not a name, phone number or account, and the public board can be browsed without registration.

Heartbeat requests record the path, the first referring page and the browser User-Agent for page-view reporting, obvious bot/script filtering and service troubleshooting. The current implementation has no third-party analytics SDK and does not expose these fields to other visitors.

As on most websites, server access logs also record the request IP, time, method, URL, User-Agent and response status for security review, crawler observation and troubleshooting; log files rotate by size.

WeChat authorisation and payment

When you bid inside WeChat, WeChat web authorisation returns an openid. The site stores it in an httpOnly cookie for 30 days only to bind JSAPI checkout to the current payment flow; a separate hint cookie only prevents repeated redirects. The openid is not written to the public board.

Checkout is handled by WeChat Pay. The site keeps listing, amount, order, payment-status and timestamp records so confirmed payments can take effect, public bid history can be shown and genuine errors such as duplicate charges can be reconciled. The site does not handle bank-card details or payment credentials.

Use, retention and choices

Access and order data are used to provide the board, statistics, payment confirmation, abuse prevention and dispute handling. The current code has no visitor account centre or automatic deletion endpoint, so some operational and reconciliation records may remain for as long as those purposes require.

You can stop using the site and clear browser cookies; that does not erase public listings or paid bid history already recorded. For payment reconciliation or help, message the WeChat official account 希望之地Service (WeChat ID: wwwcc8cc) with the time, amount and listing link.