Scope and necessary information
This page explains data handling for accounts, community discussions and private consultations. Public guides do not require sign-in. For an account, we process your email, nickname, assigned account ID and member or administrator role. You do not need an HKID number, passport, bank card or complete application file to register.
Share only what the task requires. Describe experiences without identifying people, and avoid unrelated details about relatives, employers or others even in consultations. Do not put documents, banking numbers, addresses, passwords or verification codes in text where they are unnecessary.
What is processed and why
| Information | Purpose |
|---|---|
| Email, nickname and account identifier | Verify sign-in, associate content with its owner and show a nickname in discussions. |
| Posts, replies, categories and times | Provide discussions and search, display current content status and support moderation. |
| Saved-discussion records | Display saved discussions in your account. |
| Private consultation subjects, text, replies and status | Support follow-up between the owner and administrators. |
| Report reasons and moderation action records | Investigate breaches, review decisions and administer the community. |
| Code verification records, request times and a request-source hash | Limit abuse, enforce expiry and attempt limits and prevent code reuse. |
Search terms are sent to this site and may appear in the page URL to retrieve relevant content. Do not search for document numbers or other sensitive details. The site currently uses no advertising trackers or third-party behavioural analytics scripts. Hosting and email services may still keep operational logs.
Who can see public and private content
- Approved posts and replies are readable by visitors, including nickname, category and time. They can be copied, shared or indexed. Public discussion pages do not display the account email.
- Pending or hidden content is accessible to its relevant author and administrators under access controls. A link alone does not give another member permission.
- Private consultations and replies are accessible only to the owner and administrators, who can read and answer them when handling the issue. They do not appear in public community lists.
- Reports and moderation records support administration and are not public member information. Saved-discussion lists are retrieved for the signed-in account.
Email verification and abuse prevention
Sign-in uses a six-digit one-time code valid for ten minutes with up to five attempts. Resending invalidates the old code. Requests have a 60-second interval and limits by email and request source. The application database stores a keyed verification value and delivery and use status rather than the plaintext code. The rate-limit source is also hashed: a configured trusted proxy can supply an IP, while an unconfigured deployment uses a shared source identifier.
Delivery requires passing the recipient address and code-containing message to the configured mail service. Missing configuration or sending failure returns an error and does not establish a verified account. Never share a code. The fact that it is delivered by email means the mail service handles the message content.
Storage, service providers and safeguards
Account and community records are stored in a server-side database. Server checks enforce sign-in, ownership and administrator permissions for access and changes. User content is rendered as text rather than executing submitted HTML as page scripts. Attachments, member direct messages and payment-data processing are not provided.
Mail delivery, hosting and database maintenance can involve the relevant providers or authorised maintenance personnel. Providers, processing locations and operational logging depend on deployment; the platform does not claim every record is necessarily stored only in Hong Kong. The private-consultation label is not a reason to submit unnecessary highly sensitive documents.
Deletion, expiry and retained records
Deleting a post or reply removes it from public view, but its text, deletion marker and moderation records remain in the database. Hiding content, closing a consultation, code expiry or session expiry does not immediately erase all related records. There is currently no uniform automatic deletion schedule, so deletion is not immediate permanent erasure.
You can ask administrators to access, correct or handle account records. They will check your identity, which records are involved and whether any need to be retained. Do not submit sensitive information to test deletion. Removing content from the site cannot retrieve copies other people have saved or shared.
Your controls, access and correction requests
- Review your posts, replies, saved discussions and consultations in your account. Edit or delete your own discussion content or remove a saved discussion.
- For access to or correction of personal data, sign in and use a private consultation to identify the request, account and records involved. Reasonable identity checks may be needed; complete documents should not be requested in a public discussion.
- The site does not currently offer self-service account closure, a full data export or one-click permanent deletion. Tell an administrator what you need so they can explain the available options and any records that must be retained.
- If you suspect account misuse, secure your email, sign out on untrusted devices and report relevant times and circumstances through the site. Do not provide passwords or one-time codes as proof.
The Office of the Privacy Commissioner for Personal Data provides official information on access and correction rights. The site contact process does not replace applicable legal rights or routes for seeking help from the relevant authority.
Contact and policy updates
For privacy or data requests, contact administrators through a private consultation. Use “Privacy and data request” as the subject and explain what you need. Please use this site contact route and keep personal details out of public discussions.
Changes to account features, data collection, service providers or retention arrangements require this page to be revised and dated. You can return to check it at any time. If the service behaves differently from what is described, let administrators know through the site contact channel.