Apify Cookie Policy
Apify Technologies s.r.o., with its registered seat at Vodičkova 704/36, 110 00 Prague 1, Czech Republic, Company reg. no. 04788290, recorded in the Commercial Register kept by the Municipal Court of Prague, File No.: C 253224 ("we", "us" or the "Provider") welcomes you (“you” or the “User”) on our website apify.com (the “Website”).
This Cookie Policy (the “Policy” or “Cookie Policy”) describes the way we use cookies on our Website and on our platform on console.apify.com (the “Platform”). Terms starting with a capital letter used in this Policy have the meaning defined in our General Terms and Conditions (the “Terms”). By accessing the Website, Platform or using our Services, you acknowledge and agree to this Policy. If you do not agree to the terms of this Policy, please do not use the Website, Platform or any of our Services. Each time you use the Website, Platform or our Services, the current version of the Cookie Policy will apply.
Cookies
When you access our Website, Platform or use our Services, we may collect information regarding your IP address for the purposes of administering the Website or Platform and tracking Website or Platform usage. However, your IP address may vary each time you visit, or it may remain the same depending on the type of Internet connection you are using or the location from which you access the Website or Platform.
We may also collect information about the websites that directed you to our Website or Platform after you clicked on a text or banner link or an ad from another website, or the day and time you visited our Website or Platform and how long you spent on the Website or Platform. We aggregate such information to help us to compile reports as to trends and other behavior about users visiting our Website. However, such information is anonymous and cannot be tied directly to you.
We may also use “cookies” and your personal information to enhance your experience on the Website, Platform and with the Services and to provide you with personalized offers. A cookie is a small data file placed on your computer's hard drive that contains information that allows us to track your activity on the Website or Platform. The cookie itself does not contain any personal information; however, if you provide us with any personal information, the cookie may act as an identifier to tie your personal information to your IP address or computer. You may choose to delete cookies from your computer's hard drive at any time or to disable cookies on your computer. If you delete cookies that relate to the Website, we may not be able to identify you upon your return to the Website. Additionally, if you disable your computer's cookies, you may not be able to access certain features of the Website, Platform or Services that require that cookies be enabled.
The Website's or Platform's cookies cannot be used to read data from your hard drive and cannot retrieve information from any other cookies created by other websites. Additionally, our cookies cannot be used as a virus, Trojan horse, worm, or any other malicious tool that could impair your use of your computer. Our cookies are used to help us better understand how you and other users use the Website or Platform, so we can continue to provide a better, more personalized user experience on the Website. We also share website usage information about our Website or Platform with those interested in running targeted promotional campaigns on the Website. For this purpose, we and our advertisers track some of the pages that you visit on the Website through the use of pixel tags (also called clear gifs).
What types of cookies do we use?
Strictly Necessary Cookies
These cookies are necessary for the website to function and cannot be switched off in our systems. They are usually only set in response to actions made by you which amount to a request for services, such as setting your privacy preferences, logging in or filling in forms. You can set your browser to block or alert you about these cookies, but some parts of the site will not then work. These cookies do not store any personally identifiable information.
Performance Cookies
These cookies allow us to count visits and traffic sources, so we can measure and improve the performance of our site. They help us to know which pages are the most and least popular and see how visitors move around the site. All information these cookies collect is aggregated and therefore anonymous. If you do not allow these cookies, we will not know when you have visited our site, and will not be able to monitor its performance.
Functional Cookies
These cookies enable the website to provide enhanced functionality and personalisation. They may be set by us or by third party providers whose services we have added to our pages. If you do not allow these cookies then some or all of these services may not function properly.
Targeting Cookies
These cookies may be set through our site by our advertising partners. They may be used by those companies to build a profile of your interests and show you relevant adverts on other sites. They do not store directly personal information, but are based on uniquely identifying your browser and internet device. If you do not allow these cookies, you will experience less targeted advertising.
How long do cookies last?
None of our cookies last forever. You can always choose to delete cookies from your computer at any time. Even if you do not delete them yourself, our cookies are set to expire automatically after some time. Some cookies will be deleted as soon as you close your browser (so-called “session cookies”), some cookies will stay on your device until you delete them or they expire (so called “persistent cookies”). You can see from the table below the lifespan of each type of cookie that we use; session cookies are those marked with 0 days' expiration, all other cookies are persistent, and you can see the number of days they last before they automatically expire. The expiration periods work on a rolling basis, i.e., each time you visit our website again, the period restarts.
| Cookie name | Cookie description | Type | Expiration (in days) |
|---|---|---|---|
| AWSALB | AWS ELB application load balancer | Strictly necessary | 6 |
| OptanonConsent | This cookie is set by the cookie compliance solution from OneTrust. It stores information about the categories of cookies the site uses and whether visitors have given or withdrawn consent for the use of each category. This enables site owners to prevent cookies in each category from being set in the user's browser, when consent is not given. The cookie has a normal lifespan of one year, so that returning visitors to the site will have their preferences remembered. It contains no information that can identify the site visitor. | Strictly necessary | 364 |
| AWSALBCORS | This cookie is managed by AWS and is used for load balancing. | Strictly necessary | 6 |
| ApifyProdUserId | This cookie is created by Apify after a user signs into their account and is used across Apify domains to identify if the user is signed in. | Strictly necessary | 0 |
| ApifyProdUser | This cookie is created by Apify after a user signs into their account and is used across Apify domains to identify if the user is signed in. | Strictly necessary | 0 |
| intercom-id-kod1r788 | This cookie is used by Intercom service to identify user sessions for customer support chat. | Strictly necessary | 270 |
| intercom-session-kod1r788 | This cookie is used by Intercom service to identify user sessions for customer support chat. | Strictly necessary | 6 |
| _gaexp_rc | _ga | Performance | 0 |
| _hjTLDTest | When the Hotjar script executes we try to determine the most generic cookie path we should use, instead of the page hostname. This is done so that cookies can be shared across subdomains (where applicable). To determine this, we try to store the _hjTLDTest cookie for different URL substring alternatives until it fails. After this check, the cookie is removed. | Performance | 0 |
| _hjSessionUser_1441872 | Hotjar cookie that is set when a user first lands on a page with the Hotjar script. It is used to persist the Hotjar 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. | Performance | 364 |
| _hjIncludedInPageviewSample | This cookie is set to let Hotjar know whether that visitor is included in the data sampling defined by your site's pageview limit. | Performance | 0 |
| _ga | 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. By default it is set to expire after 2 years, although this is customisable by website owners. _ga | Performance | 729 |
| _ga_F50Z86TBGX | _ga | Performance | 729 |
| _hjIncludedInSessionSample | This cookie is set to let Hotjar know whether that visitor is included in the data sampling defined by your site's daily session limit. | Performance | 0 |
| _hjFirstSeen | Identifies a new user's first session on a website, indicating whether or not Hotjar's seeing this user for the first time. | Performance | 0 |
| _gclxxxx | Google conversion tracking cookie | Performance | 89 |
| _hjAbsoluteSessionInProgress | This cookie is used by HotJar to detect the first pageview session of a user. This is a True/False flag set by the cookie. | Performance | 0 |
| __hssc | This cookie name is associated with websites built on the HubSpot platform. It is reported by them as being used for website analytics. | Performance | 0 |
| _gaexp | Used to determine a user's inclusion in an experiment and the expiry of experiments a user has been included in._ga | Performance | 43 |
| _hjIncludedInPageviewSample | This cookie is set to let Hotjar know whether that visitor is included in the data sampling defined by your site's pageview limit. | Performance | 0 |
| _gat_UA-nnnnnnn-nn | This is a pattern type cookie set by Google Analytics, where the pattern element on the name contains the unique identity number of the account or website it relates to. It appears to be a variation of the _gat cookie which is used to limit the amount of data recorded by Google on high traffic volume websites. | Performance | 0 |
| __hstc | This cookie name is associated with websites built on the HubSpot platform. It is reported by them as being used for website analytics. | Performance | 389 |
| _hjIncludedInSessionSample | This cookie is set to let Hotjar know whether that visitor is included in the data sampling defined by your site's daily session limit. | Performance | 0 |
| _hjSession_1441872 | A cookie that holds the current session data. This ensures that subsequent requests within the session window will be attributed to the same Hotjar session. | Performance | 0 |
| _gid | 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._gid | Performance | 0 |
| _gat | This cookie name is associated with Google Universal Analytics, according to documentation it is used to throttle the request rate - limiting the collection of data on high traffic sites. It expires after 10 minutes._ga | Performance | 0 |
| __hssrc | This cookie name is associated with websites built on the HubSpot platform. It is reported by them as being used for website analytics. | Performance | 0 |
| ApifyAcqRef | This cookie is used by Apify to identify from which website the user came to Apify. | Performance | 364 |
| ApifyAcqSrc | This cookie is used by Apify to identify from which website the user came to Apify. | Performance | 364 |
| hubspotutk | This cookie name is associated with websites built on the HubSpot platform. HubSpot report that its purpose is user authentication. As a persistent rather than a session cookie it cannot be classified as Strictly Necessary. | Functional | 389 |
| _ALGOLIA | This cookie name is associated with websites built on the HubSpot platform. HubSpot report that its purpose is user authentication. As a persistent rather than a session cookie it cannot be classified as Strictly Necessary. | Functional | 179 |
| kvcd | Social Media sharing tracking cookie. | Targeting | 0 |
| _gat_gtag_xxxxxxxxxxxxxxxxxxxxxxxxxxx | Google Analytics | Targeting | 0 |
| km_vs | Social Media sharing tracking cookie. | Targeting | 0 |
*Please note that the table serves for general information purposes. The information included in it may change over time and the table may be updated from time to time accordingly.