Lincoln

Privacy Policy

This policy covers the pages of our Lincoln Casino game library review. We are an editorial project, not a casino: we hold no player accounts, take no deposits and cannot see anything you do on the operator's own website.

Who publishes this review

The review is written and kept up to date by our games library editor, James Kingsford, with help from a small editorial team. We are independent of the operator and of Liberty Slots Group, and this policy applies to our pages only, not to anything hosted on Lincoln's own domain.

What we collect while you read

Nothing here asks you to sign up, and no form on the site requests your name, address or payment details. When a page loads, the hosting server writes a standard technical log: IP address, browser and device type, the page requested and the time of the request. We use those logs to keep the review online and to track down broken pages, never to build a profile of an individual reader.

Cookies and visit counts

The review is a static site and needs no cookies to display. If we switch on a basic measurement tool, it counts visits in aggregate, for example how many readers opened the pokies section or the banking table, without identifying anyone. Blocking or clearing cookies in your browser will not stop any part of the review from working.

Following a link to Lincoln

Buttons on these pages open the operator's site in a new tab. From that moment the operator's privacy policy governs everything you type there, including registration details, identity documents and payment data. Read it before creating an account, because we have no say in how that information is stored or shared.

Retention and sharing

Server logs are kept only as long as security and troubleshooting require, then deleted. We do not sell, rent or swap visitor data with casinos, advertisers or data brokers, and we would hand it over only where a legal obligation forces us to.

Your requests and future changes

You may ask what technical data relates to your visit and ask for it to be erased; because we hold nothing tied to a name, most requests are simple to settle. If we ever add a tool that handles visitor data, this policy will be rewritten to describe that tool before it goes live.