Cookie Policy
FIRST SEEN 2026-07-29 · VERSION 20260729_rev01 · COMPARED WITH 20250206_rev01
Full text changes — 20250206_rev01 to 20260729_rev01
COLOUR MARKS THE SEVERITY OF A FLAGGED CLAUSE · + AND − MARK ADDED AND REMOVED
| 1 | FREEPIK COMPANY, S.L.U., hereafter Freepik, is the owner, and thus responsible, of the projects indicated below, including any of their subdomains and sections, hereafter "Website": | |
| 1 | FREEPIK COMPANY, S.L.U., hereinafter Magnific, owns and is therefore responsible for the projects indicated below, including any of their subdomains or sections, hereinafter the "Website": | |
| 2 | 2 | |
| 3 | In this document we provide you with information about cookies, both in a general way and about the ones we use in particular. | |
| 3 | In this document we provide you with information about cookies in general, and then about the ones we use in particular. Likewise, at this [link](https://www.magnific.com/es/legal/privacidad) you can review our privacy policy. | |
| 4 | 4 | |
| 5 | 5 | #### II. SPECIFIC INFORMATION ABOUT COOKIES USED ON OUR WEBSITES |
| 6 | 6 | |
| 7 | **Freepik only hires tier-1 service providers.** | |
| 7 | **Magnific only works with first-class service providers.** | |
| 8 | 8 | |
| 9 | Regarding the control and management of cookies and similar technologies, we use One Trust "cookie compliance" technology. | |
| 9 | In relation to the control and management of cookies and similar technologies, we use One Trust's "cookie compliance" technology. | |
| 10 | 10 | |
| 11 | Through our cookie setting panel (powered by One Trust) you can consent or reject, granularly, the use of our cookies and those of third parties, as well as certain data processing carried out by third parties based on their legitimate interests. By selecting "Reject all" you will also block said data processing. | |
| 11 | Through our configuration panel (powered by One Trust) you can consent to or reject, granularly, the use of our cookies and those of third parties, as well as certain data processing carried out by third parties based on their legitimate interests. By selecting "Reject all" you will also block such data processing. | |
| 12 | 12 | |
| 13 | Cookies (and similar technologies) help us better understand what interests and helps our users most, and to improve our services. | |
| 13 | Cookies (and similar technologies) help us better understand what most interests and helps our users and to improve our services. | |
| 14 | 14 | |
| 15 | You can find extended information and clarification about each category of cookies used on our websites through our cookie settings panel, to which you access by clicking on "Cookie setting", located at the bottom of all our webs, in section "Legal". | |
| 15 | You can find information and explanations about each category of cookies used on our websites in our configuration panel, which you can access from "cookie settings" (a link present in the footer of all the pages of our website, in the "legal" column). | |
| 16 | 16 | |
| 17 | Please find below the description of some of them: | |
| 18 | ||
| 19 | 17 | ##### Session and persistent cookies |
| 20 | 18 | |
| 21 | In addition, we and our partners use "persistent cookies" to withhold information about those users who repeatedly access any of our websites. | |
| 19 | On the other hand, we and our partners use "persistent cookies" to retain information about those users who repeatedly access one of our internet pages. | |
| 22 | 20 | |
| 23 | 21 | ##### Analytical cookies |
| 24 | 22 | |
| 25 | ##### Cookies can also be "first-party" or "third-party" cookies | |
| 23 | ##### Cookies can also be "first-party" or "third-party". | |
| 26 | 24 | |
| 27 | "First-party" cookies are those that are sent to the user's terminal equipment from a device or domain managed by Freepik as editor of the website from which the services requested by the user are provided. | |
| 25 | "First-party" cookies are those that are sent to the user's terminal device from a computer or domain managed by Magnific as the publisher of the web portal and from which the services requested by the user are provided. | |
| 28 | 26 | |
| 29 | "Third-party" cookies are those that are sent to the user's terminal equipment from a device or domain that is not managed by Freepik, but by another organization, which processes the data obtained through such cookies. | |
| 27 | "Third-party" cookies are those that are loaded onto the user's terminal device from a computer or domain that is not managed by Magnific, but by a different entity, on the occasion of your visit to our websites. | |
| 30 | 28 | |
| 31 | You can find out complete information about the data processing carried out by these third parties (lawful bases, international data transfers carried out, retention periods, exercise of rights of access, erasure, restriction of processing, portability and rectification, and how exercise your rights, ... in their respective policies linked in this text and in the cookie tables). | |
| 29 | You can find complete information about the data processing carried out by these third parties (legal bases, international data transfers carried out, retention periods or the exercise of rights of access, deletion, restriction, portability and rectification, how to exercise your rights, etc.) in their respective policies linked in this text and in our own cookie tables. | |
| 32 | 30 | |
| 33 | You will find detailed information about all cookies used on each of our websites in the cookie table at the end of this text. | |
| 31 | You will find detailed information about all the cookies used on each of our websites in the cookie table, at the end of this text. | |
| 34 | 32 | |
| 35 | #### Information on the processing of data shared with our advertising partners | |
| 33 | #### Information about data processing shared with our advertising partners | |
| 36 | 34 | |
| 37 | ##### Preliminary information | |
| 35 | ##### Preliminary information: | |
| 38 | 36 | |
| 39 | In the field of online advertising, cookies and other similar technologies allow website visitors to be recognized or singled out (but not identified in the traditional sense of the word, that is, by their names, surnames, ID number or email address) and classified into groups or "audiences" based on their interests. | |
| 37 | In the field of online advertising, cookies and other similar technologies allow website visitors to be recognized or singled out (but not identified in the traditional sense, by first name, surname, tax ID or email) and classified into groups or "audiences" based on the interests they express through their web browsing. | |
| 40 | 38 | |
| 41 | Knowing your interests and personalizing the advertising displayed to you in accordance with them is possible thanks to the use of these cookies and similar technologies. | |
| 39 | Knowing your interests and personalizing the advertising shown to you accordingly is possible thanks to the use of these cookies and similar technologies. | |
| 42 | 40 | |
| 43 | ##### Shutterstock and Getty Images' advertising | |
| 41 | ##### Magnific advertising | |
| 44 | 42 | |
| 45 | Freepik, in turn, offers third-party advertising (Getty Images and Shutterstock), and tracks its users through [Google Analytics](https://marketingplatform.google.com/intl/en_uk/about/analytics/) when they click on its advertising banners, to check the performance in terms of conversion rate on that advertiser's website. | |
| 43 | Magnific contracts personalized advertising services from Pinterest, Google Ads, X, Meta and LinkedIn to attract potential new users to our website who have been profiled by these platforms according to their interests. Magnific selects, among those profiles, those we understand may be interested in our products (for example, users who have already visited our websites or users in a certain age range or geographic location). | |
| 46 | 44 | |
| 47 | ##### Freepik advertising | |
| 45 | These platforms integrate "cookies" and other technologies into our website that, -subject to your consent to their use-, allow them to observe, for example, whether their users have only accessed the Magnific website and left without doing anything further, or have downloaded products or become Premium users. | |
| 48 | 46 | |
| 49 | Freepik contracts personalized advertising services of Pinterest, Google Ads, X, Meta and Linkedin to attract potential new users to our websites who have been profiled by such platforms according to their interests. Freepik selects, among these profiles, those who we understand may be interested in our products (for example, those users who had visited our websites, or users within a determined age or geographical location). | |
| 47 | They then supply us with that information in an aggregated and anonymous manner in order to bill us accordingly, which allows us to better understand the profitability of our advertising campaigns on each platform. | |
| 50 | 48 | |
| 51 | These platforms integrate "cookies" and other technologies on our website. These technologies allow them, after you have provided consent, to track, for example, whether their users have only accessed Freepik's websites to just quit, they have downloaded any products or have become Premium users. | |
| 49 | In addition, we may show ads to visitors who have left our website e.g. without registering, to try to finally convince them to do so (retargeting). | |
| 52 | 50 | |
| 53 | Then, they provide us with this information in an aggregated and anonymous way to bill us accordingly, allowing us to better understand the price and profitability of our advertising campaigns on each platform. | |
| 51 | In relation to all this data processing, Magnific is a "joint controller" together with each of those platforms, in relation to (i) the selection of the interests of their users to whom we ask that our advertising be shown; (ii) their tracking and observation on our website; and (iii) the provision of statistical and aggregated data to Magnific about the result of these campaigns, that is, the conversion, where applicable, into our customers. | |
| 54 | 52 | |
| 55 | Furthermore, we may show advertisements to visitors who have left our website, for example without registering, to try to convince them to do so (retargeting techniques). | |
| 53 | All this processing is carried out without Magnific being able to identify you: we only identify you when you register as a free or premium user. | |
| 56 | 54 | |
| 57 | Regarding these data processing operations, Freepik is a "joint controller" together with each of those platforms, in relation to (i) the selection of the interests of its users to whom we request our advertising is displayed; (ii) their monitoring and observation on our websites; and (iii) the provision of statistical and aggregated data to Freepik on the result of these campaigns, that is, the conversion rate , if applicable, into our clients. | |
| 55 | Otherwise, Magnific does not participate in or take responsibility for the processing carried out by the aforementioned advertisers and platforms for their own purposes, either before or after the processing carried out jointly with Magnific. | |
| 58 | 56 | |
| 59 | All these processing operations are carried out without Freepik being able to identify you: we only identify you when you register as a free or premium user. | |
| 60 | ||
| 61 | Otherwise, Freepik does not participate in and therefore is not a controller of the processing operations that advertisers and platforms carry out for their own purposes, either prior or subsequent to those other processing operations carried out together with Freepik. | |
| 62 | ||
| 63 | 57 | ##### International data transfers |
| 64 | 58 | |
| 65 | Regarding Freepik advertising, we participate together with our partners in the international transfer of personal data to countries with a potentially lower level of protection than that imposed by the General Data Protection Regulation. These international transfers are therefore based on standard contractual clauses. | |
| 59 | In relation to advertising on the Magnific website, we participate with our partners in the international transfer of data to countries with a level of personal data protection that is potentially lower than that imposed by the General Data Protection Regulation. Personalized online advertising entails, by definition, making the data processed through cookies available worldwide to, potentially, thousands of companies. | |
| 66 | 60 | |
| 67 | In relation to third-party advertising, Freepik's controllership is limited to the duties of providing information and obtaining our website visitors' consent for the purpose of using their cookies to show personalized advertising. | |
| 61 | In relation to third-party advertising, Magnific's responsibility is limited to informing and obtaining the consent of the visitors of our website in relation to the use of their cookies to show them personalized advertising. | |
| 68 | 62 | |
| 69 | ##### Additional Information | |
| 63 | ##### Additional information | |
| 70 | 64 | |
| 71 | Below, and in the corresponding cookie tables, Freepik provides you with the links to the information offered by each of these companies and platforms regarding the joint controllership situations already described and their own processing operations (lawful bases, international data transfers carried out, retention periods or the exercise of a right of access, erasure, restriction of processing, portability and rectification). | |
| 65 | Magnific provides you below (and in the respective cookie tables) with the links to the information offered by each of these companies and platforms in relation to the joint-controllership situations described and to their own processing (legal bases, international data transfers carried out, retention periods or the exercise of rights of access, deletion, restriction, portability and rectification). | |
| 72 | 66 | |
| 73 | You can revoke your consent to the use of cookies at any time (but without retroactive effect) via our cookie banner (or by clicking on the "cookie settings" option at the bottom of our website). | |
| 67 | You can revoke your consent to the use of cookies at any time (but without retroactive effect) through our cookie banner (or by clicking the "cookie settings" option located at the bottom of our website). | |
| 74 | 68 | |
| 75 | We remind you again that you can exercise your rights of access, restrictions of processing and / or erasure in relation to the processing of your personal data carried out jointly with the aforementioned platforms: | |
| 69 | We remind you again that you can exercise your rights of access, restriction of processing and/or deletion in relation to the processing of your personal data carried out jointly with the aforementioned platforms: | |
| 76 | 70 | |
| 77 | - Through our email [rpd@freepik.com](mailto:rpd@freepik.com), if you are a registered user of Freepik. | |
| 78 | - And otherwise, before the platforms in which you have a user account (because we will not be able to identify you). | |
| 71 | - Through our email address rpd@magnific.com, if you are a registered Magnific user. | |
| 72 | - And otherwise, before the platforms themselves on which you have a user account (because we will not be able to identify you). | |
| 79 | 73 | |
| 80 | 74 | **Pinterest**: |
| 81 | 75 | |
| 82 | - Privacy Policy: [https://policy.pinterest.com/en/privacy-policy](https://policy.pinterest.com/en/privacy-policy) | |
| 83 | - Cookies Policy: [https://policy.pinterest.com/en/cookies](https://policy.pinterest.com/en/cookies) | |
| 76 | - Privacy Policy: [https://policy.pinterest.com/es/privacy-policy](https://policy.pinterest.com/es/privacy-policy) | |
| 77 | - Cookie Policy: [https://policy.pinterest.com/es/cookies](https://policy.pinterest.com/es/cookies) | |
| 84 | 78 | |
| 85 | 79 | **Google**: |
| 86 | 80 | |
| 87 | - Privacy Policy: [https://policies.google.com/privacy?hl=en-GB](https://policies.google.com/privacy) | |
| 88 | - Cookies Policy: [https://policies.google.com/technologies/cookies?hl=en-GB](https://policies.google.com/technologies/cookies) | |
| 81 | - Privacy Policy: [https://policies.google.com/privacy?hl=es](https://policies.google.com/privacy) | |
| 82 | - Cookie Policy: [https://policies.google.com/technologies/cookies?hl=es](https://policies.google.com/technologies/cookies) | |
| 89 | 83 | |
| 90 | 84 | **X**: |
| 91 | 85 | |
| 92 | - Privacy Policy: [https://x.com/privacy](https://x.com/privacy) | |
| 93 | - Cookie Policy: [https://help.x.com/rules-and-policies/x-cookies](https://help.x.com/rules-and-policies/x-cookies) | |
| 86 | - Privacy Policy: [https://x.com/es/privacy](https://x.com/es/privacy) | |
| 87 | - Cookie Policy: [https://help.x.com/es/rules-and-policies/x-cookies](https://help.x.com/es/rules-and-policies/x-cookies) | |
| 94 | 88 | |
| 95 | 89 | **Meta (Facebook)**: |
| 96 | 90 | |
| 97 | 91 | - Privacy Policy: [https://www.facebook.com/privacy/policy](https://www.facebook.com/privacy/policy) and [https://developers.facebook.com/docs/meta-pixel/implementation/gdpr](https://developers.facebook.com/docs/meta-pixel/implementation/gdpr) |
| 98 | 92 | - Cookie Policy: [https://www.facebook.com/privacy/policies/cookies/](https://www.facebook.com/privacy/policies/cookies/) |
| 99 | - Annex on joint controllership: [https://www.facebook.com/legal/terms/businesstools\_jointprocessing](https://www.facebook.com/legal/terms/businesstools_jointprocessing) | |
| 93 | - Joint-controllership addendum: [https://www.facebook.com/legal/terms/businesstools\_jointprocessing](https://www.facebook.com/legal/terms/businesstools_jointprocessing) | |
| 100 | 94 | |
| 101 | 95 | **LinkedIn**: |
| 102 | 96 | |
| 103 | 97 | - Privacy Policy: [https://www.linkedin.com/legal/privacy-policy](https://www.linkedin.com/legal/privacy-policy) |
| 104 | 98 | - Cookie Policy: [https://www.linkedin.com/legal/cookie-policy](https://www.linkedin.com/legal/cookie-policy) |
| 105 | 99 | |
| 106 | #### Freepik Company's cookie table | |
| 100 | #### Magnific cookie table | |
| 107 | 101 | |
| 108 | In the table below you will find detailed information about all cookies used on Freepik's web pages. | |
| 102 | In the table below you will find detailed information about all the cookies used on the Magnific websites. | |
| 109 | 103 | |
| 110 | ##### First-party cookies on the websites owned by Freepik Company | |
| 104 | ##### First-party cookies on the websites owned by Magnific | |
| 111 | 105 | |
| 112 | | PURPOSE | EXPIRY DATE | DOMAIN | | |
| 106 | | PURPOSE | DURATION | DOMAIN | | |
| 113 | 107 | | --- | --- | --- | |
| 114 | | Language detection. Helps us to collect information about the language preferences of the User to provide visitors with information in their preferred language | Session | Freepik, Contributor | | |
| 115 | | User login. Used to manage and store information about the user login | Session | Freepik, Contributor | | |
| 116 | | Stores URL to redirect the user after finishing the registration or login process | 10 minutes | Freepik (profile) | | |
| 117 | | Remembers user's personal ID each time they log on. This cookie is only created if the user agrees to be remembered | 30 days | Freepik (profile) | | |
| 118 | | Avoids CSRF attacks in forms | 2 hours | Freepik (profile) | | |
| 119 | | Stores information on marketing campaigns in which the User has participated | 30 days | Freepik (profile) | | |
| 120 | | Used in the payment process to redirect the user to the payment platform in case they are logged off | 7 days | Freepik (profile) | | |
| 121 | | Test about payment data. Selection of payment, subscription to Premium | 3 days | Freepik | | |
| 122 | | Test about search activity. Analysis of searches run by the user | 30 days | Freepik | | |
| 123 | | Checks if internal promotions are shown to the user | 2 days | Freepik | | |
| 124 | | Checks if cookies compliance messages are visible on the Website | Session | Freepik | | |
| 125 | | Collects information about visits | 2 years | Freepik | | |
| 126 | | Develops statistics about Premium services advertisements | 1 hour | Freepik | | |
| 127 | | Measures data collected from searches | 30 days | Freepik | | |
| 128 | | Cookie session login | 120 minutes | Wepik | | |
| 108 | | Cookie used to perform metrics and statistics on Premium service ads | 1 hour | Magnific | | |
| 109 | | Cookie used to store the URL to which the user is redirected once login or registration is completed | 10 minutes | Magnific (profile) | | |
| 110 | | Cookie used to collect visit information | 2 years | Magnific | | |
| 111 | | Cookie used to check whether internal promotions are shown to the user | 2 days | Magnific | | |
| 112 | | Cookie used to prevent CSRF attacks on forms | 2 hours | Magnific (profile) | | |
| 113 | | Test on purchase data. Purchase selection, Premium subscription | 3 days | Magnific | | |
| 114 | | Cookie used to store the user ID once they have logged in. This cookie is only created if the user wants to be remembered in their browser | 30 days | Magnific (profile) | | |
| 115 | | Cookie used to store information about marketing campaigns in which the user has participated | 30 days | Magnific (profile) | | |
| 116 | | Test on search data. Analysis of searches carried out by the user | 30 days | Magnific | | |
| 117 | | Cookie used to perform metrics on search data | 30 days | Magnific | | |
| 118 | | Cookie used in the purchase process to redirect the user to the purchase screen if they are not logged in | 7 days | Magnific (profile) | | |
| 119 | | Language detection. This cookie is used to store information about the user's language and display the website in the corresponding language | Session | Magnific, Contributor | | |
| 120 | | User session cookie (login). It is used to manage and store the user's session information | Session | Magnific, Contributor | | |
| 121 | | Cookie used to check whether the Website's cookie information/message has been shown | Session | Magnific | | |
| 122 | | Cookie used to store a partner referral identifier when a user arrives via a partner link. It is required to apply the pricing, loyalty benefits, or promotional conditions associated with that partner. The cookie enables us to provide the service and benefits the user is entitled to, and it is not used for marketing, analytics, or tracking. The value is only processed by our backend to fulfil partner-linked benefits. | 30 days | Magnific | | |
| 129 | 123 | |
| 130 | ##### Third-party cookies in [www.freepik.com](https://www.freepik.com/) | |
| 124 | ##### Third-party cookies of [www.magnific.com](https://www.magnific.com/) | |
| 131 | 125 | |
| 132 | | THIRD PARTY | COOKIE | DESCRIPTION | MORE INFO | | |
| 126 | | PROVIDER | COOKIE | DESCRIPTION | MORE INFORMATION | | |
| 133 | 127 | | --- | --- | --- | --- | |
| 134 | | **Google Analytics** (Analysis) | | We collect information of how users interact with the content of the web. When a user browses the pages of a website, information about the page the user has viewed is collected; for example, URL, time spent on the website, number of pages viewed. It allows us to generate labels or objectives to know if you have bought, what item, how many times... It also collects demographic and navigation data, that is; where does the user come from, how does he get to our website or what campaign does he come from | [Here](https://developers.google.com/analytics/devguides/collection/analyticsjs/cookie-usage) | | |
| 135 | | **Hotjar** (Measuring and Analysis) | \_hjClosedSurveyInvites | Hotjar cookie that is set once a visitor interacts with an External Link Survey invitation modal. It is used to ensure that the same invite does not reappear if it has already been shown. | [Here](https://help.hotjar.com/hc/en-us/articles/115011789248) | | |
| 136 | | \_hjDonePolls | Hotjar cookie that is set once a visitor completes a survey using the On-site Survey widget. It is used to ensure that the same survey does not reappear if it has already been filled in. | | |
| 137 | | \_hjMinimizedPolls | Hotjar cookie that is set once a visitor minimizes an On-site Survey widget. It is used to ensure that the widget stays minimized when the visitor navigates through your site. | | |
| 138 | | \_hjShownFeedbackMessage | Hotjar cookie that is set when a visitor minimizes or completes Incoming Feedback. This is done so that the Incoming Feedback will load as minimized immediately if the visitor navigates to another page where it is set to show. | | |
| 139 | | \_hjid | Hotjar cookie that is set when the customer 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. | | |
| 140 | | \_hjRecordingLastActivity | This should be found in Session storage (as opposed to cookies). This gets updated when a visitor recording starts and when data is sent through the WebSocket (the visitor performs an action that Hotjar records). | | |
| 141 | | \_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. | | |
| 142 | | \_hjUserAttributesHash | User Attributes sent through the Hotjar Identify API are cached for the duration of the session in order to know when an attribute has changed and needs to be updated. | | |
| 143 | | \_hjCachedUserAttributes | This cookie stores User Attributes which are sent through the Hotjar Identify API, whenever the user is not in the sample. These attributes will only be saved if the user interacts with a Hotjar Feedback tool. | | |
| 144 | | \_hjLocalStorageTest | This cookie is used to check if the Hotjar Tracking Script can use local storage. If it can, a value of 1 is set in this cookie. The data stored in\_hjLocalStorageTest has no expiration time, but it is deleted almost immediately after it is created. | | |
| 145 | | \_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. | | |
| 146 | | \_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. | | |
| 147 | | \_hjAbsoluteSessionInProgress | This cookie is used to detect the first pageview session of a user. This is a True/False flag set by the cookie. | | |
| 148 | | **Google Tag Manager** (Advertising and Analysis) | | Google Tag Manager is a tag management system that allows third parties to add functionality to websites, video content, and mobile applications. Examples of such solutions include web analytics, campaign analytics, audience measurement, and personalisation. It allows you to easily and quickly update tags and code snippets on a website or your mobile applications, such as those intended for traffic analysis and optimising marketing campaigns. Custom, third-party, or AdWords tags, Google Analytics, Firebase Analytics and Floodlight, Twitter Ads, Hotjar tags can be added and updated. It is used for the purpose of managing the different conversion codes of the online marketing and retargeting tools. | [Here](https://support.google.com/tagmanager/answer/6102821) | | |
| 149 | | **Salesforce** (Performance) | sfdc-stream | Used to properly route server requests within Salesforce infrastructure for sticky sessions. | [Here](https://help.salesforce.com/s/articleView) | | |
| 150 | | oid | Stores the last logged in org for redirecting requests. Used for logging whether the cookie is present in site and community guest-user requests. | | |
| 151 | | CookieConsentPolicy | Used to apply end-user cookie consent preferences set by our client-side utility. | | |
| 152 | | pctrk | Used to track unique page visitors in Experiences. | | |
| 153 | | renderCtx | Used to store site parameters in the session for reuse across requests by a single client for functionality and performance reasons. | | |
| 154 | | **Google** (Advertising / Analysis) | NID | Used by Google to personalise the advertisements shown in its spaces. | [Here](https://policies.google.com/technologies/cookies) | | |
| 128 | | **Google Analytics (Analytics and Measurement)** | | We record how users interact with the website's content. When a user browses the pages of a website, information is recorded about the page the user has viewed; for example, the URL of the page, time spent, number of pages viewed. And it allows us to generate tags or goals to know whether they have made a purchase, which item, how many times... It also collects demographic and browsing data, that is, where the user comes from, how they reach our website or which campaign they come from. | [Here](https://developers.google.com/analytics/devguides/collection/analyticsjs/cookie-usage) | | |
| 129 | | **Hotjar (Analytics and Measurement)** | \_hjClosedSurveyInvites | It is set once a visitor interacts with an external link Survey invitation modal. It is used to ensure that the same invitation does not appear again if it has already been shown. | [Here](https://help.hotjar.com/hc/en-us/articles/115011789248) | | |
| 130 | | \_hjDonePolls | It is set once a visitor completes a survey using the Survey widget on the site. It is used to ensure that the same survey does not appear again if it has already been filled in. | | |
| 131 | | \_hjMinimizedPolls | It is set once a visitor minimizes a survey widget on the site. It is used to ensure that the widget remains minimized while the visitor browses your site. | | |
| 132 | | \_hjShownFeedbackMessage | It is set when a visitor minimizes or completes incoming feedback. This is done so that incoming feedback loads as minimized immediately if the visitor navigates to another page where it is configured to be shown. | | |
| 133 | | \_hjid | It is set when the customer first lands on a page with the Hotjar script. It is used to retain the Hotjar User ID, unique to that site in the browser. This ensures that behavior in subsequent visits to the same site is attributed to the same user ID. | | |
| 134 | | \_hjRecordingLastActivity | This should be found in session storage (unlike cookies). It is updated when a visitor's recording starts and when data is sent through the WebSocket (the visitor performs an action that Hotjar records). | | |
| 135 | | \_hjTLDTest | When the Hotjar script runs, we try to determine the most generic cookie path we should use, instead of the page host name. This is done so that cookies can be shared across subdomains (where applicable). To determine this, we try to store the cookie \_hjTLDTest for different URL substring alternatives until it fails. After this check, the cookie is deleted. | | |
| 136 | | \_hjUserAttributesHash | User attributes sent through Hotjar's Identify API are cached for the duration of the session in order to know when an attribute has changed and needs to be updated. | | |
| 137 | | \_hjCachedUserAttributes | This cookie stores user attributes that are sent through Hotjar's Identify API, whenever the user is not in the sample. These attributes will only be saved if the user interacts with a Hotjar Feedback tool. | | |
| 138 | | \_hjLocalStorageTest | This cookie is used to check whether the Hotjar Tracking Script can use local storage. If it can, a value of 1 is set in this cookie. The data stored in \_hjLocalStorageTest has no expiration date, but is deleted almost immediately after being created. | | |
| 139 | | \_hjIncludedInPageviewSample | This cookie is set so that Hotjar knows whether that visitor is included in the data sampling defined by your site's page view limit. | | |
| 140 | | \_hjIncludedInSessionSample | This cookie is set so that Hotjar knows whether that visitor is included in the data sampling defined by your site's daily session limit. | | |
| 141 | | \_hjAbsoluteSessionInProgress | This cookie is used to detect a user's first page-view session. This is a True / False flag set by the cookie. | | |
| 142 | | **Google Tag Manager (Advertising and analytics)** | | Google Tag Manager is a tag management system that allows third parties to add functionality to websites, video content and mobile applications. Examples of such solutions include web analytics, campaign analysis, audience measurement, personalization, and it allows you to easily and quickly update the tags and code snippets of a website or its mobile applications, such as those intended for traffic analysis and to optimize marketing campaigns. Custom, third-party or AdWords, Google Analytics, Firebase Analytics and Floodlight, Twitter Ads, Hotjar tags can be added and updated. It is used for the purpose of managing the different conversion codes of online Marketing and retargeting tools. | [Here](https://support.google.com/tagmanager/answer/6102821) | | |
| 143 | | **Salesforce (Performance)** | sfdc-stream | It is used to correctly route server requests within the Salesforce infrastructure for sticky sessions. | [Here](https://help.salesforce.com/s/articleView) | | |
| 144 | | oid | It stores the last organization that logged in for redirect requests. It is used to record whether the cookie is present in community and site guest-user requests. | | |
| 145 | | CookieConsentPolicy | It is used to apply the end user's cookie consent preferences set by our client-side utility. | | |
| 146 | | pctrk | It is used to track unique page visitors in Experiences. | | |
| 147 | | renderCtx | It is used to store site parameters in the session for reuse across requests by a single client for feature and performance reasons. | | |
| 148 | | **Google (Advertising and analytics)** | NID | Used by Google to personalize the ads shown in its spaces. | [Here](https://policies.google.com/technologies/types) | | |
| 155 | 149 | | \_ga | Used by Google Analytics to distinguish users. | |
| 156 | 150 | | \_gid | Used by Google Analytics to distinguish users. | |
| 157 | | 1P\_JAR | Google uses this cookie to personalise ads that may be of interest to you. | | |
| 158 | | hsid | Security cookie to authenticate users, prevent fraudulent use of login credentials and protect user data from unauthorised third parties. | | |
| 159 | | sidcc | Security cookie to authenticate users, prevent fraudulent use of login credentials and protect user data from unauthorised third parties. | | |
| 160 | | sidcc | Used by Google to obtain anonymous browsing information | | |
| 161 | | sapisid | Created when you sign in to a Google Account in order to stay connected to that same Google Account when you use its services again. | | |
| 162 | | apisid | Created when you sign in to a Google Account in order to stay signed in to that same Google Account when you use its services again. | | |
| 163 | | ssid | Created when you sign in to a Google Account in order to stay signed in to that same Google Account when you use its services again. | | |
| 151 | | 1P\_JAR | Google uses this cookie to personalize ads that may be of interest to you. | | |
| 152 | | hsid | Security cookie to authenticate users, prevent the fraudulent use of login credentials and protect user data from unauthorized third parties. | | |
| 153 | | sidcc | Security cookie to authenticate users, prevent the fraudulent use of login credentials and protect user data from unauthorized third parties. | | |
| 154 | | sidcc | Used by Google to obtain anonymous information about browsing. | | |
| 155 | | sapisid | It is created when logging into a Google account in order to stay connected to that same Google account when using its services again. | | |
| 156 | | apisid | It is created when logging into a Google account in order to stay connected to that same Google account when using its services again. | | |
| 157 | | ssid | It is created when logging into a Google account in order to stay connected to that same Google account when using its services again. | | |
| 164 | 158 | | dsid | Used by Google to show more relevant ads. | |
| 165 | 159 | | ide | Used by Google to show more relevant ads. | |
| 166 | | anid | Used by Google to personalise the ads shown in its spaces. | | |
| 167 | | refmodal | Own cookie. Used by Google Analytics to collect the value of the referrer in the modal. | | |
| 168 | | **Pinterest** (Advertising / Analysis) | | We will impact users who have visited the website or are registered with a banner ad, we will use the data of registered users to avoid impacting with campaigns whose objective is a premium subscription and we will look for users with similar online behaviour to registered users or users who have visited the website. This dataset will be used both to reach our target audience through online campaign segmentation and to measure campaign results. | [Here](https://policy.pinterest.com/es/cookies) | | |
| 169 | | **Google Ads** (Advertising / Analysis) | | Look a likes, Rmk and Opt-out. We collect data from visitors to our pages to analyse behaviour and impact them with our ads if they do not register or do not subscribe. And to be able to impact users similar to those who visit us or similar to registered or subscribed users who are not customers. | [Here](https://policies.google.com/privacy) | | |
| 170 | | **Google Tag Manager** (Advertising / Analysis) | | Google Tag Manager is a tag management system that allows third parties to add functionality to websites, video content and mobile applications. Examples of such solutions include web analytics, campaign analytics, audience measurement, personalisation, allows you to easily and quickly update tags and code snippets on a website or your mobile applications, such as those for traffic analysis and optimising marketing campaigns. Custom, third-party or AdWords, Google Analytics, Firebase Analytics and Floodlight, Facebbok Ads, Twitter Ads, Hotjar tags can be added and updated. It is used for the purpose of managing the different conversion codes of the online marketing and retargeting tools. | [Here](https://support.google.com/tagmanager/answer/6102821) | | |
| 171 | | **ContentSquare** | \_cs\_id | This cookie contains the ContentSquare user ID. | [Here](https://www.contentsquare.com/privacy-and-security/) | | |
| 172 | | \_cs\_s | This cookie contains the number of page views within the current session for ContentSquare Solution. | | |
| 173 | | \_cs\_vars | This cookie is used by ContentSquare to record custom variables. | | |
| 174 | | \_cs\_ex | This cookie is used by ContentSquare to exclude some visitors from the collection. | | |
| 175 | | \_cs\_c | This cookie is used by ContentSquare to store the user's consent to be tracked. | | |
| 176 | | \_cs\_optout | This cookie is used by ContentSquare to exclude some visitors from the collection. | | |
| 177 | | \_cs\_mk | This cookie is used for Google Analytics integrations. | | |
| 178 | | **OneTrust** | OptanonConsent | OptanonConsent and OptanonAlertBoxClosed are cookies related to our Cookie Compliance Solution. They are used to store your preferences with regards to cookies and other trackers and identify and interpret user interactions with the banner (for example, closing a banner means rejection of non-essential trackers). | [Here](https://www.onetrust.com/cookie-policy/) | | |
| 160 | | anid | Used by Google to personalize the ads shown in its spaces. | | |
| 161 | | refmodal | First-party cookie. Used so that Google Analytics collects the referrer value in the modal | | |
| 162 | | **Pinterest (Advertising and analytics)** | | We will reach users who have visited the website or are registered on it with an advertising banner, we will use the data of registered users so as not to target them with campaigns whose objective is a premium subscription, and we will look for users with online behavior similar to that of registered users or those who have visited the website. This data set will be used both to reach our target audience through online campaign segmentation and to measure the results of those campaigns. | [Here](https://policy.pinterest.com/es/cookies) | | |
| 163 | | **Google Ads (Advertising and analytics)** | | Look-alikes, Rmk and Exclusion. We collect data from visitors to our pages to analyze behaviors and target them with our ads if they ultimately do not register or subscribe. And to be able to target users similar to those who visit us or similar to registered or subscribed users who are not customers. | [Here](https://policies.google.com/privacy) | | |
| 164 | | **OneTrust** | OptanonConsent | OptanonConsent and OptanonAlertBoxClosed are cookies related to our cookie compliance solution. They are used to store your preferences regarding cookies and other trackers and to identify and interpret the user's interactions with the banner (for example, closing a banner means the rejection of non-essential trackers). | [Here](https://www.onetrust.com/cookie-policy/) | | |
| 179 | 165 | | OptanonAlertBoxClosed | |
| 180 | | **Twitter** | \_twclid | Cookies used for attribution. Advertising cookie. First Party | [Here](https://business.twitter.com/en/help/campaign-measurement-and-analytics/conversion-tracking-for-websites/about-conversion-tracking.html) | | |
| 166 | | **X (Twitter)** | \_twclid | Cookies used for attribution. Advertising cookie. First Party | [Here](https://business.twitter.com/en/help/campaign-measurement-and-analytics/conversion-tracking-for-websites/about-conversion-tracking.html) | | |
| 181 | 167 | | muc\_ads | Cookies used for attribution. Advertising cookie. Third Party | |
| 182 | 168 | | auth\_token | Cookies used for attribution. Login cookie. Third Party | |
| 183 | 169 | | personalization\_id | Cookies used for attribution. Advertising cookie. Third Party | |
| 170 | | **Google Analytics 4 (Analytics and Measurement)** | | We use Google Analytics 4 to measure and analyze user behavior on our website: pages visited, time spent, conversion events and traffic sources. This information helps us improve our product and understand how users interact with Magnific. | [Here](https://policies.google.com/technologies/cookies) | | |
| 171 | | \_ga | First-party cookie used by Google Analytics to distinguish users. Expires after 2 years. | | | |
| 172 | | \_ga\_<container-id> | First-party cookie used to maintain the session state. Expires after 2 years. | | | |
| 173 | | \_gid | First-party cookie used by Google Analytics to distinguish users. Expires after 24 hours. | | | |
| 174 | | \_gat | First-party cookie used to limit the request rate. Expires after 1 minute. | | | |
| 175 | | **PostHog (Analytics and Measurement)** | | We use PostHog to record product events, user funnels and feature usage. This data allows us to make data-driven decisions about product improvements and to understand how users interact with specific Magnific features. | [Here](https://posthog.com/docs/privacy/cookies) | | |
| 176 | | ph\_<project\_id>\_posthog | First-party cookie used by PostHog to store the anonymous user ID, session data and feature flags. Expires after 1 year. | | | |
| 177 | | **Apollo.io (Advertising and Analytics)** | | We use Apollo.io to identify the companies that visit our website and to support our B2B lead-generation efforts. This helps us know which companies are interested in Magnific and reach decision-makers through relevant campaigns. | [Here](https://www.apollo.io/privacy-policy) | | |
| 178 | | apollo\_sid | First-party cookie used by Apollo.io to identify the user's session on the website. | | | |
| 179 | | apollo\_anonymous\_id | First-party cookie used by Apollo.io to track anonymous visitors for company-identification purposes. | | | |
| 180 | | **Google Ads (Advertising)** | | We use Google Ads to run paid search and display campaigns aimed at attracting new users to Magnific. We measure conversions and use remarketing lists to re-target users who have already visited our website but have not yet subscribed. | [Here](https://policies.google.com/technologies/ads) | | |
| 181 | | \_gcl\_au | First-party cookie used by Google AdSense to experiment with advertising effectiveness across different websites. | | | |
| 182 | | \_gcl\_aw | First-party cookie that stores click information when a user arrives from a Google Ads advertisement. | | | |
| 183 | | \_gcl\_dc | First-party cookie used by Google DoubleClick for advertising conversion tracking. | | | |
| 184 | | IDE | Third-party cookie used by Google DoubleClick to record and report user actions after viewing or clicking on an ad. | | | |
| 185 | | DSID | Third-party cookie used by Google DoubleClick to identify a user who has logged in on non-Google sites. | | | |
| 186 | | **Meta (Advertising and Analytics)** | | We will target users who have visited the website or are registered with ads on Facebook and Instagram. We will use the data of registered users so as not to target them with campaigns whose objective is a premium subscription, and we will look for users with online behavior similar to that of registered users or those who have visited the website. This data set will be used both to reach our target audience through online campaign segmentation and to measure campaign results on the Meta advertising network. | [Here](https://www.facebook.com/privacy/policies/cookies/) | | |
| 187 | | \_fbp | First-party cookie used by Meta to display, measure and improve the relevance of ads. | | | |
| 188 | | \_fbc | First-party cookie that stores the last click identifier (fbclid) when a user arrives at the website from a Meta advertisement. | | | |
| 189 | | fr | Third-party cookie used by Meta for advertising, its delivery and measurement. | | | |
| 190 | | tr | Third-party tracking cookie used by Meta for ad measurement and attribution. | | | |
| 191 | | **Reddit (Advertising)** | | We use Reddit Ads to reach communities of creative professionals and AI enthusiasts who may be interested in Magnific. We measure conversions and create audience segments to optimize our campaigns on the Reddit platform. | [Here](https://www.reddit.com/policies/cookies) | | |
| 192 | | rdt\_uuid | First-party cookie used by Reddit to assign a unique identifier to the user for conversion tracking and attribution purposes. | | | |
| 193 | | \_rdt\_uuid | First-party cookie used by the Reddit pixel to track user activity and ad performance on the website. | | | |
| 194 | | **LinkedIn (Advertising and Analytics)** | | We collect data from visitors to our pages to analyze their behavior and target them with our ads on LinkedIn if they do not register or subscribe. We also use this data to reach professionals with profiles similar to those of our registered or subscribed users, and to measure the performance of our B2B advertising campaigns. | [Here](https://www.linkedin.com/legal/cookie-policy) | | |
| 195 | | bcookie | Third-party browser-identifier cookie, used by LinkedIn to recognize the browser visiting the website. | | | |
| 196 | | lidc | Third-party cookie used by LinkedIn for routing between data centers. | | | |
| 197 | | li\_sugr | Third-party cookie used by LinkedIn to perform a probabilistic match of a user's identity outside the designated countries. | | | |
| 198 | | UserMatchHistory | Third-party cookie used by LinkedIn Ads for identifier synchronization (ID syncs). | | | |
| 199 | | AnalyticsSyncHistory | Third-party cookie used by LinkedIn to store information about when a synchronization was performed with the lms\_analytics cookie. | | | |
| 200 | | li\_gc | First-party cookie used by LinkedIn to store visitors' consent regarding the use of cookies for non-essential purposes. | | | |
| 201 | | **X - Twitter (Advertising)** | | We use X (formerly Twitter) Ads to run campaigns aimed at users interested in AI, design and creative tools. We measure conversions and create custom audiences from website visitors to re-target potential subscribers. | [Here](https://help.twitter.com/en/rules-and-policies/twitter-cookies) | | |
| 202 | | personalization\_id | Third-party cookie used by X to personalize the user experience and show targeted advertising on and off the X platform. | | | |
| 203 | | guest\_id | Third-party cookie used by X to identify guest users for analytics and ad-targeting purposes. | | | |
| 204 | | \_ga | Third-party cookie used by X together with Google Analytics for traffic analysis. | | | |
| 205 | | **TikTok (Advertising)** | | We use TikTok Ads to reach younger and more creative audiences through video campaigns. We measure conversions from our TikTok ads and create custom audiences from website visitors to improve campaign performance. | [Here](https://www.tiktok.com/legal/page/global/cookie-policy/en) | | |
| 206 | | \_ttp | First-party cookie used by TikTok to track user behavior and measure the effectiveness of advertising campaigns. | | | |
| 207 | | tt\_webid\_v2 | Third-party cookie used by TikTok to assign a unique identifier to a web user for ad-targeting and conversion-tracking purposes. | | | |
| 208 | | ttwid | Third-party cookie used by TikTok to store a unique session identifier for users who visit sites with TikTok pixels. | | | |
| 184 | 209 | |
| 185 | ##### Third-party cookies in [www.wepik.com](https://www.wepik.com/) | |
| 210 | ##### Third-party cookies of [www.storyset.com](http://www.storyset.com/) | |
| 186 | 211 | |
| 187 | | THIRD PARTY | COOKIE | DESCRIPTION | MORE INFO | | |
| 212 | | PROVIDER | COOKIE | DESCRIPTION | MORE INFORMATION | | |
| 188 | 213 | | --- | --- | --- | --- | |
| 189 | | **Google Analytics** (Analysis) | | We collect information of how users interact with the content of the web. When a user browses the pages of a website, information about the page the user has viewed is colected; for example, URL, time spent on the website, number of pages viewed. It allows us to generate labels or objectives to know if you have bought, what item, how many times ... It also collects demographic and navigation data, that is; where does the user come from, how does he get to our website or what campaign does he come from | [Here](https://developers.google.com/analytics/devguides/collection/analyticsjs/cookie-usage) | | |
| 190 | | **CloudFlare** (Performance / Functionality) | \_cflb, \_cf\_bm y \_cfduid | It is used to override any security restrictions based on the IP address the visitor is coming from. It does not correspond to any user identification in the web application, nor does the cookie store any personally identifiable information | [Here](https://support.cloudflare.com/hc/en-us/articles/200170156-What-does-the-Cloudflare-cfduid-cookie-do-) | | |
| 191 | | **Pinterest** (Advertising / Analysis) | | We will impact users who have visited the website or are registered on it with an advertising banner, we will use the data of registered users so as not to impact campaigns whose objective is premium subscription and we will look for users with similar online behavior to registered users or who have visited the web. This set of data will be used both to reach our target audience through online campaign segmentation and to measure their results. | [Here](https://policy.pinterest.com/es/cookies) | | |
| 192 | | **Google Tag Manager** (Advertising / Analysis) | | Google Tag Manager is a tag management system that allows third parties to add functionality to websites, video content, and mobile applications. Examples of such solutions include web analytics, campaign analytics, audience measurement, personalization, allows you to quickly and easily update tags and code snippets on a website or your mobile applications, such as those intended for analytics traffic and optimize marketing campaigns. You can add and update custom, third-party or AdWords tags, Google Analytics, Firebase Analytics and Floodlight, Facebbok Ads, Twitter Ads, Hotjar. It is used in order to manage the different conversion codes of the online Marketing and retargeting tools | [Here](https://support.google.com/tagmanager/answer/6102821) | | |
| 193 | | **Salesforce** (Performance) | sfdc-stream | Used to properly route server requests within Salesforce infrastructure for sticky sessions. | [Here](https://support.google.com/tagmanager/answer/6102821) | | |
| 194 | | CookieConsentPolicy | Used to apply end-user cookie consent preferences set by our client-side utility. | | |
| 195 | | pctrk | Used to track unique page visitors in Experiences. | | |
| 196 | | renderCtx | Used to store site parameters in the session for reuse across requests by a single client for functionality and performance reasons. | | |
| 197 | | **OneTrust** | OptanonConsent | OptanonConsent and OptanonAlertBoxClosed are cookies related to our Cookie Compliance Solution. They are used to store your preferences with regards to cookies and other trackers and identify and interpret user interactions with the banner (for example, closing a banner means rejection of non-essential trackers). | [Here](https://www.onetrust.com/cookie-policy/) | | |
| 214 | | **Google Analytics (Analytics and Measurement)** | | We record how users interact with the website's content. When a user browses the pages of a website, information is recorded about the page the user has viewed; for example, the URL of the page, time spent, number of pages viewed. And it allows us to generate tags or goals to know whether they have made a purchase, which item, how many times... It also collects demographic and browsing data, that is, where the user comes from, how they reach our website or which campaign they come from. | [Here](https://developers.google.com/analytics/devguides/collection/analyticsjs/cookie-usage) | | |
| 215 | | **OneTrust** | OptanonConsent | OptanonConsent and OptanonAlertBoxClosed are cookies related to our cookie compliance solution. They are used to store your preferences regarding cookies and other trackers and to identify and interpret the user's interactions with the banner (for example, closing a banner means the rejection of non-essential trackers). | [Here](https://www.onetrust.com/cookie-policy/) | | |
| 198 | 216 | | OptanonAlertBoxClosed | |
| 199 | | **Google Ads** (Advertising / Analysis) | | We collect data from visitors to our pages to analyze behavior and impact them with our ads if they finally do not register or do not subscribe. Also, to be able to impact users similar to those who visit us or similar to those registered or subscribed that are not clients. | [Here](https://policies.google.com/privacy) | | |
| 200 | | **ContentSquare** | \_cs\_id | This cookie contains the ContentSquare user ID. | [Here](https://www.contentsquare.com/privacy-and-security/) | | |
| 201 | | \_cs\_s | This cookie contains the number of page views within the current session for ContentSquare Solution. | | |
| 202 | | \_cs\_vars | This cookie is used by ContentSquare to record custom variables. | | |
| 203 | | \_cs\_ex | This cookie is used by ContentSquare to exclude some visitors from the collection. | | |
| 204 | | \_cs\_c | This cookie is used by ContentSquare to store the user's consent to be tracked | | |
| 205 | | \_cs\_optout | This cookie is used by ContentSquare to exclude some visitors from the collection. | | |
| 206 | | \_cs\_mk | This cookie is used for Google Analytics integrations. | | |
| 207 | ||
| 208 | ##### Third-party cookies in [www.storyset.com](http://www.storyset.com/) | |
| 209 | ||
| 210 | | THIRD PARTY | COOKIE | DESCRIPTION | MORE INFO | | |
| 211 | | --- | --- | --- | --- | | |
| 212 | | **Google Analytics** (Analysis) | | We collect information of how users interact with the content of the web. When a user browses the pages of a website, information about the page the user has viewed is colected; for example, URL, time spent on the website, number of pages viewed. It allows us to generate labels or objectives to know if you have bought, what item, how many times ... It also collects demographic and navigation data, that is; where does the user come from, how does he get to our website or what campaign does he come from | [Here](https://developers.google.com/analytics/devguides/collection/analyticsjs/cookie-usage) | | |
| 213 | | **OneTrust** | OptanonConsent | OptanonConsent and OptanonAlertBoxClosed are cookies related to our Cookie Compliance Solution. They are used to store your preferences with regards to cookies and other trackers and identify and interpret user interactions with the banner (for example, closing a banner means rejection of non-essential trackers). | [Here](https://www.onetrust.com/cookie-policy/) | | |
| 214 | | OptanonAlertBoxClosed | |