How PeraBet Casino & Sports Review handles visitor data

Data and retention periods

Who is responsible for data

Ben Haynes is the publisher and the party responsible for visitor data on PeraBet Casino & Sports Review. This site publishes editorial material about PeraBet but does not manage the operator's gaming accounts or payments. The casino's privacy policy covers a different service; enquiries about data on this editorial site should go to the publisher.

For a general question about an article, use editorial contacts . For a personal-data request, write to [email protected] and identify the information concerned. Do not send a gaming-account password, payment details or documents unless they are needed for an editorial request.

What information the site processes

A necessary cookie remembers the interface language and consent choice. Server logs record technical events needed to operate and protect the site. If you send an email, the editorial team receives your address, message and any details you include yourself. There are no separate contact forms, reader accounts, comments or newsletter in the initial version.

After consent, the site's own Matomo analytics is enabled alongside the editorial site. It helps show aggregate traffic and how pages are used. IP addresses are not included in published statistics. Optional analytics is not enabled without consent; advertising pixels and retargeting are not used.

Table 1. Visitor data and retention periods

The retention period for an email begins when the conversation closes, not when it is sent. A working record may be deleted sooner following a justified request; its backup then leaves the system within its cycle of up to 30 days. Analytics and server-log periods begin with the event.

Cookies and analytics choices

Necessary cookies support the chosen language and remember the consent decision. They serve the interface and do not amount to consent to advertising tracking. Analytics cookies are a separate optional category: Matomo starts processing analytics events after the visitor chooses it.

You can decline optional analytics. To change your choice, use the site's consent controls; for questions about a saved choice, email the publisher's privacy address. The initial version has no advertising cookie category, personalised advertising pixels or retargeting, so visitors are not offered an option to enable that processing.

You can also delete or restrict cookies in your browser. If you delete a necessary cookie, the site may ask for your language and consent again. Blocking all cookies may stop some interface choices from being saved between visits.

Visitor rights and the policy's scope

Contact the publisher

You can request access to information connected with your enquiry or ask for its deletion. Send the request to [email protected] and provide the email address you used to contact the editorial team so the publisher can find the correspondence. If the request concerns only an analytics choice, say so separately.

The editorial team does not create a gaming profile for visitors or see their full history of bets, deposits or withdrawals. Questions about a gaming account go to the operator through its own support route. More about the editorial project and responsible publisher appears on the author and site page .

How this differs from the operator's policy

This page describes processing of visitor data by the editorial site . It covers reading pages, language and analytics choices, technical logs and emails to the editorial team. It does not govern casino registration, player identity checks, payment documents or betting history. Those actions take place in the operator's service and are governed by its own terms.

Before opening the operator's site, remember the 18+ age restriction and applicable responsible gambling rules. General terms for this editorial site and affiliate-link disclosures appear in the terms and disclaimer . Do not send payment or account details to the editorial team to resolve an issue that belongs to the casino.