How This MegaFishWins Guide Handles Reader Data
- Published
- Updated
Effective 13 October 2026.
This policy describes what happens to personal data when a reader uses this independent information guide to MegaFishWins Casino. It is organised by situation, since the data involved depends on what the reader is doing: reading a page, writing to the editors, following a link to the casino, or asking for their data to be removed. The guide is addressed to readers in the European Union and follows the principles of the General Data Protection Regulation (GDPR).
Who is responsible for the data
The editors of this guide decide why and how the personal data described below is handled, which makes them the controller for it. The guide is separate from the casino: the casino has its own relationship with its players, and anything a player gives to the casino when registering, depositing or being verified is handled under the casino’s own terms and not under this policy. The controller can be reached at [email protected].
Situation one: reading a page
Opening a page sends a request from the reader’s browser to the server that delivers the guide. Like any website, the server receives the technical details that make the exchange work, such as the network address of the device, the type of browser, the page asked for and the time of the request. The purpose is to deliver the page and to keep the site working and secure. The legal basis is the legitimate interest of the controller in operating a website.
The guide does not ask readers to register, and reading it does not require giving a name, an address or a payment detail.
Situation two: writing to the editors
A reader who e-mails the editors provides an e-mail address and whatever the message contains. The data is used to read and answer the message, and, where the message reports a mistake in a figure, to correct the page. The legal basis is the legitimate interest in answering correspondence, or the reader’s request where the message asks for something specific.
The message is kept for as long as it is needed to answer it and to document a correction. A reader should leave out account numbers, document images and payment details: nothing in a question about a withdrawal ceiling or a bonus term calls for them.
Situation three: following a link to the casino
Some pages link to MegaFishWins Casino. Following a link leaves this guide. From that point the casino’s own pages, cookies and privacy terms apply to anything the reader does there, including registering, depositing or sending verification documents. The guide has no access to an account at the casino and cannot see what a reader does there.
Situation four: cookies and similar technologies
Cookies are small files that a website can store in a browser. Where this guide uses them, they serve the working of the site. Every browser lets the reader refuse or delete cookies in its settings; refusing them does not stop a page from being read. A reader who arrives from a link on another site is also subject to that site’s cookie rules before reaching this guide.
Situation five: the reader is under 18
The guide is meant for readers aged 18 or over, in line with the casino’s own 18+ rule. It does not seek data from minors. A parent or guardian who believes a minor has written to the editors can ask for the message to be deleted by e-mail.
Requests in practice
| Request | Right used | What the editors do | Timing |
|---|---|---|---|
| Asking what data is held | Access | Send a copy of the e-mail thread and the other data held | Within one month |
| Deleting a message after a figure was corrected | Erasure | Delete the message; the corrected figure stays, because it holds no reader data | Within one month |
| A parent asking to remove a minor’s message | Erasure | Delete the message from the editors’ mailbox | Within one month |
| Objecting to log handling | Objection to legitimate interest | Review the objection and stop the handling unless a compelling reason remains | Within one month |
Rights of the reader
Under the GDPR a reader has the right to ask for access to the personal data held, for correction of inaccurate data, for deletion, for restriction of handling, for the data in a portable form, and to object to handling based on legitimate interest. Where handling rests on consent, consent can be withdrawn at any time, and the withdrawal does not affect what was done before it. These requests are made by e-mail, and the editors answer within the time that the GDPR sets, which is one month in the ordinary case.
A reader who is not satisfied with the answer can complain to the data-protection supervisory authority of their own EU member state, whether that is the country of residence, of work or of the alleged infringement.
Sharing, transfers and security
Personal data is not sold. It is shared only where needed to run the site, for example with the hosting service that delivers the pages, and where the law requires it. Where a service involved is outside the European Economic Area, the transfer is made under the safeguards that the GDPR provides.
Changes to this policy
When the handling of data changes, this page is updated and the effective date at the top is changed. A reader who wants to know what applied on an earlier date can ask for it by e-mail.
What a rights request should contain
A rights request goes to [email protected] and works best when it names the e-mail address used to write, the page concerned, the right asked for and, for a correction, the figure involved. The editors may ask for confirmation of identity before releasing or deleting data, so that nobody receives another person’s messages.