Cookie Policy

8th August 2019

The website www.webdesh.com collects and stores “cookies”“Cookies” are small text files, which are stored on the user’s device for a specific amount of time upon visitation of the website. On their own, they do not require any personal information in order to be used and do not identify the person using the Internet. “Cookies” collect information about the way the user interacts with the website in order to improve its efficiency and allow other functionalities without identifying a certain user.

In the following policy we state and explain our principles for collecting, storing and processing “cookies”. Those rules explain how we from Webdesh EOOD and the users of our website actually use “cookies” and the different ways to control them.

“Cookies” are small portions of data, stored in text files on your computer or another device, which you are loading the website on. They are widely used and their aim is to “remember” you and your preferences – for one visitation (via Session Cookies) or multiple visitations (via Persistent Cookies). They provide a successive and effective journey for the user by performing main functions such as allowing the user to register and stay in their profile. Our company uses “cookies” from Google Analytics and WordPress for acquiring information about how and when specific pages of our website are visited, as well as how many people have visited them.

You can set your browser to decline, remove or block “cookies” or to tell you when a new “cookie” is generated, without affecting most of the website’s functionalities. For more information on “cookies”, please visit: www.allaboutcookies.org.

Strictly Necessary Technical “Cookies”

Those “cookies” are necessary in order for our site to function and they cannot be turned off. Usually they are generated upon the actions you have taken, which could be a service request, setting your privacy preferences, logging into the system or filling out forms. You can set your browser to block those “cookies” or warn you about them, but in this case some parts of our page will not work for you. Those “cookies” do not collect any personal information.

Some “cookies” are only for registered users, while others are for all users and they are listed in the table below. When a “cookie” only concerns a certain subdomain, they are situated in the corresponding header.

Functionality “Cookies”

Those “cookies” are used to store preferences stated by the user, such as name, language and location.

Performance “Cookies”

They are used by a trusted third-party network (i.e. Google Analytics) to track details such as how many unique visitors have visited the site and how many times each page was shown. This information is collected in order to improve the practice and experience for the visitors as well as for our website.

“Cookies” for Improving Effectiveness

“Cookies” for improving effectiveness collect information about the way users interact with our website. This information is collected solely for improving the functionality of our website.

Social Media “Cookies”

They collect information about the usage of Social medias. “Cookies”, used by Facebook and Instagram (by using the sharing buttons) – datr (536 days), fr (89 days), lu (536 days). We don’t have direct control over the information collected by those “cookies”.

“Cookies” used:

CookieDurationPurpose
devicePixelRatioBrowser default (1 year)Used to make the site responsive to the visitor’s screen size.
wordpress_test_cookieSessionTests that the browser accepts cookies.
__qca5 yearshttps://www.quantcast.com/privacy/
__utma2 yearsGoogle Analytics – Used to distinguish users and sessions. The cookie is created when the javascript library executes and no existing __utma cookies exists. The cookie is updated every time data is sent to Google Analytics.
__utmb30 minsGoogle Analytics – Used to determine new sessions/visits. The cookie is created when the javascript library executes and no existing __utmb cookies exists. The cookie is updated every time data is sent to Google Analytics.
__utmcSessionGoogle Analytics – Set for interoperability with urchin.js. Historically, this cookie operated in conjunction with the __utmb cookie to determine whether the user was in a new session/visit.
__utmt10 minsGoogle Analytics – Used to throttle request rate.
__utmz6 months
Google Analytics – Stores the traffic source or campaign that explains how the user reached your site. The cookie is created when the javascript library executes and is updated every time data is sent to Google Analytics.
welcome-{blog_id}PermanentUsed to record if you’ve chosen to hide the “Welcome” message at the top of the corresponding blog.
showComments10 years
Used to determine if you prefer comments to be shown or hidden when reading the site.
camptix_client_stats1 yearUsed to track unique visitors to tickets page on a WordCamp site
wp-saving-post1 day
Used to track if there is saved post exists for a post currently being edited. If exists then let user restore the data
comment_author_{hash}347 days
Used to tracked comment author name, if “Save my name, email, and website in this browser for the next time I comment.” is checked
wp-postpass_{hash}10 days
Used to maintain session if a post is password protected
tix_view_token2 days
Used for session managing private CampTix content
tk_aiBy browser defaultIt is used for tracking.
jetpackStateSessionIt is used for maintaining the Jetpack State.
stnojs2 daysIt remembers if the user does not want any javascript to be executed.
wordpress_logged_in_{hash}SessionIt remembers user sessions.
cookie_notice_accepted1 monthIt is used by the Cookie Notice plugin, which function is to “elegantly inform users that the site uses cookies and to comply with the EU cookie law GDPR regulations.” (taken from the policy of the plugin itself).

