Privacy Policy

1. Publisher, controller and privacy contact

The publisher below is responsible for deciding how personal information is used for this website. A site-delivery or analytics supplier may process information on our behalf under its own service arrangements.

Publisher and data controller

Not yet specified for publication.

Website

Pragmatic Wiki · https://play2pragmatic.com/

Contact email

[email protected]

For a privacy question or rights request, use the contact email above. You do not need a player account or a paid service to make a request.

2. A summary of this website’s data use

• There are no player accounts, gambling transactions, registration forms, public comments or newsletter sign-ups on this website.
• Game-name searches, filters and reading controls operate within the page. We do not send their input as custom analytics events or save those controls in cookies or browser storage.
• Game artwork and fonts are served with the website. A game demo or support service opens only when you follow its external link; it is not embedded here.
• Technical requests are processed to deliver and protect the website. Optional Umami measurement is described separately below.

We do not operate behavioural advertising, sell personal information, upload customer lists, assign a logged-in user identifier or make solely automated decisions with legal or similarly significant effects on visitors.

3. Information needed to deliver and protect the site

When your browser requests a page, image or script, the infrastructure handling the request receives technical information such as your IP address, requested resource, request time and browser or device headers. Hosting, network and security services may retain access or security logs under the arrangements described below.

Site-delivery provider

Not yet specified for publication.

Processing locations

Not yet specified for publication.

Access and security log retention

Not yet specified for publication.

The purpose is to deliver requested content, diagnose errors, manage abuse and maintain availability. Where data-protection law requires a lawful basis, our stated basis is our legitimate interest in operating a reliable and secure reference website. Processing required by a binding legal obligation uses that obligation as its basis instead.

A static website can still generate infrastructure logs. The absence of a user account does not mean that no technical information is processed. We do not use delivery logs to build gambling profiles or infer a visitor’s financial circumstances.

4. Optional Umami audience measurement

Analytics on this version: enabled. The configured tracker loads after the page becomes interactive.

When enabled, Umami is used to understand which reference pages are read and to improve the website. Its documented metrics include page paths and titles, referring pages, browser language, screen size, browser and operating-system categories, device type and approximate location.

Umami’s standard web tracker does not use cookies. Its analytics service can process an IP address and browser information to derive location and a rotating session identifier. Not storing a raw IP address as an analytics field is different from never processing it: hosting, proxy or security logs may still contain it. Cookieless measurement is not a promise of absolute anonymity or automatic legal compliance.

Our tracker settings exclude the current page’s query string and URL fragment, request Do Not Track support and turn off optional performance collection. Referrer information may still be sent. We do not call Umami’s identify function, supply a custom visitor ID, send search-box input, record custom click events, or enable session-replay or heatmap features in this project.

Analytics service operator

Not yet specified for publication.

Processing locations

Not yet specified for publication.

Analytics retention

Not yet specified for publication.

Stated lawful basis

Legitimate interests in understanding aggregate readership and improving reference content, only where applicable law permits this measurement without prior consent.

This integration does not display a consent prompt. We do not treat continued browsing as consent. Optional analytics must remain disabled where applicable rules require prior consent that has not been obtained. The right to object and browser controls are explained below.

5. Cookies, browser storage and page controls

The website’s own application code does not set cookies or use localStorage or sessionStorage. Search, filter and appearance settings are held in page memory and reset when that page is reloaded. The URL may contain a section fragment when you follow an article link; this is navigation, not a saved profile.

Umami’s standard tracker is cookieless, but a hosting or security service may have separate technical cookie requirements. Any such services must be reflected in the site-delivery details and this notice before use. Cookie and storage rules on an external provider’s website apply after you follow its link.

You can use your browser’s cookie, storage and script controls. Blocking scripts may disable interactive search and filters; the main reference text and ordinary links remain available in the exported HTML. Cookie controls alone do not block every network request or prevent server-side security logging.

6. Information you send by email

If you choose to email us, we receive your address, your message and any information or attachments you choose to include. The mailto link opens your email application; it does not submit a form to this website. Your email provider and ours also process the message in delivering it.

We use correspondence to answer the request, investigate a correction or complaint, and keep a proportionate record of its resolution. Where a lawful basis is required, this is our legitimate interest in responding to enquiries and maintaining an accountable editorial service, or a legal obligation when handling a legally required request.

