What happens to the data

Questions and corrections

A mistake about Megaways can be sent to the editorial team through the contacts page, and a question about the website can be sent the same way. The route does not depend on the size of the issue: a wrong detail, an unclear point and a request to understand how something works all travel through that page. What matters is the destination and the channel. The destination is the editorial team; the channel is the contacts page. A reader who has spotted an error and a reader who simply wants an explanation are therefore using one door rather than two separate ones.

Providers that carry requests

Each request to Megaways passes through infrastructure providers, hosting and delivery, and those providers process the request on our behalf. Before a page is assembled for the reader, the request has already moved across providers that keep the site hosted and deliver its material. Their role is operational. Hosting makes the site reachable; delivery carries the response back toward the reader. In that chain, the providers are handlers for Megaways, not the source of the editorial content. They are not named, so no specific hosting company or delivery company is identified.

Server records and page tags

The server keeps a technical record of each request. That record contains the browser details, the address of the referring page, the IP address, the requested address and the time of the request. Read together, those items describe the arrival of the request: what software asked, where the reader was referred from when that address is available, which address was requested, and when. The retention period is 30 days; once that period has passed, the individual server record is no longer kept. If the delivery provider reports an approximate country derived from the IP address, the record gains that country as well. Campaign tags behave differently from the technical list. A tag in the page address is stored together with the request, so a visit reached through a tagged campaign address keeps the tag beside the request that carried it.

Affiliate clicks and partner links

An affiliate link is treated as a click that can be measured and can also be shared. When a visitor follows such a link, data about the click is recorded: the IP address, the browser details, the page and the country. The first consequence is retention inside that click record. After 90 days, the IP address and the browser details are erased; the record of the click stays without them. The click remains, but two technical details are removed from it. The second consequence concerns movement. Some pages link to casinos as partners, and following such a link may earn Megaways a reward. That reward possibility is why the link is affiliate in character. An affiliate link may also pass data about the click to the partner, a casino or its affiliate programme. The items passed on are specific: the domain of Megaways, the address of the page, the country of the reader and the address of the website the reader came from. Plainly, the click can reach beyond the record made here. It can leave a reduced record after 90 days and still have transmitted click data to the partner side at the moment of the follow.

Longer-kept visit statistics

• They are aggregated visit statistics, which means they describe traffic across visits rather than one server record for one request.
• They contain no IP addresses.
• They are kept longer than the individual server records.
• They show which pages are popular, so the lasting view includes page-level demand.
• They show the number of visits.
• They show sources of visits, meaning the places visits come from.
• They show countries when the delivery provider reports them.
• They show browsers.

No analytics or advertising cookies

Megaways itself does not set analytics or advertising cookies.