This privacy policy explains what information is handled when someone visits RiskNews, uses the site search, follows an external source link or contacts the editorial team. It applies to pages served from risknews.org.cn. External websites linked from an article have their own policies and controls.
Information handled during a visit
The web server may record standard technical information needed to deliver and protect the site. This can include the requested page, request time, IP address, browser user agent, referrer and response status. These records are used for reliability, security review and basic traffic analysis.
RiskNews also uses a first-party traffic measurement script served by board.colorfun.com.cn. The script creates a random visitor identifier in local storage and a short-lived session identifier in session storage. It can send the site domain, page path, page title, referrer, browser language, screen dimensions, time zone and those random identifiers. The script is designed to avoid administrative pages and does not intentionally collect a visitor's name, email address or article text.
Cookies and browser storage
The content management system may set a session cookie so pages and forms work consistently. It may also set a language preference cookie. The traffic measurement script uses local storage for a random visitor identifier and session storage for a session identifier and duplicate-page-view control. Browser settings can be used to block or clear cookies and storage. Blocking them may affect search, forms or traffic measurement, but ordinary article reading should remain available.
Search and correspondence
Words entered in the site search are processed to return matching pages and may appear in routine server logs. If a reader contacts RiskNews, the correspondence will contain the information the reader chooses to provide, such as a name, email address, organization, question or correction request. Do not send confidential supplier files, identity documents, payment records or other sensitive material unless a secure method has been agreed in advance.
Why this information is used
- To deliver pages, search results and contact functions.
- To detect abuse, investigate errors and maintain site security.
- To understand which topics and navigation paths are useful to readers.
- To answer editorial questions, correction requests and source inquiries.
- To meet legal obligations or respond to a valid legal request.
Service providers and disclosure
Technical data may be processed by hosting, security and traffic measurement providers that support the site. Information may also be disclosed when required by law, to protect the site and its users, or during a change in site ownership or operation. RiskNews does not sell personal information or use the site tracker to build advertising profiles.
Retention and security
Server logs, traffic records and correspondence are retained only for as long as reasonably needed for the purposes described above, including security investigation, editorial follow-up and legal compliance. Retention periods can differ by record type. Reasonable technical and organizational measures are used to limit unauthorized access, but no internet service can guarantee absolute security.
Reader choices and requests
Visitors can clear or block cookies and browser storage, disable JavaScript, use browser privacy controls or avoid submitting personal details. Depending on applicable law, a reader may ask about personal information connected to their correspondence, request correction or deletion, or object to certain processing. A request may require enough information to locate the relevant record and verify that it concerns the requester.
Children and external links
RiskNews is written for business and professional readers and is not directed to children. Articles often link to regulators, marketplaces and other external sources. RiskNews does not control how those sites collect or use information.
Policy updates
This policy may be revised when the site's tools, legal obligations or operating practices change. The date shown on this page is the effective date of the current version.
Contact
Questions about this policy or a privacy request can be sent through the Contact page. For editorial corrections, use the process described in the Corrections Policy.