Correspondence retention: Not yet specified for publication. A record may be kept longer where a specific legal duty or unresolved legal claim requires it. We limit any such exception to the relevant information and purpose.

Do not send payment credentials, a casino password or unnecessary sensitive information. We do not ask you to disclose a gambling history or medical diagnosis to read the responsible-gambling material.

7. Recipients, external links and international processing

Information needed for site delivery may be available to hosting, content-delivery, security and operational suppliers. Email correspondence is available to the people handling the request and the suppliers needed to deliver and maintain that mailbox. If analytics is enabled, its named service operator receives the measurement requests.

We may disclose relevant information when required by law, to respond to a valid legal process, or where necessary and lawful to protect the website or another person’s rights. We do not give an external casino or game provider your search text or a player profile from this website.

An external link takes you to a different service, which receives its own request from your browser and applies its own privacy rules. Our external links use a no-referrer link setting, but that does not prevent the destination from receiving technical information needed to serve you.

Processing may take place in the locations listed for the relevant service above. Where data is transferred across borders and the applicable law requires safeguards, the relevant arrangements must use a permitted transfer mechanism, such as an applicable adequacy decision or appropriate contractual safeguards. You can contact us for the arrangements relevant to your information; we do not claim a particular transfer approval for an unidentified supplier.

8. Retention and security

The log, correspondence and, where applicable, analytics periods above describe their different purposes. A rotating analytics identifier is not a deletion schedule. Analytics records are not automatically erased merely because a session identifier changes.

We aim to restrict access to those who need it, keep the website and supporting services maintained, and use suitable technical and organisational protections. No internet transmission or storage system can be guaranteed completely secure. Please report a suspected security or privacy issue using the contact details above and avoid including more personal data than necessary.

Where information is no longer needed for its stated purpose, it should be deleted or made no longer identifiable, subject to applicable legal requirements and any disclosed backup or security-log arrangements.

9. Your rights and how to make a request

Depending on the law that applies and the type of information held, you may have rights to access personal information, correct inaccuracies, request erasure, restrict processing and receive or transfer certain data. These rights have conditions and exceptions; not every right applies to every record or lawful basis.

Send a request with enough detail to identify the relevant interaction, for example an email exchange or an approximate request date and page. We may ask for proportionate information to verify identity. Please do not send identity documents unless their need and a suitable method have first been explained.

We will handle requests within the period required by applicable law and explain any permitted extension or refusal. We do not collect extra identifiers solely to identify a visitor in otherwise unidentifiable analytics records.

If you are not satisfied, you can complain to the relevant data-protection authority without first obtaining our permission. In the EEA, consult the EDPB directory of supervisory authorities. In the United Kingdom, the Information Commissioner’s Office provides complaint information. Your local authority may be the appropriate route elsewhere.

10. Browser controls and analytics objections

Our Umami integration sets the tracker’s Do Not Track option. A compatible tracker honours the preference when a browser exposes it. Browser support varies; this setting is not a general consent system and does not stop infrastructure logging.

You can also use script or request blocking to prevent your browser from loading or contacting the analytics service. For an objection that needs action by us, contact the privacy email above. Changing browser settings does not erase records already held; use the rights-request route for a deletion request where it applies.

11. Children and changes to this policy

The website is intended for adults aged 18 or over and does not invite children to register or submit information. We do not knowingly seek personal information from children. If you believe a child has supplied information to us, contact us with enough detail to investigate without sending unnecessary sensitive information.

The “Last updated” date identifies the policy version. We will update the notice when the website’s data practices change, including before enabling a new analytics service or introducing a form. A policy change is not, by itself, consent to a new use of personal information.

For conditions of using the reference material and links, read the Terms & Conditions.

12. Technical references

These references explain the standard analytics technology and general privacy rights. The deployment-specific details in this notice describe this website; a supplier’s general description does not replace them.

• Umami FAQ — cookieless tracking, configuration and retention.
• Umami metric definitions — request data, identifiers and location processing.
• Umami tracker configuration — query, fragment, performance and Do Not Track settings.
• ICO information for the public — UK data-protection rights.