Server Logs:

A server log entry will be made with any visit to any page located in the ardclan.com domain. This log entry will be created upon any navigation to an ardclan.com domain page or browser refresh.

Any page using the Faron Design HTTP API will also log the same information. If you were sent here from another site’s privacy link then the site uses the FD HTTP API.

The server entry stays resident in the SQL server as a row of data and gets backed up into a CSV (comma seperated value) file after 3 months. The CSV files are then archived and parsed for another 18 months and then deleted. A typical server entry will consist of:

Host Name of the visitor  (IP address of the visitor) - Time and date of the visit (Unix time stamp of the visit) - URI of the visited page – Locale – (GMT-offset)

For example:

ip68-11-248-24.br.br.cox.net (68.11.248.24 ) – 4/10/2011 21:17:37(1302405457) - /blog/?cat=5 - America/Chicago – (GMT-21600)

The server log’s main purpose is to track the number of times search engine crawlers that visit the a site. This is easily done when the data is housed in the SQL server.

Cookies

Ardclan.com (and those domains served by the Faron Design HTTP API) will place cookies into your browser to help with security and to track unique visitors. However, each site will function with less features should cookies be disabled.

Examples may include:

unique – the code simply places a value of 1 into the browser if the unique cookie has no value

blog_key – a 128 bit hexadecimal number (used to verify if visitors have rights to view private data).

data_key – a 128 bit hexadecimal number (used to verify if visitors have rights to view private data). Will look something like (which happens to be the sha256 hash of the word cookie):

If you are using services which require a login; there will be other cookies used to identify your visit and purpose which may include:

A key or a user_key cookie may be saved to your browser to identify you to the login logic. This variable is usually an sha256 (256 bit) hash of your username or email address. This hexadecimal value is used to cross reference other user data stored in the SQL server (so this is the only data exchanged over unsecured HTTP, which is a good thing). Example:

person@example.com

542d240129883c019e106e3b1b2d3f3cb3537c43c425364de8e951d5a3083345