The data a visit leaves, and where it goes

Hosting and delivery providers

A request to Tryline travels through outside companies that provide hosting and delivery for the site. Hosting keeps the pages available; delivery carries them across the network to the reader's browser. Those providers process the requests on our behalf as part of that work, and we do not name them. Because they act on our behalf, their handling is part of how the site is served. The practical point is that serving a page is not handled by us alone. Outside companies stand in the technical path and handle the traffic for us. Their part is the machinery that keeps the site reachable and moves its pages to you. A reader does not see this chain from the page itself, but it forms part of the route taken by each request.

Cookies we do not set

We do not set analytics cookies, and we do not set advertising cookies. A cookie is a small item of browser storage that a site can read later. An analytics cookie can be used to measure visits, while an advertising cookie is used in connection with advertising. Neither kind is placed in your browser by us. Opening a page here therefore does not cause Tryline to store a cookie for visit measurement or advertising. The boundary concerns cookies we set ourselves.

Record of each request

For every request, the server writes a technical entry. It contains your IP address, the internet address used by your connection; the time of the request; the browser string, the line with which your browser identifies itself; the address you requested; and the address of the page that sent you. Together, these details show what was asked for, when it was asked for, which browser announced itself, which internet address made the request and which page led to it. If the address you open includes campaign tags, the labels used to mark a campaign, those tags are stored with the same request. The saved form of the address therefore keeps those labels alongside the technical details. Where the delivery provider reports an approximate country worked out from the IP address, that country is recorded too. The country is approximate and depends on the provider reporting it. Each server entry is kept for 30 days. Opening a page therefore leaves a technical trace tied to the connection for that period, with the requested address, the address that led there and any campaign labels sitting beside the connection and browser details.

Partner-link clicks

Certain pages include partner links to casinos, and following such a link can result in a reward for us. When a visitor follows such a link, we record the page where the click occurred, the browser string, the IP address and the country. The browser string identifies the browser; the IP address is the internet address used by the connection. After 90 days, those details are erased. The record that the click happened remains without them. A partner link can also send information about the click onward. It may pass the address of that page, the address of the site the reader came from, the reader's country and our domain name, meaning the main address of our website, to the partner, to the casino or to its affiliate programme. An affiliate programme is the outside arrangement through which a casino handles partner referrals. The click information can therefore reach an organisation beyond the casino itself. Such a transfer is possible through the link itself, not through a separate action by the reader. A casino reached this way is an external website with its own rules and policies. After you follow the link, that casino's rules and policies apply to what happens there.

Combined visit statistics

• Combined visit totals are kept longer than the server record for an individual request.
• IP addresses do not appear in those totals.
• They count how many visits take place.
• Visit sources are grouped.
• Countries appear when the delivery provider reports them.
• Browsers are recorded.
• Popular pages are shown.