Privacy Policy for Readers of This Service

4 Fields the Server Logs Record

The server logs record 4 fields and nothing more: IP address, requested URL, user agent and timestamp. They exist for security and error diagnosis. No name, email address or payment detail is among them; the IP address is, and that is the one identifying value a log of this kind keeps.

Nothing is sold. Server logs here stay unsold and unmerged with anything else. They feed no profile, they stay inside this one site, and the pages ship without an analytics script, so a tracking pixel is simply absent.

In Short, What We Hold About You

Here's the honest summary: it's a web server log and that's all. There's no account, no newsletter and no advertising identifier, so there's very little to hand over even when you ask.

You'll still get a straight answer to a data request. If the log has already been discarded, the reply says exactly that, because an empty answer beats an invented one.

Accounts

None

Cookies this site sets

0

Analytics scripts

None

Server log fields

4 (IP, URL, user agent, time)

Images site-wide

All original, served from this domain

Policy dates

2 Nov 2026 / 2 Nov 2026

What Should You Do Before You Start Reading?

Three steps are worth taking before you start, and all of them are available inside your own browser. Browse the range of privacy settings your browser offers, then read the policy of any site you are sent on to.

1. Check the privacy settings your browser already applies to this site.
2. Read the policy of any site a redirect hands you across to.
3. Note the date of your visit if you plan to ask what the server kept.

How long an access log survives is the host's setting rather than ours, and all 9 pages here are dated. Doing this in advance matters, because a request arriving days later can only be answered honestly.

What Those Logs Leave Out

Every identifying detail is missing from those server logs: name, email address, payment record and gambling history are absent, because none of that is ever gathered here. That is a real limitation of what a data request here can return.

An operator account is a separate world with separate records. We can see a click leaving Fruit King and nothing after it.

Cookies, Local Storage and Logs

Cookies here number zero right now, and none are set by this site at all. Cookies stay absent from this policy for a simple reason: the site sets none, so the server log and the click record described below are the only records here. The 2 scripts each page loads rewrite the affiliate button address and add small conveniences such as copy link and back to top.

Neither script sends data anywhere, and the pages ship free of advertising tags. Our methodology for this site keeps the front end static, so a page offers nothing for a tracker to attach to.

Anything else a reader sees is ordinary browser behaviour. Anything a browser keeps on its own, such as a collapsed menu state, stays on the device, and the browser settings clear it at any time.

Affiliate Redirects Beside the Logs

Beside the logs sits one outbound hop. Affiliate redirects are the only outside traffic in play, and this site runs its first hop itself. The play button points to a redirect address on this site, which writes one line to its own click record: the path of the page the click came from, the page language, a click type and the time, with no IP address and no browser details. The affiliate redirect then sends the reader on, without passing the page address, to the affiliate network's own tracker, whose policy applies from that moment, and the terms of use explain that arrangement in full.

Once a reader lands on another site, that site's own policy takes over. No casino is named on any page here, so the one affiliate link a reader meets is the play button; the rest lead to the studio's own pages and to the support services in the footer.

Which Types of Data a Redirect Passes?

The redirect provides a click record and nothing more. It includes no name, no email address and no payment detail, because this service collects none of them from you.

An operator supplies its own tracking once you arrive, and they answer for it under their own regulator. Compared to this site, which collects nothing, the notice at the far end of a redirect is the one worth reading. Their privacy policy governs everything after that moment, so you should read it before you register.

The weakness of this arrangement is visibility: we cannot see what an operator stores about you, and that limitation is stated instead of glossed over.

Third-Party Software and Embedded Content

No analytics or advertising software loads. Embedded content of that kind is absent from every page here. Widgets of that kind appear nowhere on Fruit King. Pages carry no video players, social widgets or advertising scripts. No game client is embedded either: the studio offers no stable public demo address a page could carry, so playing the game always means leaving this site by your own choice.

According to the file record, every screenshot here is an original captured in the recorded demo session of the studio's own client, and served from this domain. The testing method page explains where those frames come from.

How Long the Logs Are Kept

Nobody here can state that window yet. Retention will belong to the host, not to us. Whatever window that host keeps, it will exist for security and error diagnosis instead of for analytics, and nothing gets copied out of it. Every log stays inside that single system, for every page this site serves.

The length of that window is the one thing this page cannot state: the host is not chosen yet, and inventing a number of days would be worse than naming the gap. It gets printed here the day the host is settled. So write early if you intend to ask about a specific visit, because the log may be gone before the question arrives.

Reader Rights over Those Logs

Reader rights over the current logs follow data-protection law. Where the General Data Protection Regulation, Regulation (EU) 2016/679, applies, it is the rule we follow. A reader may ask what data, if any, the server holds about their visits, and may request its deletion. A reader who is not satisfied with the answer may also complain to the data-protection authority of their own country.

Write to the editor through the contact page, name the approximate date and time of your visit, and the request is checked against whatever logs survive. To verify the answer, the editor reads the server log directly. However, a log already discarded cannot be produced, and the reply says exactly that.

What Is Left Behind by a Deposit?

The complete list of what a deposit leaves here is empty. A deposit, a withdrawal or a bonus claim happens entirely inside an operator account, so none of it reaches this service. The about page sets out who is responsible for Fruit King.

The responsible gambling page explains that this site holds no gambling account data whatsoever, which is also why this desk cannot help with an operator balance.

Terms This Policy Uses

Access log

The line a web server writes for each request, holding an IP address, a URL, a user agent and a timestamp.

Affiliate redirect

A short link that records a click for commission accounting before sending the reader on.

Local storage

A small store inside the browser itself, cleared from the browser settings and never read by this site.

Data request

A message asking what the server holds about a visit, answered against whichever logs still exist.

Does This Site Set Any Cookie?

This site sets no cookie of its own, and the pages load no analytics script, so a reader has nothing here to opt out of and nothing to clear afterwards.

Another site is a different matter once you leave. Its cookies, its tags and its retention rules take over the instant you land there.

Recap: This Policy Compared with an Operator

If you want a one-line answer, the policy of the site you land on next is the one to read. This one is short: the server logs 4 fields, the site sets 0 cookies, embedded content is absent, affiliate redirects record a click, retention belongs to the host, and a reader may ask what survives. That short list is the whole of the record.

This policy was first published on 2 Nov 2026 and changes only when the technical setup behind Fruit King changes; the current wording dates from 2 Nov 2026. Because no accounts exist here, a change reaches readers through this page instead of by email.