Cookie Policy
At DomainCrawler, we use cookies on our website(s). This cookie policy explains what and how cookies are used. For more information on how we process personal data and your rights as a data subject, please see our Privacy Policy.
When you visit our website, you will be given the choice via a cookie banner to consent to our use of cookies based upon the contents of this policy.
What is a Cookie file?
A cookie is a small piece of data, which may include a unique identifier that is stored on your computer or mobile device when you visit a website. Cookies can generally be categorised based on their lifespan and whether the cookie is set by the domain you are visiting or by another domain.
First party cookies are set directly by and can only be read by the website you are visiting. Third party cookies are set by a domain other than the one you are visiting, which typically occurs when the website uses external services. Persistent cookies are not automatically deleted at the end of your browser session. Cookies that are deleted once you quit your browser session are known as session cookies.
What types of cookies do we use?
There are a number of different types of cookies, however, our website uses. We categorise cookies in four categories:
- Visitor preference cookies (store visitor preferences)
- Operational cookies (make our website operational)
- Analytical cookies (gather analytics data about visitors)
- Advertising (you may be shown advertising based on your browsing patterns on our website)
Certain cookies may be accessed by third parties as disclosed below.
How do we use cookies?
DomainCrawler uses cookies in a range of ways to improve your experience on our website, including:
- Keeping you signed in
- Understanding how you use our website
- Direct marketing
- Advertisement on your browser
1. Visitor preference cookies
Name of cookie | Purpose | Duration | Cookie type | Access by third party |
Cookie_notice_accepted | Content: true or false. Used to store your cookie preference in order not to ask you again | 1 month | First party persistent cookie | No |
2. Operational cookies
Name of cookie | Purpose | Duration | Cookie type | Access by third party |
_gat_UA-85713726-4 | Used to throttle request rate* | 1 day | First party persistent cookie
| |
_gat_waas | Used to throttle request rate* | 1 minute | First party persistent cookie
| |
intercom-id-*: | Used by intercom for communications (chat) with our customer. | 9 months | Third party persistent cookie
| Intercom |
PHPSESSID | Cookie generated by applications based on the PHP language. This is a general-purpose identifier used to maintain user session variables. It is normally a random generated number, how it is used can be specific to the site, but a good example is maintaining a logged-in status for a user between pages. | 1 month | First party persistent cookie
| N/A |
REMEMBERME | Checkbox functionality | 1 month | First party persistent cookie
| N/A |
*Used to determine and control technical access to the website.
3. Analytical cookies
Name of cookie | Purpose | Duration | Cookie type | Access by third party |
_ga | Used to identify unique users* This cookie name is associated with Google Universal Analytics – which is a significant update to Google’s more commonly used analytics service. This cookie is used to distinguish unique users by assigning a randomly generated number as a client identifier. It is included in each page request in a site and used to calculate visitor, session and campaign data for the sites analytics reports. | 2 years | First party persistent cookie | |
_gid | Used to track user behavior* This cookie name is associated with Google Universal Analytics. This appears to be a new cookie and as of Spring 2017 no information is available from Google. It appears to store and update a unique value for each page visited. | 2 days | First party persistent cookie | |
wordpress_test_cookie | WordPress also sets a cookie named wordpress_test_cookie to check if the cookies are enabled on the browser to provide appropriate user experience to the users. This cookie is used on the front-end, even if you are not logged in. | Session | First party session cookie | N/A |
_hjid | Hotjar cookie. This cookie is set when the customer first lands on a page with the Hotjar script. It is used to persist the random user ID, unique to that site on the browser. This ensures that behavior in subsequent visits to the same site will be attributed to the same user ID. | 1 year | Third party persistent cookie | Hotjar |
_hjIncludedInSample | This cookie is associated with web analytics functionality and services from Hot Jar, a Malta based company. It uniquely identifies a visitor during a single browser session and indicates they are included in an audience sample. | Session | Third party persistent cookie | Hotjar |
_hjSessionInProgress | Hotjar cookie. Used to keeping track of a session. Detailed information about Hotjar cookies here: | Session | Third party persistent cookie | Hotjar |
_ym_* | Cookie set by Yandex Metrica for website statistics. Detailed information about Yandex Metrica cookies here: | 1 year | Third party persistent cookie | Yandex Metrica |
_hj* | Cookie set by Hotjar to run track usage. Detailed information about Hotjar cookies here: | Decided by Hotjar | Third party non-essential cookie | Hotjar |
intercom-session-* | Used to keeping track of a session. An identifier for each unique browser session. This cookie is refreshed on each successful logged-in ping, extending it to 1 week from that moment. The user can access their conversations and have data communicated on logged out pages for 1 week, as long as the session isn’t intentionally terminated with ‘Intercom (‘shutdown’)’; , which usually happens on logout. Detailed information about Intercom cookies here: | 1 week | First party persistent cookie | Intercom |
*Used to gather statistical data, such as how long time you spend on the website, how frequently you visit the website, and the pages you visit.
4. Advertising
| Name of cookie | Purpose | Duration | Cookie type | Access by third party |
| _fbp: | Used by Facebook to deliver a series of advertisement products such as real time bidding from third party advertisers. | 3 months | Third party persistent cookie | |
| __adroll_fpc: | Used to identify the visitor across visits and devices. It is used by real-time bidding for advertisers to present relevant advertisements. | 1 year | Third party persistent cookie | Adroll |
| __ar_v4: | This cookie is associated with the DoubleClick advertising service from Google. Helps with tracking conversion rates for ads. | 1 year | Third party persistent cookie |
How to manage cookies
Most web browsers accept the use of cookies as a default setting. However, most web browsers can be customised to manage the use of cookies for a specific website or all websites.
Removing cookies from your device
You may choose to delete cookies already stored on your device. Instructions for making these settings are usually found in your browser’s documentation. Please note that when deleting cookies, you may lose certain saved information and settings, such as site preferences and login details.
One way to withdraw your consent is to delete cookies as described above and the next time you return to our website you can choose not to consent to the use of cookies.
Blocking cookies
Most web browsers accept the use of cookies as a default setting. In most web browsers, you have the ability to disable the use of cookies for a specific or all websites. To do that you usually have to click the Settings button in your browser and then proceed to the Privacy & Security section. Details on how to manage your web browser settings are normally available in the user’s guide which can be found on the support web page of your browser.
Changes to our privacy policy
DomainCrawler keeps its privacy policy under regular review and places any updates on this web page. Please check this policy on a regular basis to ensure that you are aware of the latest version.
This privacy policy was last updated on 30 October 2020.
How to contact us
If you have any questions about DomainCrawler privacy policy, the data we hold on you, or you would like to exercise one of your data protection rights, please do not hesitate to contact us:
DomainCrawler
Roslagsgatan 26A, 11355, Stockholm, Sweden
info@domaincrawler.com
