Information We Collect
Data arrives at the site in two ways. Some comes automatically when a page loads. Some comes from visitors who choose to send it through the contact form.
Technical data collected automatically includes IP address, browser type and version, operating system, device type, screen resolution, referring URL (the page or search engine that brought the visitor here), pages visited on this site, time spent on each page, and the date and time of the visit. This is standard server-level logging. Every website with any form of analytics collects similar data. The purpose is understanding how the site gets used in aggregate — which pages draw readers, which devices need testing, where traffic comes from — not identifying individual visitors by name.
Contact form data includes whatever the visitor types into the form. In practice, this means a name, an email address, and a message. The name helps address the response. The email is where the reply goes. The message contains the question, correction, or suggestion. No other fields are collected through the form. No phone number. No physical address. No identity documents.
The site does not require registration. No accounts. No profiles. No stored login credentials. Each visit is treated as a standalone interaction. The contact form creates a communication record, not a user account. If a visitor chooses not to use the contact form, the only data collected is the automatic technical information generated by the page load. This data does not include names, email addresses, or any self-reported personal information.
How We Use Your Information
The uses are specific and limited.
- Responding to messages. Data from the contact form is used to reply to the sender. The email address delivers the response. The name addresses it. The message content determines what the response covers. After the exchange is complete, the data sits in the editorial inbox archive. It is not used for any secondary purpose.
- The site does not send newsletters, promotional emails, or marketing messages. Submitting a contact form message does not enroll the sender in any mailing list. The only email that arrives from the site is the reply to the specific message sent.
- Improving the site. Technical data is analysed in aggregate to understand reader behaviour at a population level, not an individual level. Which articles attract the most visitors. Which pages have high bounce rates, suggesting the content isn’t meeting expectations. Which devices and browsers are most common among visitors, informing testing priorities. Which search queries bring visitors to the site, shaping editorial planning.
- This analysis looks at numbers and trends. Not at individual records. The team does not examine a single visitor’s session path, device fingerprint, or reading behaviour. The aggregate tells the story. Individual records stay in the server logs and are not extracted for analysis.
- Diagnosing technical issues. When a visitor reports through the contact form that a page doesn’t load properly, the technical data associated with the request can help troubleshoot. Browser type, device, screen resolution — all useful for reproducing and fixing display problems.
- Maintaining security. Technical data helps identify and block automated abuse. Spam bots submitting garbage through the contact form. Scraping tools extracting content at scale. Traffic patterns consistent with denial-of-service activity. These protective measures operate automatically and do not affect normal visitor experience.
Cookies Policy
Cookies are small text files that the site asks the browser to store. The browser sends them back on subsequent visits, allowing the site to recognise a returning browser without requiring any identifying information from the visitor.
The site uses two categories of cookies.
- Functional cookies. These handle basic site operations. Remembering a language preference. Maintaining session state so the page doesn’t reset mid-visit. Keeping the cookie consent choice itself, so the visitor doesn’t see the same prompt on every page load.
- Analytics cookies. These help count visitors and page views. An analytics cookie distinguishes one anonymous browser from another anonymous browser. It does not identify the person behind the browser. The data it generates feeds into aggregate statistics — total visits, unique visitors, page popularity — without connecting those numbers to names, email addresses, or any personal identifier.
The site does not use advertising cookies. No retargeting. No cross-site tracking. No behavioural profiling for ad delivery. No data shared with advertising networks.
Visitors can manage cookies through their browser settings. Every major browser — on both desktop and mobile — allows blocking all cookies, blocking only third-party cookies, clearing cookies on exit, or deleting specific cookies manually.
Blocking all cookies will not prevent the site from loading or its content from being readable. Some preferences may not persist between visits. The cookie consent banner may reappear. These are minor inconveniences, not functionality losses.
Incognito or private browsing mode automatically clears cookies when the browser window closes. For visitors who want zero cookie persistence without changing their default browser settings, this is the simplest path.
Third-Party Services
The site uses a small number of external services to operate.
- Content management system. The CMS that powers the site runs on its developer’s platform. Plugins and extensions used on the site may process data according to their own policies. Updates to the CMS and its plugins are applied regularly for security.
- Analytics. A standard analytics platform processes visitor data in aggregate. The service receives technical data — IP, browser, pages visited — and returns statistical summaries. The analytics provider has its own privacy policy governing how it handles the data. The site selects analytics tools that align with minimal data collection, but cannot control or audit the provider’s internal practices.
- Hosting and content delivery. The site runs on infrastructure managed by a hosting provider. Server logs are generated and stored as part of normal hosting operations. The provider’s retention policies and data handling practices are governed by their own terms.
- Anti-spam protection. The contact form uses spam filtering to separate real messages from automated junk. The service may analyse IP addresses, form interaction timing, and submission patterns to determine whether a message is from a human or a bot.
Each third-party service has its own data handling standards. The site chooses services that practice minimal data collection, but “minimal” is defined by each provider, not by this site. Visitors with questions about which specific services are currently in use can ask through the contact form.
Data Protection
The site takes reasonable measures to protect data in transit and at rest. Reasonable means practical and proportionate — not theatrical, and not accompanied by claims of absolute security that no website can honestly make.
- HTTPS encrypts all communication between the visitor’s browser and the site’s server. Page loads, form submissions, and any other interaction are protected in transit. An attacker intercepting the connection would see encrypted data, not readable text.
- Access to the site’s administrative systems is restricted to editorial team members. Each has individual credentials. Login activity is logged. Shared passwords are not used.
- The CMS, its plugins, and the server software receive regular updates. Security patches address known vulnerabilities as updates become available. Delaying patches leaves the site exposed to documented exploits, so updates are applied promptly.
- Anti-spam and rate-limiting tools protect the contact form from automated abuse. Submission frequency is capped. Suspicious patterns trigger additional checks.
- Periodic security reviews check for misconfigurations, outdated dependencies, and signs of unauthorized access. External scanning tools supplement the team’s internal checks.
Despite all of these measures, no online system is fully immune to every possible threat. Software vulnerabilities exist. New attack methods emerge. Social engineering targets people, not systems. The site maintains current best practices and responds to new threats as they arise. Promising complete immunity would be inaccurate, so it is not promised. What is promised is a reasonable, maintained, and regularly reviewed approach to data protection.
User Rights
Visitors have rights regarding the data that pertains to them.
- Access. A visitor who has submitted data through the contact form can request a summary of what is stored. The request goes through the same contact form. The team verifies the requester’s identity through the email address used in the original communication, then provides the information.
- Deletion. A visitor can request that their data be removed from the editorial inbox. The request goes through the contact form. After identity verification, the team deletes the relevant messages and confirms completion.
- Correction. If the data associated with a previous communication is inaccurate — for example, the visitor’s name was misspelled in the original message — the visitor can request a correction through the form.
- Opt-out of analytics. Visitors who prefer not to be counted in aggregate analytics can block analytics cookies through their browser settings or use a browser extension that prevents analytics scripts from loading. This does not require any action from the site’s team.
Visitors who have not submitted data through the contact form have no individual-level data stored by the site. Their visits are reflected only in aggregate analytics, which cannot be traced to a specific person.
Links to Other Websites
The site contains links to external resources. Game provider pages. Casino operator sites. Reference materials. Support organisations.
Clicking a link takes the visitor to a domain operated by someone else. That domain has its own privacy policy, its own cookie practices, and its own terms. The content there may be very different from the content here.
This site does not control, endorse, or take responsibility for external destinations. A link in an article means the resource was relevant at the time of writing. It does not mean ongoing partnership, approval, or liability for whatever happens on the linked page.
Visitors concerned about privacy should review the privacy policy of any external site before submitting personal information there.
Changes to This Policy
The privacy policy may be updated. When that happens, the new version replaces the current one on this page. A date of last revision is noted at the top. Continuing to use the site after an update constitutes acceptance of the revised policy.
Major changes may be noted on the homepage or through the contact list for visitors who have previously communicated with the team, but this is not guaranteed for every revision.
Contact Information
Questions about data handling, access requests, deletion requests, and privacy concerns are accepted through the contact form. Including the word “privacy” in the message helps route it to the right person. Responses arrive within one to two working days for standard requests.