Visit records and sharing

Combined visit totals

• Combined visit totals contain no IP address.
• They are kept longer than the individual server records.
• They group many visits instead of keeping one request entry at a time.
• The totals include browser details across those grouped visits.
• They include the number of visits and the sources of visits.
• They also include the pages that readers used most during those visits.
• Countries enter only when the delivery provider reports them for a visit.
• For a reader, the longer-kept view stays combined rather than individual.

Infrastructure providers carrying requests

A request reaches Fruit Slots through outside companies. Those companies provide the hosting and the delivery. They process the request on our behalf. Hosting is the side that stores the site. Delivery is the side that sends the page out. We do not name those providers. A reader should expect carrying companies to act for us. A request is not handled only at the end point. It is carried and processed by those outside companies first. The path matters because handling happens before the page reaches the reader. It also matters because the companies stay unnamed. The reader still deals with one website, Fruit Slots. The carrying work sits outside that single name.

Individual request records

• Every request to Fruit Slots creates a server record on our side.
• The record holds the browser string and the requested address.
• It also holds the IP address and the referring page address.
• It holds the time of the request as well.
• The requested address shows which page was asked for by the reader.
• The referring page address shows where the reader arrived from before the request.
• Each one of these records is kept for 30 days.
• When the delivery provider reports it, an approximate country is added from the IP address.

Campaign tags in the page address

A page address can carry campaign tags. Those tags are part of the address that is requested. They are stored with the request itself. The stored tag stays attached to that same request. It does not stand apart from the request in storage. The tag tells us which campaign label arrived in the address. That label is kept with the request that carried it. A reader may see such a tag in the page address. Its storage follows the request that brought it here.

Affiliate clicks and partner links

• Some pages link to casinos as partners.
• Following such a link may earn Fruit Slots a reward.
• A click on an affiliate link is recorded as a click in its own right.
• The click record holds the browser string for that click.
• It holds the country, the IP address and the page for that click.
• Those details belong to the affiliate click rather than to a normal read.
• The IP address and browser string are erased after 90 days.
• The click record stays after those two details are gone.

Click data sent to a partner

An affiliate link can pass click data to the partner on the other end. That partner may be a casino or its affiliate programme. The data can include the address of the page the reader was on. It can include the country of the reader. It can include the address of the website the reader came from. It can include the Fruit Slots domain. That is data leaving Fruit Slots with the click. The sharing is tied to following the affiliate link. The page address places the click on a specific page. The reader country is passed as the country recorded for the click. The referring website address points back to the earlier page. The Fruit Slots domain identifies this website in that pass. A reader should treat the partner link as a data handoff.

No analytics or advertising cookies

Fruit Slots itself sets no analytics cookie. It sets no advertising cookie. So cookie-based tracking is not part of a visit here.