The current website preview
The event, partnership and correction forms shown in this preview have no submission endpoint and their final buttons are disabled. Sanya Expats does not intentionally receive the values typed into those preview fields.
Normal website infrastructure may still process technical request information when a page is loaded. The final notice must identify the services involved, the information they process, where it may be stored or transferred, and how long it is retained.
Information a future service may need
When real submissions open, the product is expected to need only information relevant to the requested service, such as:
- event, venue or correction details;
- an organizer or submitter contact for editorial follow-up;
- image credits, permissions and visibility choices;
- consent and submission records needed to manage the request; and
- limited security information needed to prevent abuse.
The final form and notice must separate information used privately for follow-up from contact details the organizer explicitly permits Sanya Expats to display.
Purpose, access and retention
Before collection starts, Sanya Expats must document why each field is needed, who can access it, the legal or consent basis relied on, and a deletion schedule. Raw submissions and personal contacts should be limited to authorized editorial or administrative access.
Personal information should not be kept simply because storage is available. Retention periods are not yet finalized and must be stated before launch.
Services, analytics and transfers
The final notice must name hosting, database, security, email, analytics and other processors actually used by the launched service. It must also explain any relevant storage or transfer across borders.
Analytics and newsletter choices are not finalized in this preview. Any future measurement should be limited to useful product signals and any newsletter consent should be separate and optional.
Your choices and requests
A practical route for access, correction, deletion, takedown and newsletter opt-out must be published before the corresponding features launch. The direct privacy contact is still being prepared and is therefore not invented on this draft page.
For a factual problem with public content, you can review the correction form preview; it also does not send information yet.
Before publication
The final wording should be reviewed against the laws that actually apply to the operator and audience, including China-facing personal-information collection and any other applicable jurisdictions. The public version must include a revision date only after it has actually been reviewed and approved.