Fairplay Guide uses this policy to explain possible information handling when visitors read the publication or send a message. When visitors send a message, the site receives the details they submit, such as a name, email address and message text. Hosting systems also process technical records to deliver pages and protect the site. The policy should be updated if the site adds analytics, advertising or embedded services.
Information received
A visitor who writes to the journal may provide an email address, a name and details about a correction or question. The information is used to assess the request and respond where appropriate. Avoid sending account credentials, financial records, medical details or documents that are not necessary for the enquiry.
Hosting, delivery and security systems may produce technical records such as an address used to connect, browser type, requested page, access time and security events. These records help diagnose delivery errors, investigate suspicious requests and maintain site security. Retention is limited to the period needed for those purposes and applicable recordkeeping duties.
Cookies, analytics and embedded tools
A cookie is a small browser file that can remember a setting or support a site function. If analytics are enabled, a tool may process visits and interactions to help understand readership. Browser settings can restrict cookies, though some site functions may behave differently. This policy does not name an analytics company because none was specified.
An embedded player, social widget, comment tool or form provider can receive technical details when loaded. If these features are added, the operator should explain them and review the provider’s privacy terms. A separate game or app service controls its own privacy terms; this publication’s policy does not govern those independent systems.
Providers, sharing and retention
The operator may use hosting, security, email and maintenance providers to run this publication. A provider may process information needed for its task under its service arrangement. The site does not sell visitor contact information. Data may also be disclosed to comply with a valid legal obligation, respond to a security incident or protect the publication from abuse.
Messages should be retained only as long as necessary to answer the request, document an editorial correction or meet an applicable recordkeeping duty. Security logs follow configured operational retention. When information is no longer required, the operator should delete it or remove identifying details where practical. Backup copies may persist until their ordinary replacement cycle.
Safeguards and individual requests
Reasonable access controls and software maintenance can reduce risk, but no website can guarantee absolute protection. Visitors should use care when sending information over email. If you want to ask what information you supplied, or request a correction or deletion, use the journal contact page and identify the correspondence without including unnecessary sensitive material.
If a visitor sends an editorial report, the submitted text may be stored alongside the date it arrived so that the site can evaluate the matter and avoid repeating a corrected error. Personal data should be removed from a published correction unless disclosure is necessary and lawful. The operator should not repurpose contact details for unrelated marketing without a separate lawful basis and a clear notice.
A security provider may use automated systems to identify malicious requests, which can cause a legitimate message to be delayed or blocked. Visitors should not include sensitive attachments in a routine correction report. If the operator enables a form with file uploads, it should limit file types and size, scan submissions and state how long uploaded material is retained.
A privacy request can be sent through the contact route, but identity checks should be proportionate to the information requested. The operator should not collect a complete identity document merely to locate an email. Where a request cannot be fully granted because records must be retained for security or law, the response should explain the limit in plain language.
The site operator should periodically check plugin and hosting settings for new data collection, including spam filters and backup services. This policy must follow the actual configuration rather than assume that a particular tool is in use.
A legal or security duty may limit deletion of a particular record. The policy covers this editorial site, not third-party gaming services or device applications. The journal’s scope is described on About; the disclaimer explains the limits of its content.