For more information: https://wordpress.org/about/privacy/cookies/

Users have the right to limit the usage of “cookies” or to completely deactivate them. Most browsers suggest different ways to control the behavior of the “cookies” – for example the duration of their storage – by using a in-built functionality or by using plugins and apps from third-parties. 

To learn more about controlling and deleting “cookies”, you can visit aboutcookies.org. For more information about Advertising Cookies and how to control them, you can visit youronlinechoices.eu (based in the EU) or aboutads.info (based in the US).

Some special apps for declining the usage of “cookies” you can check here:

Quantcast – https://www.quantcast.com/opt-out/

Google Analytics – https://tools.google.com/dlpage/gaoptout

It is important to know  that limiting or deactivating the usage and storage of “cookies” can limit the functionality of a website or interfere with their work overall.

Google Analytics is a tool, which helps us to determine the way users interact with the content on our website. When a user is surfing a web page, Google Analytics provides the owner of said web page with javascript tags (libraries), which store data about the web page the user visited, for example its URL address.

The javascript libraries of Google Analytics use HTTP “cookies” to remember the way the user interacted with previous pages. Google Analytics supports three javascript libraries to determine the website usage: gtag.js, analytics.js and ga.js. The next sections describe the way each of those libraries uses “cookies”.

gtag.js and analytics.js

CookieDurationDescription
_ga2 yearsIt is used to distinguish the users.
_gid24 hoursIt is used to distinguish the users.
_gat1 minUsed to throttle request rate. If Google Analytics is deployed via Google Tag Manager, this cookie will be named _dc_gtm_.
AMP_TOKEN30 secs to 1 year
Contains a token that can be used to retrieve a Client ID from AMP Client ID service. Other possible values indicate opt-out, inflight request or an error retrieving a Client ID from AMP Client ID service.
_gac_90 days
Contains campaign related information for the user. If you have linked your Google Analytics and Google Ads accounts, Google Ads website conversion tags will read this cookie unless you opt-out. Learn more.

ga.js

CookieDurationDescription
__utma2 years from set/updateUsed to distinguish users and sessions. The cookie is created when the javascript library executes and no existing __utma cookies exists. The cookie is updated every time data is sent to Google Analytics.
__utmb30 mins from set/update
Used to determine new sessions/visits. The cookie is created when the javascript library executes and no existing __utmb cookies exists. The cookie is updated every time data is sent to Google Analytics.
__utmcEnd of browser session
Not used in ga.js. Set for interoperability with urchin.js. Historically, this cookie operated in conjunction with the __utmb cookie to determine whether the user was in a new session/visit.
__utmt10 mins
Used to throttle request rate.
__utmz6 months from set/updateStores the traffic source or campaign that explains how the user reached your site. The cookie is created when the javascript library executes and is updated every time data is sent to Google Analytics.
__utmv2 years from set/updateUsed to store visitor-level custom variable data. This cookie is created when a developer uses the _setCustomVar method with a visitor level custom variable. This cookie was also used for the deprecated _setVar method. The cookie is updated every time data is sent to Google Analytics.

urchin.js

Google Analytics provides javascript with a library for measuring, called urchin.js. When a newer library ga.js is released, developers are encouraged to transfer to the newer library. For a website which have not completed the transfer to the newer library, urchin.js determines the “cookies” identically with what is preset in ga.js. For more information, read the section about usage of ga.js cookies above.

For more information about Google Analytics Cookies: https://developers.google.com/analytics/devguides/collection/analyticsjs/cookie-usage

If you have any questions regarding our Cookie Policy, feel free to contact us at [email protected]