Cookies policy
January 2025
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”:
In this document we provide you with information about cookies, both in a general way and about the ones we use in particular.
I. GENERAL INFORMATION ABOUT COOKIES
What are cookies?
"Cookies" are small compressed text files that allow us to save data specifically related to the user’s device while he is visiting our website.
Generally, when referring to "cookies" on the Internet, reference is also made to other technologies used for similar purposes: for instance, through the technical configuration of your device, or your IP address when you download complete images or simply a "pixel”, data are being collected. This allows us to recognize you when you visit our website again, to know your approximate location, the connection time, the device from which you access (fixed or mobile), the operating system and browser used, the most visited pages, the number of clicks made, among others.
How to manage Cookies?
Web browsers usually allow you to disable the use of cookies; limit them to specific web pages or configure the browser to notify you when a cookie is placed in the device. You can also delete them at any time from your computer's hard drive (file: "cookies").
In most cases, a website can be accessed even if the use of cookies has been blocked in the browser settings or when they have not been accepted.
However, typically, when you block the placement of cookies, you can suffer limitations in the presentation of the website and your user interface.
To obtain more detailed information about the cookies installed on your device and how to manage and delete them, please click the link corresponding link in your web browser:
Additional information is also available at the following link:
II. SPECIFIC INFORMATION ABOUT COOKIES USED ON OUR WEBSITES
Freepik only displays advertisements to its free users: if you become a "premium" user we will not show you advertisements.. To show you this advertising, for example, we use cookies.
Freepik only hires tier-1 service providers (such as OneTrust) and advertising providers (such as IAB vendors, Google).
Regarding the control and management of cookies and similar technologies, we use One Trust “cookie compliance” technology, based on IAB Europe “Transparency and Consent Framework”.
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.
Cookies (and similar technologies) help us better understand what interests and helps our users most, and to improve our services.
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”.
Please find below the description of some of them:
Session and persistent cookies
We use the so-called “session cookies”, which are stored exclusively during the time of your visit to any of our websites.
In addition, we and our partners use "persistent cookies" to withhold information about those users who repeatedly access any of our websites.
Analytical, advertising cookies ...
We use personalized advertising cookies (which we will talk about below) and web analytics cookies, to know the number of visitors to the different pages and sections of our website, their interactions and duration of their visits, place of entry and exit, to try to improve our content and its capacity to generate interaction.
We use Google Analytics, Cloudfare and Hotjar cookies to measure the results of visits and customer acquisition, and to analyze traffic and, for example, detect potentially malicious “bots”.
Cookies can also be “first-party” or “third-party” cookies
"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.
"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.
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).
You will find detailed information about all cookies used on each of our websites in the cookie table at the end of this text.
Information on the processing of data shared with our advertising partners
Preliminary information
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.
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.
Third-parties advertising
We allocate the exploitation of our advertising spaces to companies that market them to third parties who then insert their advertisements on our website, depending on your habits and interests.
Consequently, Freepik offers its advertising spaces based on real-time biddings through two channels or platforms:
- Google AdManager and
- Various platforms that also market our advertising spaces among their own partners through header bidding techniques (Rubicon Project, Index Exchange, DistrictM, Amazon APS, OpenX, etc.).
Through these real-time biddings, companies interested in our advertising spaces, bid to display their ads on our website, customizing their advertising based on the user.
Freepik logically benefits from the advertising displayed, enables the collection of user information through cookies and captures their consent to this extent through its websites. But here is where our intervention and responsibility ends.
Freepik cannot and indeed does not control the advertisements displayed, nor does it participate in the data processing operations carried out on these platforms to select the user receiving the ads and the advertiser placing such ads.
For these purposes, and to guarantee the quality of both the advertising and the advertisers, Freepik only markets its advertisement space with the leading platforms worldwide (IAB those others mentioned in the cookies policy), as previously stated.
You can learn more about Google AdManager and the Header Bidding service providers, in their respective links as provided below.
You can browse the full list of IAB Europe partners (advertisers) here.
You can prevent targeted advertising from being specifically shown to you on Freepik websites in the following ways:
Through our cookie setting panel: by granularly accepting or rejecting the different categories of cookies used, you can authorize or not the processing of your data for the purposes of profiling you, the placing of personalized advertising, and the rest of the processing operations described hereby.
You can also disable cookies in your browser by installing a plug-in as Ghostery or Privacy Badger or through a rejection system ("opt-out") provided by some third parties that install cookies on our website, as Google (behavioral advertising) (requires Google log-in).
Freepik advertising
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).
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.
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.
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).
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.
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.
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.
International data transfers
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.
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.
Additional Information
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).
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).
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:
- Through our email rpd@freepik.com, if you are a registered user of Freepik.
- And otherwise, before the platforms in which you have a user account (because we will not be able to identify you).
Pinterest:
- Privacy Policy: https://policy.pinterest.com/en/privacy-policy
- Cookies Policy: https://policy.pinterest.com/en/cookies
Google:
- Privacy Policy: https://policies.google.com/privacy?hl=en-GB
- Cookies Policy: https://policies.google.com/technologies/cookies?hl=en-GB
X:
- Privacy Policy: https://x.com/privacy
- Cookie Policy: https://help.x.com/rules-and-policies/x-cookies
Meta (Facebook):
- Privacy Policy: https://www.facebook.com/privacy/policy and https://developers.facebook.com/docs/meta-pixel/implementation/gdpr
- Cookie Policy: https://www.facebook.com/privacy/policies/cookies/
- Annex on joint controllership: https://www.facebook.com/legal/terms/businesstools_jointprocessing
LinkedIn:
- Privacy Policy: https://www.linkedin.com/legal/privacy-policy
- Cookie Policy: https://www.linkedin.com/legal/cookie-policy
Freepik Company’s cookie table
In the table below you will find detailed information about all cookies used on Freepik's web pages.
First-party cookies on the websites owned by Freepik Company
PURPOSE | EXPIRY DATE |
Language detection. Helps us to collect information about the language preferences of the User to provide visitors with information in their preferred language | Session |
User login. Used to manage and store information about the user login | Session |
Stores URL to redirect the user after finishing the registration or login process | 10 minutes |
Remembers user’s personal ID each time they log on. This cookie is only created if the user agrees to be remembered | 30 days |
Avoids CSRF attacks in forms | 2 hours |
Stores information on marketing campaigns in which the User has participated | 30 days |
Used in the payment process to redirect the user to the payment platform in case they are logged off | 7 days |
Test about payment data. Selection of payment, subscription to Premium | 3 days |
Test about search activity. Analysis of searches run by the user | 30 days |
Checks if internal promotions are shown to the user | 2 days |
Checks if cookies compliance messages are visible on the Website | Session |
Collects information about visits | 2 years |
Develops statistics about Premium services advertisements | 1 hour |
Measures data collected from searches | 30 days |
Third-party cookies in www.slidesgo.com
THIRD PARTY | COOKIE | DESCRIPTION | MORE INFO |
Google Analytics (Tracking / 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 | |
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 |
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 | |
Google (Advertising / Analysis) | Cookie IDE | Display of ads relevant to the user, personalized ads | Here |
Cookie ANID | Display of ads relevant to the user, personalized ads | ||
Cookies DSID, FLC, AID, TAID y exchange_uid | Display of ads relevant to the user, personalized ads | ||
__gads o __gac | Among other, in measuring interactions with the ads included in that domain and avoiding being shown the same advertising too many times | ||
__gcl | Purpose: To help advertisers determine how many of the people who click on their ads end up taking an action on their website (for example, buying an item). These cookies allow Google and the advertiser to determine that you have clicked on the ad and that you have subsequently accessed the advertiser's website. Conversion cookies only last for a limited period and Google does not use them to target personalized ads. Some of the other cookies can also be used to measure conversion events. For example, Google Marketing Platform and Google Analytics cookies can also be used for this purpose | ||
Cookies: "AID", "DSID" y "TAID" | Active only when the user is logged in with his Google account. Purpose: link your activity on devices, coordinate the ads that appear on them and measure conversion events. These cookies can be enabled in the domains google.com/ads, google.com/ads/measurement or googleadservices.com | ||
Rubicon Project (Advertising) | trp_optout | Log Preferences: Cookie indicating that a user has opted-out of behavioral targeting marketing. | Here |
FPTrust | Log Preferences: These cookies support the opt-out process via the Network Advertising Initiative (NAI). | ||
Khaos | Platform Operations: Internal user identifier used for analytics. | ||
rsid | Platform Operations: Session cookie that contains information about a device, including region (derived from IP address, not geolocation data), operating System, browser, etc., that is used during the ad inventory sale process. | ||
rpx, rpx_* | Platform Operations: Contains expiration dates for information in the rpb cookie. | ||
fcap | Platform Operations: Number of times we have shown an ad on a per user basis. | ||
put_* | Platform Operations: Bidder identifiers placed at the request of a bidder, to sync a bidder’s independent information about an end user with Rubicon Project, to allow the bidder (not Rubicon Project) to bid on ads through the Rubicon Project advertising exchange based on behavioral targeting information known only to the bidder (i.e., the user identifier will be transmitted in a bid request to the bidder that caused this cookie to be placed). | ||
pux | Platform Operations: Dates for when information in the put_* and sput cookies expires and should be refreshed. | ||
rpb | Analytics: Publisher and partner-owned audience segments used for private marketplaces and audience-based planning and forecasting in Orders. | ||
sput, sput_* | Analytics: Contains multiple bidder identifiers (i.e., data that would be stored in multiple put_* cookies) in a smaller number of cookies. | ||
ses* | Analytics: Indicates number of times Rubicon Project has served a user an advert for this particular unit of inventory. | ||
vis* | Analytics: Indicates number of times a user action has precipitated an ad request for this particular unit of inventory. | ||
cd | Analytics: Indicates whether cookies are disabled for the device. | ||
cimg* | Analytics: Contains information about served ads (timestamp, site, internal identifiers for the publisher, buyer, advertiser, and displayed advertisement). | ||
audit | Analytics: Used to record cookie consent data. | ||
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 | |
OpenX (Advertising) | i | Records anonymized user data, such as IP address, geographic location, visited websites and which ads the user has clicked on, in order to optimize the display of ads based on the user's navigation on websites that use the same advertising network | Here |
pd | Collect information about visitor behavior on various websites. This information is used on the website to optimize the relevance of advertising | ||
DistrictM (Advertising) | Allows personalized advertising to be shown | Here | |
AppNexus (Advertising) | uuid2 | This cookie contains a unique randomly-generated value that enables the Platform to distinguish browsers and devices. It is matched against information – such as advertising interest segments and histories of ads shown in the browser or device – provided by clients or other third parties and stored on the Platform. This information is used by clients to select advertisements for delivery by the Platform, and to measure the performance of, and attribute payment for, those advertisements. In addition, we use this cookie to enable clients to use data which does not reveal or use an Internet user’s real-world identity or data they collect outside of the Platform or acquire from other third parties. This cookie is also sometimes matched to clients’ or other third parties’ cookies so that they can use data they collect outside of the Platform to serve more relevant advertisements to Internet users. When a user opts out of having the Platform used to select ads based on online behavior, the unique value in uuid2 is deleted and replaced with the non-unique value “-1”. | Here |
anj | The anj cookie contains data denoting whether a cookie ID is synced with our partners. | ||
icu | The icu cookie is used to select ads and limit the number of times a user sees a particular ad. It contains information such as the number of times an ad has been shown, how recently an ad has been shown, or how many total ads have been shown. | ||
Amazon APS (Advertising) | ad-id | Used by Amazon Advertising to record user actions and target website content based on ad clicks on a different website | Here |
ad-privacy | Used by Amazon Advertising to record user actions and target website content based on ad clicks on a different website | ||
Adform (Advertising) | Allows personalized advertising to be shown | Here | |
Adpone (Advertising) | Recognize and analyze inventory available in our advertising spaces to offer our users advertising of interest. Campaign optimization, segmentation, frequency. | Here | |
RichAudience (Advertising) | Allows personalized advertising to be shown | Here | |
Smartadserver (Advertising) | Allows personalized advertising to be shown | Here | |
Sovrn (Advertising) | Allows personalized advertising to be shown | Here | |
Index Exchange (Advertising) | CMPS | Identify the main server for quick responses to the user's page | Here |
CMTS | Identify backup server for quick responses to user page | ||
CMGO | Indicates if the user's primary server has changed | ||
CMTEST | Confirm if cookies can be created for the user | ||
CMID | Recognize web users that IndexExchange has seen before by browser. This is the cookie that is used to allow personalized advertising, among other uses | ||
CMPRO | Identify server profile for quick responses to user page | ||
CMRUM3 | It contains a table that maps the IDs of Index Exchange's users with those of our bidding partners | ||
CMDD | Measures how many unique pages a user has interacted with on a web property | ||
CMST | Contains the duration of a session in a session | ||
CMSC | Contains the start time of a user in a session | ||
CMO | Indicates if the web user has chosen not to participate using behavioral advertising opt-out tools | ||
Improve Digital (Advertising) | tuuid | To enable bidding process | Here |
tuuid_lu | To enable bidding process | ||
pvt | Tracks views to measure conversions | ||
ih | To limit number of advertisements you see (frequency capping) | ||
fh | Impression counter | ||
um | To enable bidding process | ||
umeh | To enable bidding process | ||
sh | To limit number of advertisements you see (frequency capping) | ||
lcri5m | Load creative | ||
lcai9h | Load campaign impressions | ||
Adagio | Stores the Adagio user ID and the user ID of Adagio bidders. | Here | |
Sharethrough | stx_user_id | This cookie is used for analytics, multivariate testing, and site optimisation. | Here |
Pubmatic (Advertising) | DPSync2 | These cookies maintain a list of our partner’s pixel IDs, which may be used to read and place cookies on a web browser, that have been synced with PubMatic IDs. This enables us to identify the partners with whom we have already synced our cookies and to ensure that we do not unnecessarily sync cookies again within a certain period of time. | Here |
KRTBCOOKIE_xxxx | We use this cookie to correlate our user IDs with those of our partners (such as demand side platform clients or other advertising technology companies). We pass the information stored by the partner in this cookie to the partner when it is considering whether to purchase advertisements. This enables the partner to make better decisions about whether to display an advertisement to you. | ||
SyncRTB2 | These cookies maintain a list of our partner’s pixel IDs, which may be used to read and place cookies on a web browser, that have been synced with PubMatic IDs. This enables us to identify the partners with whom we have already synced our cookies and to ensure that we do not unnecessarily sync cookies again within a certain period of time. | ||
SPugT | This cookie is used to track when the server-side cookie store was last updated for the browser, and it is used in conjunction with the PugT cookie, described below. | ||
ipc | This cookie is a short-lived cookie that stores information needed to coordinate cookie syncing. | ||
PMFREQ_ON | This cookie ensures the proper functioning of the camfreq and pubfreq cookies, described above, in situations where one cookie may override the other. | ||
PUBMDCID | This cookie stores an ID for the applicable PubMatic data center that is used to display an advertisement in the user’s browser. | ||
KTPCACOOKIE | We use this cookie to check if third-party cookies are enabled on the user’s browser. | ||
KADUSERCOOKIE | We use this cookie to uniquely identify each browser or device from which an individual user visits our partners’ websites. | ||
pi | This cookie enables us to determine which set of pixels needs to be executed on the browser. | ||
PugT | This cookie tracks when cookies were updated on the browser, in order to limit the number of calls to the server-side cookie store. | ||
KCCH | This cookie ensures that a PubMatic user ID is already set and that PubMatic’s code is running properly. | ||
PUBRETARGET | We use this cookie to indicate if a user can be considered for various re-targeting ad campaigns running on the Platform. For example, we may use it to determine whether to show you an advertisement that relates to a product or service that you previously viewed on an advertiser’s website. | ||
COKENBLD | This cookie sets a flag to “true” if cookies are enabled on the user’s browser. | ||
USCC | This cookie enables PubMatic to sync user IDs properly in situations where multiple advertisements might appear on the same webpage. | ||
DPPIX_ON and SYNCUPPIX_ON | These cookies enable PubMatic to properly sync cookie IDs with our partners by ensuring that our partners do not override each other during the sync process. | ||
PUBUIDSYNCUPFQ | This cookie indicates the last time that we synced IDs with our partner. | ||
camfreq_<SITEID> | This cookie is set for each campaign and indicates the number of times (e.g., frequency) that a particular advertisement may have been shown on the applicable publisher site. | ||
pubfreq_<SITEID> | This cookie is set for each advertising network and indicates the number of times (e.g., frequency) that a particular advertisement may have been shown on the applicable publisher site. | ||
pubtime_<SITEID> | This cookie stores the period of time after which ad frequency counters reset. | ||
DPFQ | This cookie stores information regarding the number of times that a partner’s pixel is loaded by a user’s browser. This enables us to cap the number of times that a pixel is used to record a user’s visit to a website within a specific period of time. | ||
repi | This cookie is a short-lived cookie that is used to determine if repixeling is in progress. | ||
pp | This cookie tracks the last publisher website that you visited that contained an advertisement served by PubMatic. | ||
FPtrust | This cookie is a session cookie used to support the opt-out process via the Network Advertising Initiative. | ||
_curtime | This cookie stores the current timestamp. | ||
ipc | This cookie is a short-lived cookie that stores information needed to coordinate cookie syncing. | ||
PMDTSHR | This cookie is set for Komli ad server and is used for default impression when other data is not available. | ||
dV | This cookie is used to save the user’s preferences and other information. | ||
UND | This cookie stores the user network default. | ||
SSCS | This cookie calls a cookie store. | ||
chk and chkSecSet | This cookie is set on Google Chrome browsers that have a version less 67 or non-Chrome browsers, and is used for testing purposes. | ||
chkChromeAb67 and chkChromeAb67Sec | This cookie is set on Google Chrome browsers that have a version above 67 and is used for testing purposes. | ||
PM-UL-Sync | This cookie is used to execute some custom UserSync integrations such as DigiTrust. | ||
Adman media (Advertising) | admtr sdr_id ired |
To identify the user and is saved with a randomly generated identifier. ADman Media also inserts cookies from third-party partners (such as Demand Side Platforms - DSPs - or other SSPs) so that they can compare their cookie with that of ADman Media and thus be able to offer services to their customers. |
Here |
Vidoomy (Advertising) | uids | Collect the IP, in order to know which country it is and assign the corresponding campaigns. | Here |
vidoomy-uids | Collect the IP, in order to know which country it is and assign the corresponding campaigns. | ||
Liveramp (Advertising) | rlas3 | Contains Liveramps unique identifier and allows Liveramp to deterministically link the user | Here |
pxrc | Contains information about LiveRamp cookie syncs triggered off the back of this browser. Used to facilitate cookie sync priority queue. (this cookie does NOT contain or process personal data) | ||
_lr_retry_request | Used to tell LiveRamp ATS whether or not to retry a call (stops more than one simultaneous API call) | ||
_lr_geo_location | Tells LiveRamp tags where the user is based | ||
_lr_drop_match_pixel | Tells LiveRamps tags whether our match pixel (which sets the rlas3 and pxrc cookies) have recently been fired | ||
_lr_env_src_ats | Tells LiveRamps what the source of the "_lr_env" value is | ||
_lr_env_src_ats | Tells LiveRamps what the source of the "_lr_env" value is | ||
_lr_env_src_ats | Tells LiveRamps what the source of the "_lr_env" value is | ||
_lr_env | Contains the Ramp ID envelope used to provide addressability in a cookieless manner. | ||
ContentSquare | _cs_id | This cookie contains the ContentSquare user ID. | Here |
_cs_s | This cookie contains the number of page views within the current session for ContentSquare Solution. | ||
_cs_vars | This cookie is used by ContentSquare to record custom variables. | ||
_cs_ex | This cookie is used by ContentSquare to exclude some visitors from the collection. | ||
_cs_c | This cookie is used by ContentSquare to store the user's consent to be tracked | ||
_cs_optout | This cookie is used by ContentSquare to exclude some visitors from the collection. | ||
_cs_mk | This cookie is used for Google Analytics. | ||
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 |
OptanonAlertBoxClosed |
III. Changes in the cookie policy
We recommend that you review this cookie policy each time you connect to our Websites. Freepik reserves the right to modify its content at any given time.
In any case, Freepik will notify or announce the new content and the dates on which a revision of these terms occurs, for the information of its users.
Last edited: January 2025