What information this policy covers

Request logs with truncated IP addresses support website stability and security, while aggregate statistics without identifiers help assess page readership. Individual records and aggregate measures therefore have different purposes, without personal profiling of visitors.

The website has no visitor login, comments or newsletter. Editorial enquiries can be sent through the contact-page form or by email. The form collects a reply address and message; the website forwards them to the editorial mailbox without storing them in a separate enquiry database. Advertising pixels are not provided for, and no advertising-profile cookie is used. The table below therefore marks that category as unused, rather than concealing a form of advertising data collection.

The cookie saves only the browser’s language choice, which concerns the interface rather than a gaming account. Retention starts when the choice is made and ends when the cookie automatically expires, or earlier if the user clears browser data.

Purposes, recipients and retention periods

Each category’s period starts from its own event. For a log, this is the web request; for ordinary correspondence, the closure of the conversation; for a backup, its creation. A single visit date cannot replace them. Deleting a technical log also does not mean every email and all its copies are deleted at the same time.

Visitor data and retention periods
Category Purpose Recipient Period and starting event Deletion
Web request log with a truncated IP address Website stability and security Editorial hosting administrator 14 days from the request Automatic removal from the working log
Aggregate statistics without an identifier Assessing page readership Editorial team 13 months from aggregation Deletion of the aggregate month
Editorial email or form message Responding to an enquiry Editor and project email service 180 days after the conversation closes Deletion of correspondence from the working mailbox
Personal data email Fulfilling the enquiry Responsible editor 180 days after fulfilment Deletion of the working record
Email backup Recovery after a failure Backup administrator 30 days from backup creation Backup rotation; deletion from the working mailbox does not immediately shorten an existing backup’s retention
Language-choice cookie Saving an interface preference Visitor’s browser 180 days from the choice User clearance or expiry
Advertising-profile cookie Not used No transfer No retention Not applicable

Request logs and aggregate statistics

The editorial hosting administrator retains a web request log with a truncated IP address for 14 days from the request, after which it is automatically removed from the working log. Its purpose is website operation and security, without building an advertising profile of the reader.

The editorial team uses aggregate statistics to assess page readership. They contain no identifier and are retained for 13 months from aggregation. The corresponding aggregate month is deleted. This differs from an individual request record: the longer summary period does not mean the original log is automatically retained for the same 13 months.

Emails and when retention starts

Editorial correspondence is retained for 180 days after the conversation closes. Its recipients are the editor and the project’s email service. At the end of the period, correspondence is deleted from the working mailbox. While you are clarifying an enquiry, the sending date cannot be treated as the closure date: the period starts when communication ends.

For a personal data email, the period is also 180 days, but starts when the enquiry is fulfilled. The recipient is the responsible editor. The working record is deleted when the period ends. The same number of days does not merge this category with ordinary correspondence: their purposes and starting events differ.

A backup is separate from the working mailbox

The backup administrator receives an email backup for recovery after a failure, retaining it for 30 days from creation before deleting it through rotation. Deleting an email from the working mailbox does not immediately shorten this separate retention cycle.

When requesting deletion of correspondence, remember that the working record and recovery copy are held separately. An action in the working mailbox does not promise immediate disappearance from every backup, whose retention period depends on its creation date.

Language preference and no advertising cookie

The language-choice cookie is retained for 180 days from the choice. Its recipient is the visitor’s browser. The user may clear the preference earlier. This is not a request to delete an editorial email: the browser value and correspondence are processed separately and have their own retention periods.

No advertising-profile cookie is used, so this category has no transfer, retention period or deletion process. Choosing a language is not consent to advertising profiling or a subscription to a newsletter that does not exist.

How to contact the editorial team

Send personal data questions to [email protected] and comments on articles to [email protected] , matching the channel to the subject: visitor data processing or an article correction.

When requesting an article correction, provide the page address, disputed passage and explanation. This lets the editor identify the exact place your comment concerns. Passwords, payment documents and full card numbers are not requested through editorial email; they are not needed to describe a text error.

Do not use an editorial enquiry to manage a casino gaming account. PuliBet Guide’s responsibility for its own pages and the described visitor data processing does not extend to gaming transactions or the operator’s document checks, even when an article covers its product.

The project’s purpose is explained on the About PuliBet Guide page, enquiry channels are in contacts , and rules for using the content are in the website terms . These documents concern the editorial website and do not replace the casino operator’s terms.