PlayLynx privacy policy

Policy scope

This policy covers visits and messages sent to PlayLynx

This privacy policy explains the information that can be involved when somebody reads PlayLynx or chooses to contact the publication. The core guides can be read without creating a PlayLynx account. A visitor should never send casino passwords, payment credentials, identity documents or full account records through the contact page.

External casino websites, social profiles and other destinations have their own privacy practices. Following a link away from PlayLynx moves the visitor into that destination's service. This policy does not describe how another organisation handles information on its own website.

Purpose

Information should support a clear and limited task

Contact details and message text may be used to understand the request, assess the relevant PlayLynx guide and provide a reply where appropriate. A report may also help identify a broken route, unclear label or recurring presentation problem. The message should not be used as a route into an external casino account.

Basic technical records can support page delivery, security, fault diagnosis and aggregate understanding of how the publication is used. They should not be treated as a substitute for information a visitor has chosen to provide. Optional functions should remain separate from what is needed to load and navigate the core site.

The cookie policy explains browser storage in more detail. The contact page explains how to submit a focused editorial or usability message without including unnecessary private information.

Retention and protection

Stored information should remain limited to its purpose

A contact message should be retained only for as long as it remains useful for the request, the resulting editorial record or a necessary operational purpose. Technical records can follow a separate schedule because they support delivery and security rather than correspondence. Information that no longer serves its stated purpose should not be kept merely because storage is available.

Reasonable organisational and technical controls can reduce the risk of loss, misuse or unauthorised access, but no internet service can promise absolute security. Visitors can reduce exposure by keeping messages concise and leaving credentials, identity files, payment details and unrelated personal history out of the form.

If a message refers to another person, the sender should avoid including that person's private information. An editorial correction rarely needs a personal account story. The published sentence, the page address and the reason it appears unclear normally provide a safer and more useful record.

Reader choices

Visitors can control messages and browser storage

You can choose not to use the contact form and continue reading the publication. Browser settings can remove or block stored values, although a setting may affect functions that depend on them. The cookie page gives a plain-language route through those controls without assuming that every browser uses identical labels.

A person who has already sent a message can use the same contact route to ask about the information involved, request a correction or raise a deletion concern. Include enough detail to identify the correspondence, but do not resend the full message or add sensitive information.

This policy should be read alongside the site terms and editorial policy. The first covers use of PlayLynx, while the second explains how publication corrections and named authorship work.